[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1177995014.28659.54.camel@localhost.localdomain>
Date: Tue, 01 May 2007 14:50:14 +1000
From: Rusty Russell <rusty@...tcorp.com.au>
To: "H. Peter Anvin" <hpa@...or.com>
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
On Mon, 2007-04-30 at 21:00 -0700, H. Peter Anvin wrote:
> H. Peter Anvin wrote:
> > Rusty Russell wrote:
> >> It'd be nicer if there were a "struct boot_params" declaration, but we
> >> can't have everything.
> >
> > It's in my patchset-under-development.
> >
> > (Preview snapshot:
> > http://userweb.kernel.org/~hpa/setup-snapshot-2007.04.30.patch)
>
> Just pushed out a git tree:
>
> http://git.kernel.org/?p=linux/kernel/git/hpa/linux-2.6-newsetup.git;a=summary
Any chance of splitting off a "struct boot_params" header (includable by
non-kernel code) for inclusion immediately? The rest can wait until
2.6.23, but it'd be sweet to get this in place sooner.
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).
Thanks,
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