virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Vivek Goyal <vgoyal@in.ibm.com>,
	v12n <virtualization@lists.linux-foundation.org>
Subject: [PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting
Date: Wed, 06 Jun 2007 15:58:37 -0700	[thread overview]
Message-ID: <20070606225837.654272428@goop.org> (raw)

This series:
 1. Updates the boot protocol to version 2.07
 2. Clean up the existing build process, to get rid of tools/build and
    make the linker do more heavy lifting
 3. Make the bzImage payload an ELF file.  The bootloader can extract
    this as a naked ELF file by skipping over boot_params.setup_sects worth
    of 16-bit setup code.
 4. Update the boot_params to 2.07, and update the kernel's head.S to
    jump to the appropriate subarch-specific kernel entrypoint.  The
    very earliest code is common (copy boot_params, clear bss); the
    split happens just before the initial pagetable setup.
+ random little changes to make it all hang together

This boots native for me, so everything basically works.  But I haven't
tested it end-to-end yet, because I haven't done the Xen bits yet.
Perhaps Rusty can do the lguest version to verify that its all sound in
principle (hint hint ;).

So, how does it look?

	J
-- 

             reply	other threads:[~2007-06-06 22:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 22:58 Jeremy Fitzhardinge [this message]
2007-06-06 22:58 ` [PATCH RFC 1/7] update boot spec to 2.07 Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 2/7] add WEAK() for creating weak asm labels Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 3/7] allow linux/elf.h to be included in assembler Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 4/7] define ELF notes for adding to a boot image Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 5/7] i386: clean up bzImage generation Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 6/7] i386: make the bzImage payload an ELF file Jeremy Fitzhardinge
2007-06-06 23:41   ` H. Peter Anvin
2007-06-06 23:56     ` Jeremy Fitzhardinge
     [not found]     ` <466749C8.2010700@goop.org>
2007-06-07  0:08       ` H. Peter Anvin
     [not found]       ` <46674C96.7090104@zytor.com>
2007-06-07  0:20         ` Jeremy Fitzhardinge
     [not found]         ` <46674F68.6030100@goop.org>
2007-06-07  0:42           ` H. Peter Anvin
     [not found]           ` <4667547B.8080502@zytor.com>
2007-06-07  1:01             ` Jeremy Fitzhardinge
2007-06-08  3:49             ` Vivek Goyal
     [not found]             ` <20070608034958.GA10728@in.ibm.com>
2007-06-08  4:01               ` H. Peter Anvin
2007-06-07  1:47     ` Rob Landley
     [not found]     ` <200706062147.21225.rob@landley.net>
2007-06-07  1:54       ` H. Peter Anvin
2007-06-07 16:08         ` Rob Landley
     [not found]         ` <200706071208.04777.rob@landley.net>
2007-06-07 16:14           ` H. Peter Anvin
2007-06-06 22:58 ` [PATCH RFC 7/7] i386: paravirt boot sequence 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=20070606225837.654272428@goop.org \
    --to=jeremy@goop.org \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@in.ibm.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).