search for: dump_ioapic_irq_info

The formatting of the IO-APIC debug key info has niggled me for a while, and with the latest interrupt bug I am chasing, has finally motivated me to fix it. The attached patch causes all columns to line up, and removes the comma which served no purpose in combination with the spaces already present. -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900,

...8,7 +18,6 @@ extern const struct genapic apic_summit; extern const struct genapic apic_bigsmp; -extern const struct genapic apic_default; const struct genapic *__read_mostly genapic; --- 2011-03-09.orig/xen/arch/x86/io_apic.c +++ 2011-03-09/xen/arch/x86/io_apic.c @@ -2491,8 +2491,6 @@ void dump_ioapic_irq_info(void) } } -unsigned highest_gsi(void); - static unsigned int __initdata max_gsi_irqs; integer_param("max_gsi_irqs", max_gsi_irqs); --- 2011-03-09.orig/xen/arch/x86/mpparse.c +++ 2011-03-09/xen/arch/x86/mpparse.c @@ -21,7 +21,6 @@ #include <xen/delay.h> #include <xen...

...UESTS-i-1); action->nr_guests--; @@ -661,7 +694,8 @@ void pirq_guest_unbind(struct domain *d, desc->handler->shutdown(vector); out: - spin_unlock_irqrestore(&desc->lock, flags); + spin_unlock_irqrestore(&desc->lock, flags); + return rc; } extern void dump_ioapic_irq_info(void); diff -r 7750906b06b3 -r 31f09a5e24cf xen/arch/x86/msi.c --- a/xen/arch/x86/msi.c Wed Sep 24 10:23:51 2008 +0100 +++ b/xen/arch/x86/msi.c Wed Sep 24 12:36:55 2008 +0100 @@ -727,7 +727,6 @@ void pci_disable_msi(int vector) __pci_disable_msix(vector); } -extern struct h...

There is a BUG_ON() at xen/arch/x86/physdev.c:169 which appears to be dependent upon guest behavior (should close event channel before un-mapping pirq), rather than on internal hypervisor state. In 2.6.18, this likely goes unnoticed because pci_device_shutdown() only calls all the driver shutdown routines. In newer kernels, however, it also calls pci_msi_shutdown() and pci_msix_shutdown(), which

This patch set adds XSM security labels to useful debugging output locations, and fixes some assumptions that all interrupts behaved like GSI interrupts (which had useful non-dynamic IDs). It also cleans up the policy build process and adds an example of how to use the user field in the security context. Debug output: [PATCH 01/10] xsm: Add security labels to event-channel dump [PATCH 02/10] xsm: