[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1177902195.30071.203.camel@localhost.localdomain>
Date: Mon, 30 Apr 2007 13:03:15 +1000
From: Rusty Russell <rusty@...tcorp.com.au>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Jeremy Fitzhardinge <jeremy@...p.org>,
Jeff Garzik <jeff@...zik.org>, Andi Kleen <ak@...e.de>,
patches@...-64.org, Vivek Goyal <vgoyal@...ibm.com>,
linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
virtualization <virtualization@...ts.linux-foundation.org>
Subject: Re: [patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for
relocatable bzImage
On Sun, 2007-04-29 at 09:11 -0600, Eric W. Biederman wrote:
> Right now I'm a little frustrated that insanity below slipped into
> head.S right after the 32bit entry point after the review said
> use the normal linux parameters for parameter passing.
>
> > #ifdef CONFIG_PARAVIRT
> > movl %cs, %eax
> > testl $0x3, %eax
> > jnz startup_paravirt
> > #endif
>
> The whole thing should be based on a value in the linux parameter block
> pointed to by %esi, instead of the insane preserve all registers and
> attempt to be super compatible with everyone.
Dammit, Eric, you spend a lot of time using words like "insane" where
you mean we didn't do everything all at once.
It's *not* clear that using %esi is sane, but nothing in the current
code prevents that.
I was trying to get Xen to use this entry point rather than their own: I
failed, and only lguest now uses it.
Fortunately, this also means it's trivial to change.
Rusty.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists