2015年2月12日 · Xen also supports three CPU drivers: ACPI (IA32) for Intel x86 processor; ACPI (IA64) for Intel Itanium processor and PowerNow K8 for AMD processor. Domain0 has two components: ACPI parser and xenpm tool. ACPI parser parses ACPI table and pass the information to hypervisor cpufreq core.

2016年12月6日 · Xen Project 4.8 ARM DomU ACPI support is now able to build ARM64 guests with ACPI support, such as Red Hat Enterprise Linux Server for ARM Development Preview (available via Partner Early Access Program). It can also run unmodified Xen on ARM.

The Xen Environment Table: This specification lays out the structure and content of a new ACPI table – the Xen Environment Table (XENV). This table, while not currently part of the ACPI specification, may or may not become part of the specification at a later date.

Using acpi=ht causes Xen to parse the ACPI tables enough to enumerate all CPUs, but will not use other ACPI features. This is not common, and only has an effect if your system is blacklisted. The acpi=noirq option causes Xen to not parse the ACPI MADT table looking for IO-APIC entries.

* This can happen with incorrect ACPI SSDT declerations. */ if (acpi_id >= nr_acpi_bits) { pr_debug ("max acpi id %u, trying to set %u\n", nr_acpi_bits - 1, acpi_id); return AE_OK; } /* …

2016年3月4日 · ARM64: ACPI: Check if it runs on Xen to enable or disable ACPI. ARM: Xen: Document UEFI support on Xen ARM virtual platforms. XEN: EFI: Move x86 specific codes to architecture directory. ARM64: XEN: Add a function to initialize Xen specific UEFI runtime. services. FDT: Add a helper to get the subnode by given name.

> xen_guest_init, call only the one that applies. The acpi init function. > could be ifdef'ed CONFIG_ACPI. Making sure that acpi_disabled is 1 when. > !CONFIG_ACPI, we could even avoid all ifdef's from xen_guest_init. Sure, will fix. Thanks. > The rest is good, thanks. >> + ? ACPI_EDGE_SENSITIVE. >> + ? ACPI_ACTIVE_LOW. > .

I'm not sure if> that's what you want?> > It might be better to add a check to acpi_bus_type_and_status () that will> evaluate the "should ignore?" thing and return -ENODEV if this is true.

Each node contains the following properties: - compatible "xen,guest-acpi", "multiboot,module" - reg Specifies the physical address and the length of the module. RSDP table is always located at the beginning of this region.

The reason for all of this is that Linux does not talk to the BIOS directly - instead it simply walks through the necessary ACPI methods and then issues hypercall to Xen which then further completes the remaining suspend steps.