[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH RFC] acpi: add reset register to fadt

From: Phil Dennis-Jordan
Subject: Re: [Qemu-devel] [PATCH RFC] acpi: add reset register to fadt
Date: Thu, 19 Jan 2017 19:09:47 +0100

On 18 January 2017 at 17:30, Michael S. Tsirkin <address@hidden> wrote:
> I think what's important is the Fadt format revision. That one was 1 for 1.0b 
> and 3 for 2.0.
> See page 112, Table 5-5 Fixed ACPI Description Table Format in acpi spec
> 1.0b.
> Now look at page 110 in spec 2.0, this time
> "Table 5-8 Fixed ACPI Description Table (FADT) Format".
> You will see that FADT revision is now 3, and there are a bunch of new
> fields after the reset register. I think you have to fill them in,
> you probably can get away with copying the non-extended values.

I've just spent a few hours fiddling around with this, and the results
aren't good. WinXP and 7 seem absolutely fine with a rev3 (or rev5)
FADT, presumably because they ignore it. macOS 10.12 hangs on boot
with a fully filled out r3/5 FADT. If I skip filling out the
Xdsdt/Xfacs addresses and just leave them at 0 it boots OK. Windows 10
hangs or bluescreens ("ACPI BIOS ERROR") in either case. (I tested
UEFI boot with OVMF, did not try legacy BIOS.)

Just in case I'd messed up the code, I also tried this FADT patch
from some months ago which evidently never got accepted. It yielded
the same result as my independently developed implementation.

I don't really know enough about ACPI to have an intuition for what to
try next. Unfortunately, macOS's ACPI table parser does not appear to
be in any of the open source bits of the xnu kernel, otherwise I'd be
looking there for hints.

For reference, my approach to filling out the Xdsdt/Xfacs fields in
build_fadt() is essentially the same as for the 32-bit variants from

unsigned xfacs_offset = (char *)&fadt->Xfacs - table_data->data;
        ACPI_BUILD_TABLE_FILE, xfacs_offset, sizeof(fadt->Xfacs),
        ACPI_BUILD_TABLE_FILE, facs_tbl_offset);

Suggestions welcome.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]