From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Satya <satyakiran@gmail.com>
Cc: v12n <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 10/10] xen: use boot protocol to boot xen kernel
Date: Fri, 15 Jun 2007 09:41:29 -0700 [thread overview]
Message-ID: <4672C139.602@goop.org> (raw)
In-Reply-To: <acbcf3840706150912k4c80dfaak17260d503a007278@mail.gmail.com>
Satya wrote:
> hi,
> I was trying to figure out the boot code of mini-os included in the
> Xen-3.1 source distribution. Is it going to change significantly
> because of this new boot protocol? thanks!
No, there's no change for existing Xen kernels. It only changes if
you're booting from a bzImage format kernel.
J
next prev parent reply other threads:[~2007-06-15 16:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070615004818.424726597@goop.org>
2007-06-15 0:48 ` [PATCH 01/10] update boot spec to 2.07 Jeremy Fitzhardinge
2007-06-15 0:48 ` [PATCH 02/10] allow linux/elf.h to be included in assembler Jeremy Fitzhardinge
2007-06-15 0:48 ` [PATCH 03/10] define ELF notes for adding to a boot image Jeremy Fitzhardinge
2007-06-15 0:48 ` [PATCH 04/10] i386: clean up bzImage generation Jeremy Fitzhardinge
2007-06-15 0:48 ` [PATCH 05/10] i386: make the bzImage payload an ELF file Jeremy Fitzhardinge
2007-06-15 0:48 ` [PATCH 06/10] add WEAK() for creating weak asm labels Jeremy Fitzhardinge
2007-06-15 0:48 ` [PATCH 07/10] always allocate space for notes Jeremy Fitzhardinge
2007-06-15 0:48 ` [PATCH 08/10] i386: paravirt boot sequence Jeremy Fitzhardinge
2007-06-15 0:48 ` [PATCH 09/10] ask the hypervisor how much space it needs reserved Jeremy Fitzhardinge
2007-06-15 0:48 ` [PATCH 10/10] xen: use boot protocol to boot xen kernel Jeremy Fitzhardinge
[not found] ` <20070615005013.609105644@goop.org>
2007-06-15 16:12 ` Satya
2007-06-15 16:41 ` Jeremy Fitzhardinge [this message]
[not found] ` <20070615005012.962196819@goop.org>
2007-06-15 16:20 ` [PATCH 04/10] i386: clean up bzImage generation H. Peter Anvin
[not found] ` <4672BC3E.6080308@zytor.com>
2007-06-15 16:34 ` Jeremy Fitzhardinge
[not found] ` <4672BF82.9050101@goop.org>
2007-06-15 16:51 ` H. Peter Anvin
[not found] ` <4672C383.7000304@zytor.com>
2007-06-15 17:03 ` Jeremy Fitzhardinge
[not found] ` <20070615005012.882738673@goop.org>
2007-06-15 16:20 ` [PATCH 03/10] define ELF notes for adding to a boot image H. Peter Anvin
[not found] ` <4672BC5B.1040502@zytor.com>
2007-06-15 16:40 ` Jeremy Fitzhardinge
[not found] ` <4672C0FF.9080209@goop.org>
2007-06-26 20:18 ` Andrew Morton
2007-06-26 20:21 ` Jeremy Fitzhardinge
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=4672C139.602@goop.org \
--to=jeremy@goop.org \
--cc=satyakiran@gmail.com \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).