qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Nguyen Anh Quynh <aquynh@gmail.com>
Cc: kvm-devel@lists.sourceforge.net,
	Paul Brook <paul@codesourcery.com>,
	qemu-devel@nongnu.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: [Qemu-devel] Re: [RFC] linuxboot Option ROM for Linux kernel booting
Date: Tue, 22 Apr 2008 08:50:21 -0500	[thread overview]
Message-ID: <480DED1D.8080701@us.ibm.com> (raw)
In-Reply-To: <9cde8bff0804202032k6bd44ac6td913c05410e6284@mail.gmail.com>

Nguyen Anh Quynh wrote:
> Hi,
>
> This should be submitted to upstream (but not to kvm-devel list), but
> this is only the test code that I want to quickly send out for
> comments. In case it looks OK, I will send it to upstream later.
>
> Inspired by extboot and conversations with Anthony and HPA, this
> linuxboot option ROM is a simple option ROM that intercepts int19 in
> order to execute linux setup code. This approach eliminates the need
> to manipulate the boot sector for this purpose.
>
> To test it, just load linux kernel with your KVM/QEMU image using
> -kernel option in normal way.
>
> I succesfully compiled and tested it with kvm-66 on Ubuntu 7.10, guest
> Ubuntu 8.04.
>   

For the next rounds, could you actually rebase against upstream QEMU and 
submit to qemu-devel?  One of Paul Brook's objections to extboot had 
historically been that it wasn't not easily sharable with other 
architectures.  With a C version, it seems more reasonable now to do that.

Make sure you remove all the old linux boot code too within QEMU along 
with the -hda checks.

Regards,

Anthony Liguori

> Thanks,
> Quynh
>
>
> # diffstat linuxboot1.diff
>  Makefile             |   13 ++++-
>  linuxboot/Makefile   |   40 +++++++++++++++
>  linuxboot/boot.S     |   54 +++++++++++++++++++++
>  linuxboot/farvar.h   |  130 +++++++++++++++++++++++++++++++++++++++++++++++++++
>  linuxboot/rom.c      |  104 ++++++++++++++++++++++++++++++++++++++++
>  linuxboot/signrom    |binary
>  linuxboot/signrom.c  |  128 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  linuxboot/util.h     |   69 +++++++++++++++++++++++++++
>  qemu/Makefile        |    3 -
>  qemu/Makefile.target |    2
>  qemu/hw/linuxboot.c  |   39 +++++++++++++++
>  qemu/hw/pc.c         |   22 +++++++-
>  qemu/hw/pc.h         |    5 +
>  13 files changed, 600 insertions(+), 9 deletions(-)
>   

  parent reply	other threads:[~2008-04-22 13:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21  3:32 [Qemu-devel] [RFC] linuxboot Option ROM for Linux kernel booting Nguyen Anh Quynh
2008-04-21  3:33 ` [Qemu-devel] " Nguyen Anh Quynh
2008-04-21  3:36   ` Nguyen Anh Quynh
2008-04-22  9:07     ` Nguyen Anh Quynh
2008-04-22 10:35       ` Alexander Graf
2008-04-23 13:40         ` Nguyen Anh Quynh
2008-04-22 13:45       ` Anthony Liguori
2008-04-22 16:23       ` H. Peter Anvin
2008-04-23 13:49         ` Nguyen Anh Quynh
2008-04-22 13:50 ` Anthony Liguori [this message]
2008-04-22 15:02   ` Laurent Vivier
2008-04-23 13:41   ` Nguyen Anh Quynh

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=480DED1D.8080701@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=aquynh@gmail.com \
    --cc=hpa@zytor.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.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).