From: Eric Valette <eric.valette@free.fr>
To: "Zephaniah E. Hull" <warp@babylon.d2dc.net>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: RE : 2.6.6-rc3-mm2 : REGPARAM forced => no external module with some object code only
Date: Thu, 06 May 2004 15:05:59 +0200 [thread overview]
Message-ID: <409A3837.2060509@free.fr> (raw)
In-Reply-To: <20040506124454.GA12921@babylon.d2dc.net>
Zephaniah E. Hull wrote:
> On Wed, May 05, 2004 at 01:18:09PM -0700, Andrew Morton wrote:
>
>>Eric Valette <eric.valette@free.fr> wrote:
>>
>>>The Changelog says nothing really important but forcing REGPARAM is
>>> rather important : it breaks any external module using object only code
>>> that calls a kernel function.
>>
>>This is why we should remove the option - to reduce the number of ways in
>>which the kernel might have been built. Yes, there will be a bit of
>>transition pain while these people catch up.
>
>
> Any guess on when REGPARAM and 4KSTACKS will end up in Linus' tree?
> (Of interest because people may not consider it that important until
> they know it really is going to bite them.)
Well, may I suggest that the impact on end users is absolutely not the
same :
- 4KSTACKS only bites people that use badly written drivers allocating
a lot of local variables on the stack (Nvidia, ...) and the availiable
stack using this config is (from what I've read on this list) roughly
equivalent to what is availiable in 2.4 series...
- REGPARAM kills any driver whith object only file containing system calls,
Concerning the number of ways the kernel is compiled, I think that the
number of GCC version produce even more debugging path than theses
options. I really wonder if this is not a tactical game to push hardware
manufacturer. But beware it could strike back because some supplier may
just give up if they have to work on their driver even on stable series...
--
__
/ ` Eric Valette
/-- __ o _. 6 rue Paul Le Flem
(___, / (_(_(__ 35740 Pace
Tel: +33 (0)2 99 85 26 76 Fax: +33 (0)2 99 85 26 76
E-mail: eric.valette@free.fr
next prev parent reply other threads:[~2004-05-06 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 11:56 RE : 2.6.6-rc3-mm2 : REGPARAM forced => no external module with some object code only Eric Valette
2004-05-05 12:09 ` Re " Eric Valette
2004-05-05 20:18 ` RE " Andrew Morton
2004-05-06 12:44 ` Zephaniah E. Hull
2004-05-06 12:56 ` Jan-Benedict Glaw
2004-05-06 13:05 ` Eric Valette [this message]
2004-05-06 15:21 ` Andrew Morton
2004-05-09 17:03 ` Bill Davidsen
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=409A3837.2060509@free.fr \
--to=eric.valette@free.fr \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warp@babylon.d2dc.net \
/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