qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	phil@philjordan.eu, seabios@seabios.org, qemu-devel@nongnu.org,
	programmingkidx@gmail.com, Kevin O'Connor <kevin@koconnor.net>,
	kraxel@redhat.com, lists@philjordan.eu, imammedo@redhat.com,
	lersek@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 14:07:13 +0100	[thread overview]
Message-ID: <20170726130713.GL7620@redhat.com> (raw)
In-Reply-To: <20170726155118-mutt-send-email-mst@kernel.org>

On Wed, Jul 26, 2017 at 03:52:43PM +0300, Michael S. Tsirkin wrote:
> On Wed, Jul 26, 2017 at 11:31:36AM +0200, Paolo Bonzini wrote:
> > The tables that QEMU provides are not ACPI 1.0 compatible since commit
> > 77af8a2b95 ("hw/i386: Use Rev3 FADT (ACPI 2.0) instead of Rev1 to improve
> > guest OS support.", 2017-05-03).  This is visible with Windows 2000,
> > which refuses to parse the rev3 FADT and fails to boot.
> > 
> > The recommended solution in this case is to build two FADTs, v1 being
> > pointed to by the RSDT and v3 by the XSDT.  However, we leave this task
> > to the firmware.  This patch simply switches the RSDT to the XSDT, which
> > is valid for all ACPI 2.0-friendly operating systems and also leaves
> > SeaBIOS the freedom to build an RSDT that points to the compatibility
> > FADT.
> > 
> > When running Windows 2000 with an old BIOS, Windows would simply fall
> > back to a non-ACPI HAL; however, the plan should be to include a BIOS with
> > the new feature in 2.10.
> > 
> > Reported-by: Programmingkid <programmingkidx@gmail.com>
> > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> 
> I'm not against this but let's do it for q35 only please. PC is a legacy
> machine type and let's just leave it alone.

We've already touched the PC machine type in 77af8a2b95 and that needs
fixing to deal with the regressions it caused. Even if you call it
"legacy", the PC machine is used by the vast majority of deployments
that exist today & likely to be done for the foreseeable future too.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  parent reply	other threads:[~2017-07-26 13:07 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
2017-07-26 20:30         ` Michael S. Tsirkin
2017-07-26 13:07   ` Daniel P. Berrange [this message]
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=20170726130713.GL7620@redhat.com \
    --to=berrange@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=pbonzini@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).