summaryrefslogtreecommitdiff
path: root/drivers/net
diff options
context:
space:
mode:
authorSuresh Siddha <suresh.b.siddha@intel.com>2010-12-06 12:26:30 -0800
committerGreg Kroah-Hartman <gregkh@suse.de>2011-01-07 13:58:34 -0800
commitcc1bdf49cfe22fe5f549126d9e3e1f5e754c1797 (patch)
tree394622302a9b6810279a76d9b8e948288c2e4430 /drivers/net
parentf6e0591560cf3add6ee845cbde0825177044ca63 (diff)
x86, vt-d: Quirk for masking vtd spec errors to platform error handling logic
commit 254e42006c893f45bca48f313536fcba12206418 upstream. On platforms with Intel 7500 chipset, there were some reports of system hang/NMI's during kexec/kdump in the presence of interrupt-remapping enabled. During kdump, there is a window where the devices might be still using old kernel's interrupt information, while the kdump kernel is coming up. This can cause vt-d faults as the interrupt configuration from the old kernel map to null IRTE entries in the new kernel etc. (with out interrupt-remapping enabled, we still have the same issue but in this case we will see benign spurious interrupt hit the new kernel). Based on platform config settings, these platforms seem to generate NMI/SMI when a vt-d fault happens and there were reports that the resulting SMI causes the system to hang. Fix it by masking vt-d spec defined errors to platform error reporting logic. VT-d spec related errors are already handled by the VT-d OS code, so need to report the same error through other channels. Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com> LKML-Reference: <1291667190.2675.8.camel@sbsiddha-MOBL3.sc.intel.com> Reported-by: Max Asbock <masbock@linux.vnet.ibm.com> Reported-and-tested-by: Takao Indoh <indou.takao@jp.fujitsu.com> Acked-by: Chris Wright <chrisw@sous-sol.org> Acked-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions