diff options
| author | Suresh Siddha <suresh.b.siddha@intel.com> | 2012-08-08 23:16:52 +0400 |
|---|---|---|
| committer | H. Peter Anvin <hpa@zytor.com> | 2012-08-14 20:52:20 +0400 |
| commit | f1c6300183dbf5b9da25988e13f6f25a9e27151b (patch) | |
| tree | bce55a9a73b8f95509096a6d49f12d93782cab2f /init/main.c | |
| parent | 484d90eec884d814b005c9736bcf3fd018acba65 (diff) | |
| download | linux-f1c6300183dbf5b9da25988e13f6f25a9e27151b.tar.xz | |
x86, apic: fix broken legacy interrupts in the logical apic mode
Recent commit 332afa656e76458ee9cf0f0d123016a0658539e4 cleaned up
a workaround that updates irq_cfg domain for legacy irq's that
are handled by the IO-APIC. This was assuming that the recent
changes in assign_irq_vector() were sufficient to remove the workaround.
But this broke couple of AMD platforms. One of them seems to be
sending interrupts to the offline cpu's, resulting in spurious
"No irq handler for vector xx (irq -1)" messages when those cpu's come online.
And the other platform seems to always send the interrupt to the last logical
CPU (cpu-7). Recent changes had an unintended side effect of using only logical
cpu-0 in the IO-APIC RTE (during boot for the legacy interrupts) and this
broke the legacy interrupts not getting routed to the cpu-7 on the AMD
platform, resulting in a boot hang.
For now, reintroduce the removed workaround, (essentially not allowing the
vector to change for legacy irq's when io-apic starts to handle the irq. Which
also addressed the uninteded sife effect of just specifying cpu-0 in the
IO-APIC RTE for those irq's during boot).
Reported-and-tested-by: Robert Richter <robert.richter@amd.com>
Reported-and-tested-by: Borislav Petkov <bp@amd64.org>
Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
Link: http://lkml.kernel.org/r/1344453412.29170.5.camel@sbsiddha-desk.sc.intel.com
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Diffstat (limited to 'init/main.c')
0 files changed, 0 insertions, 0 deletions