search for: irq_32

...86/include/asm/tlbflush.h | 8 ++-- arch/x86/include/asm/uv/uv_bau.h | 3 +- arch/x86/kernel/cpu/intel_cacheinfo.c | 63 ++++++++++++++++------- arch/x86/kernel/cpu/mcheck/mce_amd_64.c | 21 +++++--- arch/x86/kernel/io_apic.c | 20 ++++---- arch/x86/kernel/irq_32.c | 2 +- arch/x86/kernel/irq_64.c | 2 +- arch/x86/kernel/microcode_core.c | 74 ++++++++++++++++---------- arch/x86/kernel/tlb_32.c | 67 ++++++++++-------------- arch/x86/kernel/tlb_64.c | 62 ++++++++++++---------- a...

...86/include/asm/tlbflush.h | 8 ++-- arch/x86/include/asm/uv/uv_bau.h | 3 +- arch/x86/kernel/cpu/intel_cacheinfo.c | 63 ++++++++++++++++------- arch/x86/kernel/cpu/mcheck/mce_amd_64.c | 21 +++++--- arch/x86/kernel/io_apic.c | 20 ++++---- arch/x86/kernel/irq_32.c | 2 +- arch/x86/kernel/irq_64.c | 2 +- arch/x86/kernel/microcode_core.c | 74 ++++++++++++++++---------- arch/x86/kernel/tlb_32.c | 67 ++++++++++-------------- arch/x86/kernel/tlb_64.c | 62 ++++++++++++---------- a...

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine