|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] [PATCH] hvmloader: add "wakeup from S4 on RTC alarm" bit to
# HG changeset patch
# User Paolo Bonzini <pbonzini@xxxxxxxxxx>
# Date 1296827299 -3600
# Node ID c923816861a96328aaf3d5ba8939fd9b4c441cd0
# Parent 4cd3bd56fc0343031085b7e466e3022816b1b5dc
hvmloader: add "wakeup from S4 on RTC alarm" bit to ACPI FADT
Testing Xen with Microsoft's Windows logo tests reveals a non-fatal
failure in the "CHAOS" test (more precisely in the PwrTest subjob).
The test expects to be able to hibernate the machine and have it
power up again via the RTC. We do not really care about implementing
the exact timing in the management (and neither does MS) so their
request can be easily by manually restarting the VM or even via
on_poweroff="restart" (granted, that's not something you'd usually do).
Ok?
Paolo
diff --git a/tools/firmware/hvmloader/acpi/static_tables.c
b/tools/firmware/hvmloader/acpi/static_tables.c
--- a/tools/firmware/hvmloader/acpi/static_tables.c
+++ b/tools/firmware/hvmloader/acpi/static_tables.c
@@ -71,7 +71,8 @@ struct acpi_20_fadt Fadt = {
.flags = (ACPI_PROC_C1 |
ACPI_WBINVD |
ACPI_FIX_RTC | ACPI_TMR_VAL_EXT |
- ACPI_USE_PLATFORM_CLOCK),
+ ACPI_USE_PLATFORM_CLOCK |
+ ACPI_RTC_S4),
.reset_reg = {
.address_space_id = ACPI_SYSTEM_IO,
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [PATCH] hvmloader: add "wakeup from S4 on RTC alarm" bit to ACPI FADT,
Paolo Bonzini <=
|
|
|
|
|