qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: ghammer@redhat.com, imammedo@redhat.com, qemu-devel@nongnu.org,
	shannon.zhao@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2 0/4]  acpi: xsdt support
Date: Tue, 09 Jun 2015 16:02:08 +0200	[thread overview]
Message-ID: <5576F1E0.9050504@redhat.com> (raw)
In-Reply-To: <20150609112550-mutt-send-email-mst@redhat.com>

On 06/09/15 11:49, Michael S. Tsirkin wrote:
> On Tue, Jun 09, 2015 at 02:02:31AM -0400, Paolo Bonzini wrote:
>> I would just patch OVMF to ignore the RSDT if there is an XSDT.
>>
>> Alternatively, can you check for ACPI 2.0 support via _OSI, and load the ACPI 2.0 bits via LoadTable? Hopefully XP does not BSOD if the invalid (for ACPI 1.0) opcodes are in a Then block or in a separate method... Then you can use just an RSDT.
>>
>> Paolo
> 
> 
> So it's even easier. The following doesn't crash XP:
> 
>             Method(ADDR, 0, Serialized) {
> 		/* Region is local to method to avoid crashing ACPI 1.0 guests */
>                 DataTableRegion(IDPT, "UEFI", "BXPC", "VMGENI");
> 	        Field (IDPT, AnyAcc, NoLock, Preserve) {
> 		  Offset (54),
> 		  VGIA, 64     // address of "etc/acpi/vmgenid" blob
> 	        }
> 		Return(Add(VGIA), 40);
>             }
> 
> Simply because XP doesn't ever call ADDR.
> Method must be serialized since attempts to create two
> regions or fields with the same name would crash OSPM.

That sounds like a huge relief to me, so thank you for researching it.

Laszlo

  reply	other threads:[~2015-06-09 14:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 18:14 [Qemu-devel] [PATCH v2 0/4] acpi: xsdt support Michael S. Tsirkin
2015-06-08 18:14 ` [Qemu-devel] [PATCH v2 1/4] acpi: add API for 64 bit offsets Michael S. Tsirkin
2015-06-08 18:14 ` [Qemu-devel] [PATCH v2 2/4] i386/acpi: collect 64 bit offsets for xsdt Michael S. Tsirkin
2015-06-08 18:14 ` [Qemu-devel] [PATCH v2 3/4] i386/acpi: add XSDT Michael S. Tsirkin
2015-06-08 18:14 ` [Qemu-devel] [PATCH v2 4/4] acpi: unify rsdp generation Michael S. Tsirkin
2015-06-09  0:08 ` [Qemu-devel] [PATCH v2 0/4] acpi: xsdt support Laszlo Ersek
2015-06-09  5:31   ` Michael S. Tsirkin
2015-06-09  6:02     ` Paolo Bonzini
2015-06-09  6:35       ` Michael S. Tsirkin
2015-06-09  6:38         ` Michael S. Tsirkin
2015-06-09  7:41           ` Laszlo Ersek
2015-06-09  8:34             ` Michael S. Tsirkin
2015-06-09 14:01               ` Laszlo Ersek
2015-06-09  9:39         ` Igor Mammedov
2015-06-09  9:10       ` Michael S. Tsirkin
2015-06-09  9:49       ` Michael S. Tsirkin
2015-06-09 14:02         ` Laszlo Ersek [this message]
2015-06-09 14:05           ` Michael S. Tsirkin
2015-08-27 14:27             ` Laszlo Ersek
2015-08-27 17:58               ` Michael S. Tsirkin
2015-08-28  6:23                 ` Laszlo Ersek

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=5576F1E0.9050504@redhat.com \
    --to=lersek@redhat.com \
    --cc=ghammer@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.zhao@linaro.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).