qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paul Brook <paul@codesourcery.com>
Cc: Gleb Natapov <gleb@qumranet.com>,
	Chris Lalancette <clalance@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 0/3]: Add UUID command-line option
Date: Mon, 28 Jul 2008 15:55:10 -0500	[thread overview]
Message-ID: <488E322E.2040503@codemonkey.ws> (raw)
In-Reply-To: <200807282140.56952.paul@codesourcery.com>

Paul Brook wrote:
> On Monday 28 July 2008, Anthony Liguori wrote:
>   
> Why would changing machine layout need to be able to override the ACPI table? 
> If the ACPI table doesn't match the emulated hardware that's a bug, and IMHO 
> having users supply their own tables is not a good way to fix that bug.
>   

Not everything in ACPI maps directly to emulated hardware.  The SMBIOS 
tables are a good example of this.

If I understand correctly, it's not uncommon for hardware manufactures 
to have a mostly static table, with sub-tables that are dynamically 
generated.  So we may create a mostly "static" table based on the chosen 
emulated hardware and then allow a user to fill in the sub tables.

Regards,

Anthony Liguori

> Paul
>   

  reply	other threads:[~2008-07-28 20:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 13:25 [Qemu-devel] [PATCH 0/3]: Add UUID command-line option Chris Lalancette
2008-07-28 14:15 ` [Qemu-devel] " Gleb Natapov
2008-07-28 14:37   ` Anthony Liguori
2008-07-28 14:41     ` Chris Lalancette
2008-07-28 15:02       ` Anthony Liguori
2008-07-28 15:09         ` Chris Lalancette
2008-07-28 15:12           ` Anthony Liguori
2008-07-28 15:42             ` Chris Lalancette
2008-07-28 16:02               ` Gleb Natapov
2008-07-28 16:17                 ` Anthony Liguori
2008-07-28 16:27                   ` Gleb Natapov
2008-07-28 17:41                     ` Blue Swirl
2008-07-28 16:28                   ` Jamie Lokier
2008-07-28 19:02                     ` Anthony Liguori
2008-07-28 20:00                       ` Jamie Lokier
2008-07-28 20:25                         ` Anthony Liguori
2008-07-28 20:40                           ` Paul Brook
2008-07-28 20:55                             ` Anthony Liguori [this message]
2008-07-29  6:31                           ` Gleb Natapov
2008-07-28 15:48             ` Jamie Lokier
2008-07-31 19:45               ` [Qemu-devel] " Sebastian Herbszt
2008-07-28 15:49             ` [Qemu-devel] " Jamie Lokier
2008-07-28 16:06               ` Anthony Liguori
2008-07-28 15:35     ` Gleb Natapov
2008-07-29 19:22       ` Anthony Liguori
2008-07-29 19:50         ` Gleb Natapov
2008-07-30 17:32           ` Blue Swirl
2008-08-05 14:33             ` Gleb Natapov
2008-08-06  2:35               ` Anthony Liguori
2008-08-06 16:26                 ` Blue Swirl
2008-08-06 16:33                   ` Anthony Liguori
2008-08-06 22:07                     ` [Qemu-devel] " Sebastian Herbszt
2008-08-06 22:11                       ` [Qemu-devel] " Anthony Liguori
2008-07-29  8:15     ` Daniel P. Berrange
2008-07-29  8:42       ` Chris Lalancette
2008-07-28 15:51   ` Jamie Lokier

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=488E322E.2040503@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=clalance@redhat.com \
    --cc=gleb@qumranet.com \
    --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).