From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, fastboot@lists.osdl.org
Subject: Re: [-mm patch] i386: enable REGPARM by default
Date: Fri, 24 Jun 2005 13:28:26 -0700 [thread overview]
Message-ID: <20050624132826.4cdfb63c.akpm@osdl.org> (raw)
In-Reply-To: <20050624200916.GJ6656@stusta.de>
Adrian Bunk <bunk@stusta.de> wrote:
>
> This patch:
> - removes the dependency of REGPARM on EXPERIMENTAL
> - let REGPARM default to y
hm, a compromise.
One other concern I have with this is that I expect -mregparm will make
kgdb (and now crashdump) less useful. When incoming args are on the stack
you have a good chance of being able to see what their value is by walking
the stack slots.
When the incoming args are in registers I'd expect that it would be a lot
harder (or impossible) to work out their value.
Have the kdump guys thought about (or encountered) this?
next prev parent reply other threads:[~2005-06-24 20:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 20:09 Adrian Bunk
2005-06-24 20:28 ` Andrew Morton [this message]
2005-06-24 23:08 ` [Fastboot] " Alexander Nyberg
2005-06-27 13:29 ` Vivek Goyal
2005-06-27 14:00 ` Daniel Jacobowitz
2005-06-28 4:51 ` Vivek Goyal
2005-06-28 11:24 ` Vivek Goyal
2005-06-28 19:59 ` Mark Kettenis
2005-06-29 8:34 ` Vivek Goyal
2005-06-29 10:06 ` Mark Kettenis
2005-06-29 11:47 ` Vivek Goyal
2005-06-25 7:46 ` Denis Vlasenko
2005-06-28 12:16 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2005-05-30 0:28 Adrian Bunk
2005-05-15 11:57 Adrian Bunk
2005-05-15 12:22 ` Andi Kleen
2005-05-15 12:37 ` Adrian Bunk
2005-05-15 13:00 ` Andi Kleen
2005-05-15 13:12 ` Arjan van de Ven
2005-05-15 13:16 ` Adrian Bunk
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=20050624132826.4cdfb63c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®