From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin O'Connor <kevin@koconnor.net>,
seabios@seabios.org, lersek@redhat.com, lists@philjordan.eu,
imammedo@redhat.com, phil@philjordan.eu,
programmingkidx@gmail.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [qemu PATCH for 2.10] i386: acpi: provide an XSDT instead of an RSDT
Date: Wed, 26 Jul 2017 16:24:41 -0400 (EDT) [thread overview]
Message-ID: <2080482614.19250435.1501100681184.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170726225402-mutt-send-email-mst@kernel.org>
> The point is that for PC we really should not keep piling up hacks,
> compatibility is more important.
Non-explosion of the test matrix is just as important.
> > Doing it for PC only would mean switching
> > back from FADT rev3 to rev1, which is worse for guest OS support,
>
> It's only OSX AFAIK and IIRC OSX doesn't run on PC anyway.
Sure it does. You can run it on VMware Workstation which emulates
some i440FX-like chipset.
> It's definitely way more code. I'll change my mind if there's
> a guest that needs the new FADT.
Then you can prepare a patch to revert the FADTv3 commit, or do the
work to make it specific to the 2.10 Q35 machine type.
Paolo
next prev parent reply other threads:[~2017-07-26 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 9:31 [Qemu-devel] [qemu PATCH for 2.10] i386: acpi: provide an XSDT instead of an RSDT Paolo Bonzini
2017-07-26 12:52 ` Michael S. Tsirkin
2017-07-26 13:01 ` Paolo Bonzini
2017-07-26 20:17 ` Michael S. Tsirkin
2017-07-26 20:24 ` Paolo Bonzini [this message]
2017-07-26 20:30 ` Michael S. Tsirkin
2017-07-26 13:07 ` Daniel P. Berrange
2017-07-26 13:19 ` Michael S. Tsirkin
2017-07-27 20:40 ` Kevin O'Connor
2017-07-28 14:20 ` Laszlo Ersek
2017-07-29 2:36 ` Kevin O'Connor
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=2080482614.19250435.1501100681184.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=imammedo@redhat.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=lists@philjordan.eu \
--cc=mst@redhat.com \
--cc=phil@philjordan.eu \
--cc=programmingkidx@gmail.com \
--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).