qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	David Woodhouse <dwmw2@infradead.org>,
	seabios@seabios.org, qemu-devel <qemu-devel@nongnu.org>,
	Kevin O'Connor <kevin@koconnor.net>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Jordan Justen <jljusten@gmail.com>,
	Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qemu: piix: PCI bridge ACPI hotplug support
Date: Tue, 11 Jun 2013 10:35:48 +0300	[thread overview]
Message-ID: <20130611073548.GE31474@redhat.com> (raw)
In-Reply-To: <CA+aC4kv-mhbWXgSmtGgs3gQHaeTWpssDr2VJ8MtTrefcOs7Y7g@mail.gmail.com>

On Mon, Jun 10, 2013 at 08:03:46PM -0500, Anthony Liguori wrote:
> >> It is not "supported" by QEMU.
> >
> > No, but I've always thought that QEMU was happy to have alternative
> > firmware projects.
> 
> We are and we're happy to accept patches to enable things even if its
> proprietary.  But that's all assuming we're improving hardware
> emulation.
> 
> What we're talking about here is doing something that's very un-hardware like.

Two points
1. You never explained what you mean by un-hardware like.

   Currently bios is in a ROM device, and it has a
   template for ACPI tables together with it.
   This simply moves the tables to a separate ROM
   device (FW CFG), and generalizes the template using
   the linker interface.
   One ROM is hardware-like but two is un-hardware like?

   ACPI tables are static so it's likely lots of
   hardware has at least some of them pre-formatted in flash,
   then tweak some things like SRAT a bit.

2. There's no hardware-like alternative.

   A current alternative is exposing lots of PV interfaces to bios,
   bios builds up ACPI tables based on them.
   All of this code is in practice PC only,
   if we ever attempt to generalize we'll see how
   the interfaces are not a good match.
   They are still PV, poorly documented and it's very hard for
   bios not to make any assumptions about them.
   When it does, result is a very obscure breakage.

   Yes, building tables in bios means
   QEMU code is simpler but we double the
   amount of interfaces that we need to get right:
   QEMU-BIOS + BIOS-OS

   Yes it's "not QEMU code" but it's seen as
   a single package by users and it does not really
   matter - excellent hardware with lousy firmware is
   useless.

-- 
MST

  parent reply	other threads:[~2013-06-11  7:35 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 16:41 [Qemu-devel] [PATCH] qemu: piix: PCI bridge ACPI hotplug support Michael S. Tsirkin
2013-06-10 18:58 ` Anthony Liguori
2013-06-10 19:17   ` Peter Maydell
2013-06-10 19:50     ` Anthony Liguori
2013-06-10 19:43   ` Laszlo Ersek
2013-06-10 19:57     ` Anthony Liguori
2013-06-10 20:43       ` Laszlo Ersek
2013-06-10 21:14         ` Laszlo Ersek
2013-06-10 21:45         ` Anthony Liguori
2013-06-10 23:05           ` Kevin O'Connor
2013-06-10 23:34             ` Anthony Liguori
2013-06-10 23:52               ` David Woodhouse
2013-06-11  0:11                 ` Anthony Liguori
2013-06-11 14:11                   ` David Woodhouse
2013-06-11  0:23               ` Kevin O'Connor
2013-06-11  0:51                 ` Anthony Liguori
2013-06-11  1:19                   ` Kevin O'Connor
2013-06-11  1:25                     ` Anthony Liguori
2013-06-11  1:49                       ` Kevin O'Connor
2013-06-11  6:49                       ` Michael S. Tsirkin
2013-06-11  0:28           ` Jordan Justen
2013-06-11  1:03             ` Anthony Liguori
2013-06-11  1:32               ` Jordan Justen
2013-06-11  7:35               ` Michael S. Tsirkin [this message]
2013-06-13 23:05                 ` Paolo Bonzini
2013-06-14  0:59                   ` Anthony Liguori
2013-06-14  1:23                     ` [Qemu-devel] [SeaBIOS] " Peter Stuge
2013-06-11 14:04               ` David Woodhouse
2013-06-13 23:02               ` [Qemu-devel] " Paolo Bonzini
2013-06-14  0:26                 ` Laszlo Ersek
2013-06-16 10:00                   ` Laszlo Ersek
2013-06-11  5:22   ` Michael S. Tsirkin
2013-06-11  5:33 ` Gerd Hoffmann
2013-06-11  6:55   ` Michael S. Tsirkin
2013-06-11  7:42     ` Gerd Hoffmann
2013-06-11  7:53       ` Michael S. Tsirkin
2013-06-11  8:00         ` Gerd Hoffmann
2013-06-11  8:18           ` Michael S. Tsirkin
2013-06-11  8:27             ` Michael S. Tsirkin

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=20130611073548.GE31474@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=dwmw2@infradead.org \
    --cc=jljusten@gmail.com \
    --cc=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).