qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Kevin O'Connor <kevin@koconnor.net>,
	seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [SeaBIOS] [PATCHv2] load hpet info for HPET ACPI table from qemu
Date: Mon, 14 Jun 2010 19:03:52 +0300	[thread overview]
Message-ID: <20100614160352.GC13238@redhat.com> (raw)
In-Reply-To: <20100614144016.GB9550@shareable.org>

On Mon, Jun 14, 2010 at 03:40:16PM +0100, Jamie Lokier wrote:
> Gleb Natapov wrote:
> > On Mon, Jun 14, 2010 at 09:54:25AM -0400, Kevin O'Connor wrote:
> > > Could we just have qemu build the hpet tables and pass them through to
> > > seabios?  Perhaps using the qemu_cfg_acpi_additional_tables() method.
> > > 
> > Possible, and I considered that. I personally prefer to pass minimum
> > information required for seabios to discover underlying HW and leave
> > ACPI table creation to seabios. That is how things done for HW that
> > seabios can actually detect. If we will go your way pretty soon we will
> > move creation of ACPI/SMBIOS/MP tables into qemu and IMHO this will be
> > step backworkds.
> 
> Why would creation of all the tables in qemu be a bad thing or a step
> in the wrong direction?
> 
See Avi's answer. All those tables are firmware/OS interface and as such
may (and some definitely do) contain information known only to BIOS.

--
			Gleb.

  reply	other threads:[~2010-06-14 16:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14  8:30 [Qemu-devel] [PATCHv2] load hpet info for HPET ACPI table from qemu Gleb Natapov
2010-06-14 13:54 ` [Qemu-devel] Re: [SeaBIOS] " Kevin O'Connor
2010-06-14 14:09   ` Gleb Natapov
2010-06-14 14:40     ` Jamie Lokier
2010-06-14 16:03       ` Gleb Natapov [this message]
2010-06-14 14:51     ` Avi Kivity
2010-06-14 18:25       ` Kevin O'Connor
2010-06-14 18:56         ` Gleb Natapov
2010-06-14 20:12           ` Kevin O'Connor
2010-06-15  6:37             ` Gleb Natapov
2010-06-17  1:22               ` Kevin O'Connor
2010-06-17  7:45                 ` Gleb Natapov
2010-06-17  1:58             ` Peter Stuge
2010-06-14 19:38         ` Anthony Liguori
2010-06-15  4:47           ` Avi Kivity
2010-06-15  6:50             ` Gleb Natapov
2010-06-17  1:47               ` Kevin O'Connor
2010-06-17  3:58                 ` Avi Kivity
2010-06-17  6:57                   ` Peter Stuge
2010-06-15  0:54         ` Paul Brook
2010-06-15  4:41         ` Avi Kivity
2010-06-17  0:55           ` Kevin O'Connor
2010-06-17  6:44             ` Gleb Natapov

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=20100614160352.GC13238@redhat.com \
    --to=gleb@redhat.com \
    --cc=jamie@shareable.org \
    --cc=kevin@koconnor.net \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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).