diff options
author | Eric W. Biederman <ebiederm@xmission.com> | 2006-01-11 21:46:06 (GMT) |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-01-12 03:05:00 (GMT) |
commit | 1008fddcaed7ad3e69f72939c87b24d0d3387ca2 (patch) | |
tree | 916bb6d6d4a6e4ee6e92d936ec9ee322bbd6a7ed /include/asm-x86_64/mmu_context.h | |
parent | 60923df35edab273d0bd8e829cdfdc5cfbb4fd2c (diff) | |
download | linux-fsl-qoriq-1008fddcaed7ad3e69f72939c87b24d0d3387ca2.tar.xz |
[PATCH] x86_64: Memorize location of i8259 for reboots.
Currently we attempt to restore virtual wire mode on reboot, which only
works if we can figure out where the i8259 is connected. This is very
useful when we are kexec another kernel and likely helpful to an peculiar
BIOS that make assumptions about how the system is setup.
Since the acpi MADT table does not provide the location where the i8259 is
connected we have to look at the hardware to figure it out.
Most systems have the i8259 connected the local apic of the cpu so won't be
affected but people running Opteron and some serverworks chipsets should be
able to use kexec now.
In addition this patch removes the hard coded assumption that the io_apic
that delivers isa interrups is always known to the kernel as io_apic 0.
There does not appear to be anything to guarantee that assumption is true.
And From: Vivek Goyal <vgoyal@in.ibm.com>
A minor fix to the patch which remembers the location of where i8259 is
connected. Now counter i has been replaced by apic. counter i is having
some junk value which was leading to non-detection of i8259 connected to
IOAPIC.
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com>
Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'include/asm-x86_64/mmu_context.h')
0 files changed, 0 insertions, 0 deletions