[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4636D017.5060108@zytor.com>
Date: Mon, 30 Apr 2007 22:28:55 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Rusty Russell <rusty@...tcorp.com.au>
CC: "Eric W. Biederman" <ebiederm@...ssion.com>,
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,
virtualization <virtualization@...ts.linux-foundation.org>
Subject: Re: [patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for
relocatable bzImage
Rusty Russell wrote:
>
> BTW, wrt. a new "platform type" field, should it go something like this?
>
> -0235/3 N/A pad2 Unused
> +0235/1 2.07+ platform_type Runtime platform (see below)
> +0236/2 N/A pad2 Unused
> ...
> + platform_type:
> + For kernels which can boot on multiple platforms. Currently
> + 0 == native (normal), 1 == lguest (paravirtualized).
>
Well, yes, but we need to think about if there is more things that
should be added. There *definitely* should be space for a platform data
pointer, to start out with. I would also like to see a platform data
field, as well as a bootloader extension field (we're going to have that
problem soon enough.)
-hpa
-
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