Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754764AbZLXOo4 (ORCPT ); Thu, 24 Dec 2009 09:44:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752365AbZLXOoz (ORCPT ); Thu, 24 Dec 2009 09:44:55 -0500 Received: from mail.windriver.com ([147.11.1.11]:62877 "EHLO mail.windriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751851AbZLXOoy (ORCPT ); Thu, 24 Dec 2009 09:44:54 -0500 Message-ID: <4B337E60.4000200@windriver.com> Date: Thu, 24 Dec 2009 08:44:48 -0600 From: Jason Wessel User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Stephen Rothwell CC: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Martin Hicks Subject: Re: linux-next: kgdb tree build warning References: <20091224104812.7f2495f3.sfr@canb.auug.org.au><4B32E95C.3030201@windriver.com> <20091224162117.ac18e50f.sfr@canb.auug.org.au> In-Reply-To: <20091224162117.ac18e50f.sfr@canb.auug.org.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Dec 2009 14:44:49.0031 (UTC) FILETIME=[A4A74170:01CA84A7] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1872 Lines: 49 Stephen Rothwell wrote: > Hi Jason, > > On Wed, 23 Dec 2009 22:09:00 -0600 Jason Wessel wrote: > >> Stephen Rothwell wrote: >> >>> Today's linux-next build (x86_64_allmodconfig) produced this warning: >>> >>> kernel/debug/kdb/kdb_bp.c: In function 'kdb_bp': >>> kernel/debug/kdb/kdb_bp.c:434: warning: the frame size of 32880 bytes is larger than 2048 bytes >>> >>> > That function has a kdb_bp_t on its stack which contains an NR_CPUS array > of pointers. NR_CPUS is 4096 (in this build) and pointers are 8 bytes, > so there is 32K right there :-( > > Thank you for the details. I see that I can see the same problem if I set CONFIG_MAXSMP and use CONFIG_FRAME_WARN=2048. It also allowed me to test that the problem is really fixed. :-) I had talked with Martin a while back and he gave me some patches which cleaned up the breakpoint code (kdb_bp.c). The hw breakpoint support was implemented a different way in the new kdb/kgdb. You stumbled upon something that was intended to already be removed from the source. As a side point you pointed me to an area where I could remove some other code that should not be there because the debug core is already handling the operations. The net result is this problem is fixed, and 2 more variables are gone out of that struct. - int bp_cpu; /* Cpu # (if bp_global == 0) */ - kdbhard_bp_t *bp_hard[NR_CPUS]; /* Hardware breakpoint structure */ - int bp_adjust; /* Adjustment to PC for real - * instruction */ Thanks, Jason. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/