public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@kvack.org>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: 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 10:24:35 -0500	[thread overview]
Message-ID: <20051130152435.GC23308@kvack.org> (raw)
In-Reply-To: <20051130151847.GE5706@mea-ext.zmailer.org>

On Wed, Nov 30, 2005 at 05:18:47PM +0200, Matti Aarnio wrote:
> I would rather prefer NOT to introduce this at this time.
> My primary concern is that during "even numbered series" there
> should not be radical internal ABI/API changes, like this one.

Any modules built by the official Makefile method will atomatically 
pick up the necessary changes to the compiler flags, and the ABI 
presented to userspace is unchanged.

Also, part of the patch series is needed in order to introduce colouring 
of the kernel stack (namely divorcing the relationship of thread_info 
with the stack pointer).

> In 2.7 it can be introduced, by all means.

As far as I am aware, there is no plan for a 2.7 at this time.

> Indeed at the moment my thinking is, that X86-64 is way more UNSTABLE,
> than it should be.  (And Linux kernel overall, but that is another story.)

At least I found one problem that was impacting the boot stability of my 
test box, so it can't all be bad. =-)

		-ben
-- 
"You know, I've seen some crystals do some pretty trippy shit, man."
Don't Email: <dont@kvack.org>.

  reply	other threads:[~2005-11-30 15:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30  4:21 [PATCH 0/9] x86-64 put current in r10 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
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 [this message]
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=20051130152435.GC23308@kvack.org \
    --to=bcrl@kvack.org \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.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