From: Jason Wessel <jason.wessel@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Martin Hicks <mort@sgi.com>
Subject: Re: linux-next: kgdb tree build warning
Date: Thu, 24 Dec 2009 08:44:48 -0600 [thread overview]
Message-ID: <4B337E60.4000200@windriver.com> (raw)
In-Reply-To: <20091224162117.ac18e50f.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Jason,
>
> On Wed, 23 Dec 2009 22:09:00 -0600 Jason Wessel <jason.wessel@windriver.com> 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.
prev parent reply other threads:[~2009-12-24 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 23:48 linux-next: kgdb tree build warning Stephen Rothwell
2009-12-24 4:09 ` Jason Wessel
2009-12-24 5:21 ` Stephen Rothwell
2009-12-24 14:44 ` Jason Wessel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B337E60.4000200@windriver.com \
--to=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mort@sgi.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.