From: Andrea Arcangeli <andrea@suse.de>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Andi Kleen <ak@colin2.muc.de>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@muc.de>,
linux-kernel@vger.kernel.org, jh@suse.cz
Subject: Re: [PATCH] Add CONFIG for -mregparm=3
Date: Thu, 15 Jan 2004 16:02:58 +0100 [thread overview]
Message-ID: <20040115150258.GA464@dualathlon.random> (raw)
In-Reply-To: <20040114192505.GJ23383@fs.tum.de>
On Wed, Jan 14, 2004 at 08:25:06PM +0100, Adrian Bunk wrote:
> On Wed, Jan 14, 2004 at 10:35:56AM +0100, Andi Kleen wrote:
> >...
> > I think the popular modules like nvidia or ATI could be fixed
> > relatively easily. They usually consist of a glue layer with source and a
> > binary blob that is only called from the glue layer. Basically all you
> > have to do is the mark the prototypes for the binary blob in the glue layer
> > as "asmlinkage". In addition this can be done without any ifdefs
> > because asmlinkage does the right thing on a non regparm kernel.
> >
> > Of course true binary only modules without glue layer would be more
> > difficult, but for those the vendors just have to recompile. Conceivable
> > it would be possible to write a glue layer even for them.
> >...
>
> Did I miss Linus announcing a stable ABI between kernel versions?
>
> If some binary module vendor tries to support more than one kernel
> version it's his problem - this is nothing that is officially supported
> by the Linux kernel.
agreed.
this is the sort of stuff that shouldn't be a config option, it
exercises new paths in gcc as well, _all_ the userbase has to use it, or
it's not worth the risk/pain IMHO.
next prev parent reply other threads:[~2004-01-15 19:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 9:06 [PATCH] Add CONFIG for -mregparm=3 Andi Kleen
2004-01-14 9:16 ` Russell King
2004-01-14 9:30 ` Andi Kleen
2004-01-14 9:29 ` Andrew Morton
2004-01-14 9:35 ` Andi Kleen
2004-01-14 19:25 ` Adrian Bunk
2004-01-15 15:02 ` Andrea Arcangeli [this message]
2004-01-14 9:54 ` Arjan van de Ven
2004-01-14 9:34 ` Arjan van de Ven
2004-01-14 9:39 ` Andi Kleen
2004-01-14 9:44 ` Arjan van de Ven
2004-01-14 9:47 ` Andrew Morton
2004-01-15 0:40 ` Rusty Russell
2004-01-15 9:22 ` Andi Kleen
2004-01-17 20:16 ` several oopses during boot (was: Re: [PATCH] Add CONFIG for -mregparm=3) Sander
2004-01-17 20:53 ` Andi Kleen
2004-01-17 21:07 ` Sander
2004-01-17 21:28 ` Andi Kleen
2004-01-17 22:01 ` Mike Fedyk
2004-01-18 5:44 ` Sander
2004-01-18 20:34 ` Sander
2004-01-18 21:00 ` Andi Kleen
2004-01-19 6:47 ` Sander
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=20040115150258.GA464@dualathlon.random \
--to=andrea@suse.de \
--cc=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--cc=jh@suse.cz \
--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