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

Sorry about replying to myself...

On 06/10/13 22:43, Laszlo Ersek wrote:

> It's not a design purity argument, just what's cheaper.

You probably consider SMBIOS/ACPI table generation "guest code" that has
no place in the machine emulator. You're likely willing to expose the
needed bits on a case-by-case basis, in their barest representation.

I must consider the entire stack, from the libvirt top, down to the
guest kernel or root shell, and see where it is cheapest to effect
changes. The higher I can hoist something the better.

Modulo, it depends on what element of the stack people think of as
central / indispensable -- that element should support the feature directly.

(Returning to my earlier example, it would be theoretically viable *I
guess* to equip libvirt to pre-format a Type 3 SMBIOS blob in a file,
and pass it with "-smbios file=...", but many people don't use libvirt.
It also might not apply to other emulators supported by libvirt.)

Thanks,
Laszlo

  reply	other threads:[~2013-06-10 21:13 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 [this message]
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
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=51B641C8.2050501@redhat.com \
    --to=lersek@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=dwmw2@infradead.org \
    --cc=jljusten@gmail.com \
    --cc=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=mst@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).