Messages in this thread |  | | | Date | Wed, 30 Nov 2005 10:24:35 -0500 | | From | Benjamin LaHaise <> | | Subject | Re: [PATCH 0/9] x86-64 put current in r10 |
| |
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>. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |