From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] always enable regparm on i386
Date: Sun, 9 Jan 2005 01:22:53 +0100 [thread overview]
Message-ID: <20050109002253.GJ14108@stusta.de> (raw)
In-Reply-To: <20050108155248.25393222.akpm@osdl.org>
On Sat, Jan 08, 2005 at 03:52:48PM -0800, Andrew Morton wrote:
> Adrian Bunk <bunk@stusta.de> wrote:
> >
> > The patch below always enables regparm on i386 (with gcc >= 3.0).
> >
> > With this patch, it should get a better testing coverage in -mm.
> >
> > If this doesn't cause any problems, I plan to send a patch to completely
> > remove the CONFIG_REGPARM option after 2.6.11 will be released.
>
> -mregparm has revealed at least two kernel bugs thus far. The ability to
> disable -mregparm is a useful diagnostic tool.
You are still able to disable it by editing the Kconfig file.
And even if the option will no longer be present at some time in the
future, it will be trivial to disable it in the Makefile.
But currently (an option depending on EXPERIMENTAL) the testing coverage
isn't that big, and with this -mm patch, most people using -mm [1] will
have it enabled and notice if other problems pop up.
cu
Adrian
[1] except for those with gcc < 3.0 or !i386
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-01-09 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 20:50 [-mm patch] always enable regparm on i386 Adrian Bunk
2005-01-08 23:52 ` Andrew Morton
2005-01-09 0:22 ` Adrian Bunk [this message]
2005-03-27 20:21 Adrian Bunk
2005-03-29 1:33 ` Andrew Morton
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=20050109002253.GJ14108@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@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;
as well as URLs for NNTP newsgroup(s).