All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin O'Connor <kevin@koconnor.net>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	"seabios@seabios.org" <seabios@seabios.org>
Subject: Re: [Xen-devel] Re: [RFC] [PATCH 0/2] Basic SeaBIOS support for Xen HVM
Date: Mon, 23 May 2011 20:17:59 -0400	[thread overview]
Message-ID: <20110524001759.GC28567@morn.localdomain> (raw)
In-Reply-To: <1306147478.20576.85.camel@zakaz.uk.xensource.com>

On Mon, May 23, 2011 at 11:44:38AM +0100, Ian Campbell wrote:
> On Tue, 2011-05-17 at 16:59 +0100, Ian Campbell wrote:
> > The following implements all your feedback (I hope). I have squashed it
> > down into a single commit which supports direct boot.

BTW, in general, the above patch looks okay to me.

> I've gotten all the PCI setup and ACPI stuff etc etc working but,
> frankly, the patch to SeaBIOS is getting to be pretty enormous and
> intrusive.

Is that due to incompleteness / innacuracies in the current SeaBIOS
code, or due to requirements specific to Xen?

If you have test code, I'd be curious to see a patch on the mailing
list - it may help later to understand the use cases for SeaBIOS.

> The more I look at it the more I am coming to the conclusion that it
> would be better to have hvmloader setup all this platform level stuff
> and pass details onto SeaBIOS as necessary, following the model used
> with coreboot->SeaBIOS rather than the emulator's way of doing things.
> hvmloader basically already fulfils the same role for Xen HVM guests as
> coreboot does for physical hardware so I think that makes a certain
> amount of sense.

I'm okay with that approach as well - there are pros and cons to each
method.  (At various points, it's been discussed whether SeaBIOS
should generate ACPI tables for coreboot, and it has also been
discussed if QEmu should just pass in ACPI tables to SeaBIOS..)

-Kevin

  reply	other threads:[~2011-05-24  0:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13 15:59 [RFC] [PATCH 0/2] Basic SeaBIOS support for Xen HVM Ian Campbell
2011-05-13 15:59 ` [PATCH 1/2] Kconfig: Add option to enable support for running as a Xen HVM guests BIOS Ian Campbell
2011-05-13 15:59 ` [PATCH 2/2] Basic support for booting directly as Xen HVM firmware Ian Campbell
2011-05-14 14:02   ` Kevin O'Connor
2011-05-16  8:45     ` Ian Campbell
2011-05-14 13:36 ` [RFC] [PATCH 0/2] Basic SeaBIOS support for Xen HVM Kevin O'Connor
2011-05-16  8:44   ` [SeaBIOS] " Ian Campbell
2011-05-16 23:39     ` Kevin O'Connor
2011-05-17 15:59       ` Ian Campbell
2011-05-23 10:44         ` Re: [SeaBIOS] " Ian Campbell
2011-05-24  0:17           ` Kevin O'Connor [this message]
2011-05-24 11:02             ` [Xen-devel] " Ian Campbell
2011-05-24 12:38               ` [SeaBIOS] " Gerd Hoffmann
2011-05-25  2:44               ` Re: [SeaBIOS] " Kevin O'Connor
2011-05-26 15:13                 ` [SeaBIOS] " Ian Campbell
2011-05-27  1:20                   ` [Xen-devel] " Kevin O'Connor
2011-05-27  9:27                     ` Ian Campbell
2011-05-30 14:43                       ` Kevin O'Connor
2011-06-01  9:17                         ` Ian Campbell

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=20110524001759.GC28567@morn.localdomain \
    --to=kevin@koconnor.net \
    --cc=Ian.Campbell@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=seabios@seabios.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.