summaryrefslogtreecommitdiff
path: root/crypto/internal.h
diff options
context:
space:
mode:
authorDavid Woodhouse <dwmw2@infradead.org>2009-02-13 23:18:03 (GMT)
committerIngo Molnar <mingo@elte.hu>2009-02-14 21:47:09 (GMT)
commit9af88143b277f52fc6ce0d69137f435c73c39c1a (patch)
treec382fdc5c8a1aa2860c03e52ea9341bb30207a18 /crypto/internal.h
parent2fff78c784ed97a8e5aa225ef5228f0a6d862d82 (diff)
downloadlinux-9af88143b277f52fc6ce0d69137f435c73c39c1a.tar.xz
iommu: fix Intel IOMMU write-buffer flushing
This is the cause of the DMA faults and disk corruption that people have been seeing. Some chipsets neglect to report the RWBF "capability" -- the flag which says that we need to flush the chipset write-buffer when changing the DMA page tables, to ensure that the change is visible to the IOMMU. Override that bit on the affected chipsets, and everything is happy again. Thanks to Chris and Bhavesh and others for helping to debug. Should resolve: https://bugzilla.redhat.com/show_bug.cgi?id=479996 http://bugzilla.kernel.org/show_bug.cgi?id=12578 Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Tested-and-acked-by: Chris Wright <chrisw@sous-sol.org> Reviewed-by: Bhavesh Davda <bhavesh@vmware.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'crypto/internal.h')
0 files changed, 0 insertions, 0 deletions