aboutsummaryrefslogtreecommitdiffstats
path: root/arch/x86/kernel/amd_iommu.c
diff options
context:
space:
mode:
authorChris Wright <chrisw@sous-sol.org>2010-04-02 21:27:52 -0400
committerJoerg Roedel <joerg.roedel@amd.com>2010-04-07 05:50:50 -0400
commit75f66533bc883f761a7adcab3281fe3323efbc90 (patch)
treea659f19946c80e774e7b951d114a6416e5421849 /arch/x86/kernel/amd_iommu.c
parent8b408fe4f853dcfa18d133aa4cf1d7546b4c3870 (diff)
x86/amd-iommu: enable iommu before attaching devices
Hit another kdump problem as reported by Neil Horman. When initializaing the IOMMU, we attach devices to their domains before the IOMMU is fully (re)initialized. Attaching a device will issue some important invalidations. In the context of the newly kexec'd kdump kernel, the IOMMU may have stale cached data from the original kernel. Because we do the attach too early, the invalidation commands are placed in the new command buffer before the IOMMU is updated w/ that buffer. This leaves the stale entries in the kdump context and can renders device unusable. Simply enable the IOMMU before we do the attach. Cc: stable@kernel.org Cc: Neil Horman <nhorman@tuxdriver.com> Cc: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Chris Wright <chrisw@sous-sol.org> Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
Diffstat (limited to 'arch/x86/kernel/amd_iommu.c')
0 files changed, 0 insertions, 0 deletions