xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Kevin O'Connor <kevin@koconnor.net>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: 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: Thu, 26 May 2011 21:20:01 -0400	[thread overview]
Message-ID: <20110527012001.GA374@morn.localdomain> (raw)
In-Reply-To: <1306422817.775.48.camel@zakaz.uk.xensource.com>

On Thu, May 26, 2011 at 04:13:37PM +0100, Ian Campbell wrote:
> On Tue, 2011-05-24 at 22:44 -0400, Kevin O'Connor wrote:
> > On Tue, May 24, 2011 at 12:02:07PM +0100, Ian Campbell wrote:
> > > Would that involve pulling a bunch of mainboard specific stuff from
> > > coreboot into SeaBIOS?
> > 
> > The idea - when it was last raised - was to provide raw info in a
> > coreboot specific manor (via the "coreboot tables"), and then have
> > SeaBIOS populate ACPI/SMBIOS/MPTable/etc. from that info.  It was
> > never pursued.
> 
> Speaking of coreboot tables... I also need to pass some start of day
> info into seabios (ACPI tables, e820 etc). Currently I just used a
> little ad-hoc data structure at a known physical address but I wonder if
> perhaps I should/could reuse the coreboot table datastructures? They are
> existing and well defined and I suppose they are pretty static, but I
> don't want to add any additional compatibility burden if you guys would
> rather avoid it.

Will Xen support the fw_cfg interface?  If so, passing this info
should be possible through that interface.  Another thing to consider
would be if coreboot+SeaBIOS in place of hvmloader would be a fit.  (I
don't have a good feel for what hvmloader does to judge that.)

Using the coreboot tables in Xen seems a bit odd, but I can't say it
would cause a problem.

-Kevin

  reply	other threads:[~2011-05-27  1:20 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           ` [Xen-devel] " Kevin O'Connor
2011-05-24 11:02             ` 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                   ` Kevin O'Connor [this message]
2011-05-27  9:27                     ` [Xen-devel] " 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=20110527012001.GA374@morn.localdomain \
    --to=kevin@koconnor.net \
    --cc=Ian.Campbell@eu.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 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).