From: kaf24@firebug.cl.cam.ac.uk Date: Tue, 23 Aug 2005 09:49:12 +0000 (+0000) Subject: This patch extends I/O APIC guest writes so that the correct destination X-Git-Tag: archive/raspbian/4.8.0-1+rpi1~1^2~16871^2~3^2~9 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=88ec00fa72c0fc1206c02fedace20b6a04dd7299;p=xen.git This patch extends I/O APIC guest writes so that the correct destination fields are written in the redirection table entry. Signed-off-by: Aravindh Puthiyaparambil --- diff --git a/xen/arch/x86/io_apic.c b/xen/arch/x86/io_apic.c index db3cd010a8..7dd6bd590a 100644 --- a/xen/arch/x86/io_apic.c +++ b/xen/arch/x86/io_apic.c @@ -1751,8 +1751,30 @@ int ioapic_guest_write(int apicid, int address, u32 val) pin = (address - 0x10) >> 1; + *(u32 *)&rte = val; rte.dest.logical.logical_dest = cpu_mask_to_apicid(TARGET_CPUS); - *(int *)&rte = val; + + /* + * What about weird destination types? + * SMI: Ignore? Ought to be set up by the BIOS. + * NMI: Ignore? Watchdog functionality is Xen's concern. + * INIT: Definitely ignore: probably a guest OS bug. + * ExtINT: Ignore? Linux only asserts this at start of day. + * For now, print a message and return an error. We can fix up on demand. + */ + if ( rte.delivery_mode > dest_LowestPrio ) + { + printk("ERROR: Attempt to write weird IOAPIC destination mode!\n"); + printk(" APIC=%d/%d, lo-reg=%x\n", apicid, pin, val); + return -EINVAL; + } + + /* + * The guest does not know physical APIC arrangement (flat vs. cluster). + * Apply genapic conventions for this platform. + */ + rte.delivery_mode = INT_DELIVERY_MODE; + rte.dest_mode = INT_DEST_MODE; if ( rte.vector >= FIRST_DEVICE_VECTOR ) {