From: Andi Kleen <ak@suse.de>
To: Jari Ruusu <jariruusu@users.sourceforge.net>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Arjan van de Ven <arjan@infradead.org>,
Benjamin LaHaise <bcrl@kvack.org>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] x86-64 put current in r10
Date: Wed, 30 Nov 2005 18:32:56 +0100 [thread overview]
Message-ID: <20051130173256.GS19515@wotan.suse.de> (raw)
In-Reply-To: <438DE183.439170CD@users.sourceforge.net>
On Wed, Nov 30, 2005 at 07:29:39PM +0200, Jari Ruusu wrote:
> Nick Piggin wrote:
> > Sounds like a trick question - I don't think the kernel does use any
> > out-of-tree amd64 assember code, does it? ;)
>
> Out-of-tree amd64 assember code is being run in kernel space. For example:
> http://loop-aes.sourceforge.net/
>
> Calling convention change that breaks existing assembler code that has been
> field proven and is believed to be entirely free of bugs for long time, does
> NOT belong in a STABLE kernel series.
I don't think you understand the policies of linux kernel development
very well.
If you want your code be maintained it's best to submit it to mainline.
Otherwise you're on your own.
Anyways - as long as your assembly code doesn't call any other kernel
services it should be enough to just save/restore R10 at the beginning/end.
Interrupts reload it automatically.
-Andi
next prev parent reply other threads:[~2005-11-30 17:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 4:21 Benjamin LaHaise
2005-11-30 6:39 ` Jari Ruusu
2005-11-30 7:56 ` Arjan van de Ven
2005-11-30 8:20 ` Nick Piggin
2005-11-30 17:29 ` Jari Ruusu
2005-11-30 17:32 ` Andi Kleen [this message]
2005-11-30 17:33 ` Christoph Hellwig
2005-11-30 12:45 ` Andi Kleen
2005-11-30 16:22 ` Randy.Dunlap
2005-11-30 16:39 ` Kyle Moffett
2005-12-01 9:06 ` Helge Hafting
2005-11-30 13:02 ` Andi Kleen
2005-11-30 13:32 ` Arjan van de Ven
2005-11-30 15:10 ` Benjamin LaHaise
2005-11-30 13:57 ` Andi Kleen
2005-11-30 15:18 ` Matti Aarnio
2005-11-30 15:24 ` Benjamin LaHaise
2005-11-30 15:29 ` Andi Kleen
2005-11-30 15:34 ` Arjan van de Ven
2005-11-30 16:13 ` Jesper Juhl
2005-12-01 14:30 ` Steven Rostedt
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=20051130173256.GS19515@wotan.suse.de \
--to=ak@suse.de \
--cc=arjan@infradead.org \
--cc=bcrl@kvack.org \
--cc=jariruusu@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.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 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®