xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	Kevin O'Connor <kevin@koconnor.net>,
	"seabios@seabios.org" <seabios@seabios.org>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [SeaBIOS] Re: [RFC] [PATCH 0/2] Basic SeaBIOS support for Xen HVM
Date: Tue, 24 May 2011 14:38:48 +0200	[thread overview]
Message-ID: <4DDBA6D8.5010801@redhat.com> (raw)
In-Reply-To: <1306234927.20576.155.camel@zakaz.uk.xensource.com>

   Hi,

> PCI setup is one of the main things, the interrupt routing in particular
> is different which has knock on effects on chipset setup (e.g. legacy
> PCI ISA IRQ routing) and the BIOS tables (e.g. ACPI _PRT entries). This
> strikes me as being highly "mainboard" specific, IOW the stuff I would
> expect to find in coreboot rather than SeaBIOS.

There is q35 emulation support in for qemu in the pipeline, which has 
simliar requirements, especially it needs a different dsdt table too. 
So a solution is needed here anyway.  One option is to just pass the 
table from qemu, another one is to have multiple tables compiled in and 
have seabios pick one at runtime depending on the hardware it detects.

> Another difference is that the existing hvmloader tables are ACPI 2.0
> while SeaBIOS only creates 1.0 tables, I'm not sure that strictly
> speaking counts as a incompleteness in SeaBIOS since it's not obvious
> that Xen actually needs/uses any of the functionality of 2.0. Also it
> might be something SeaBIOS would like to grow in any case.

Indeed, I don't see that as a xen specific thing.

cheers,
   Gerd

  reply	other threads:[~2011-05-24 12:38 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               ` Gerd Hoffmann [this message]
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=4DDBA6D8.5010801@redhat.com \
    --to=kraxel@redhat.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=kevin@koconnor.net \
    --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).