[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1334601616-25309-1-git-send-email-konrad.wilk@oracle.com>
Date: Mon, 16 Apr 2012 14:40:13 -0400
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: linux-kernel@...r.kernel.org, mingo@...nel.org
Cc: xen-devel@...ts.xensource.com, suresh.b.siddha@...el.com,
hpa@...or.com, hpa@...or.co, tglx@...utronix.de
Subject: [GIT PULL] (xen) for stable/for-ingo-v3.5.v3 for v3.5
Hey Ingo,
Please git pull the following branch for v3.5:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-ingo-v3.5.v3
It has the proper fix for the IO-APIC having 0xfffff... contents when booting under Xen.
Compared to the patch you have already in the tree (136d249ef7dbf0fefa292082cc40be1ea864cbd6
x86/ioapic: Add io_apic_ops driver layer to allow interception) it does three things:
1) Exposes the io_apic baremetal functions and uses the x86_io_apic_ops function table
instead of keeping it in the io_apic. This makes the code fit within the rest of
x86_ops functions.
2) Use the x86_io_apic_ops to re-direct the (*read) to the Xen emulated one.
3) Removes the work-around.
Please note, that the existing interface (136d249) can be used to do 2) as well. But the
1) makes the code more uniform by putting the function table redirection in the same
location.
Thank you!
Konrad Rzeszutek Wilk (3):
x86/apic: Replace io_apic_ops with x86_io_apic_ops.
xen/x86: Implement x86_apic_ops
Revert "xen/x86: Workaround 'x86/ioapic: Add register level checks to detect bogus io-apic entries'"
arch/x86/include/asm/io_apic.h | 35 +++++++++++++++++++----------
arch/x86/include/asm/x86_init.h | 9 ++++++-
arch/x86/kernel/apic/io_apic.c | 46 +++-----------------------------------
arch/x86/kernel/setup.c | 2 +-
arch/x86/kernel/x86_init.c | 8 ++++++
arch/x86/xen/Makefile | 2 +-
arch/x86/xen/apic.c | 17 ++++++++++++++
arch/x86/xen/enlighten.c | 2 +
arch/x86/xen/mmu.c | 4 +--
arch/x86/xen/xen-ops.h | 4 +++
10 files changed, 69 insertions(+), 60 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists