[Xen-devel] [PATCH 1/9] xen/dom0: handle acpi lapic parsing in Xen dom0

[Jeremy Fitzhardinge <jeremy@xxxxxxxx>]

When running in Xen dom0, we still want to parse the ACPI tables to
find out about local and IO apics, but we don't want to actually use
the lapics.

Put a couple of tests for Xen to prevent lapics from being mapped or
accessed.  This is very Xen-specific behaviour, so there didn't seem to
be any point in adding more indirection.

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>
---
 arch/x86/kernel/acpi/boot.c |   10 ++++++++++
 1 files changed, 10 insertions(+), 0 deletions(-)

diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
index 956c1de..32bacfe 100644
--- a/arch/x86/kernel/acpi/boot.c
+++ b/arch/x86/kernel/acpi/boot.c
@@ -42,6 +42,8 @@
 #include <asm/mpspec.h>
 #include <asm/smp.h>
 
+#include <asm/xen/hypervisor.h>
+
 static int __initdata acpi_force = 0;
 u32 acpi_rsdt_forced;
 #ifdef CONFIG_ACPI
@@ -219,6 +221,10 @@ static void __cpuinit acpi_register_lapic(int id, u8 
enabled)
 {
        unsigned int ver = 0;
 
+       /* We don't want to register lapics when in Xen dom0 */
+       if (xen_initial_domain())
+               return;
+
        if (!enabled) {
                ++disabled_cpus;
                return;
@@ -755,6 +761,10 @@ static int __init acpi_parse_fadt(struct acpi_table_header 
*table)
 
 static void __init acpi_register_lapic_address(unsigned long address)
 {
+       /* Xen dom0 doesn't have usable lapics */
+       if (xen_initial_domain())
+               return;
+
        mp_lapic_addr = address;
 
        set_fixmap_nocache(FIX_APIC_BASE, address);
-- 
1.6.0.6


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel