summaryrefslogtreecommitdiff
path: root/firmware/atmsar11.HEX
diff options
context:
space:
mode:
authorDan Williams <dan.j.williams@intel.com>2010-07-23 15:47:56 -0700
committerDan Williams <dan.j.williams@intel.com>2010-08-04 14:18:17 -0700
commit556ab45f9a775bfa4762bacc0a4afb5b44b067bc (patch)
tree6caf3f7c72617d50d78c4197b872fd0a22b18c99 /firmware/atmsar11.HEX
parent128f904ac87cb6e63921e80f378fdf9ba532c0f6 (diff)
downloadlinux-3.10-556ab45f9a775bfa4762bacc0a4afb5b44b067bc.tar.gz
linux-3.10-556ab45f9a775bfa4762bacc0a4afb5b44b067bc.tar.bz2
linux-3.10-556ab45f9a775bfa4762bacc0a4afb5b44b067bc.zip
ioat2: catch and recover from broken vtd configurations v6
On some platforms (MacPro3,1) the BIOS assigns the ioatdma device to the incorrect iommu causing faults when the driver initializes. Add a quirk to catch this misconfiguration and try falling back to untranslated operation (which works in the MacPro3,1 case). Assuming there are other platforms with misconfigured iommus teach the ioatdma driver to treat initialization failures as non-fatal (just fail the driver load and emit a warning instead of triggering a BUG_ON). This can be classified as a boot regression since 2.6.32 on affected platforms since the ioatdma module did not autoload prior to that kernel. Cc: <stable@kernel.org> Acked-by: David Woodhouse <David.Woodhouse@intel.com> Reported-by: Chris Li <lkml@chrisli.org> Tested-by: Chris Li <lkml@chrisli.org> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'firmware/atmsar11.HEX')
0 files changed, 0 insertions, 0 deletions