summaryrefslogtreecommitdiff
path: root/arch/x86/pci/visws.c
diff options
context:
space:
mode:
authorSuresh Siddha <suresh.b.siddha@intel.com>2009-10-26 21:21:32 (GMT)
committerJesse Barnes <jbarnes@virtuousgeek.org>2009-11-04 16:47:22 (GMT)
commit2992e545ea006992ec9dc91c4fa996ce1e15f921 (patch)
tree5e3760376716e96d97e7533c01ffb52c4fb66d31 /arch/x86/pci/visws.c
parent9a007b3791cdba3601d835ea10e68c14115b9afb (diff)
downloadlinux-fsl-qoriq-2992e545ea006992ec9dc91c4fa996ce1e15f921.tar.xz
x86/PCI/PAT: return EINVAL for pci mmap WC request for !pat_enabled
Thomas Schlichter reported: > X.org uses libpciaccess which tries to mmap with write combining enabled via > /sys/bus/pci/devices/*/resource0_wc. Currently, when PAT is not enabled, the > kernel does fall back to uncached mmap. Then libpciaccess thinks it succeeded > mapping with write combining enabled and does not set up suited MTRR entries. > ;-( Instead of silently mapping pci mmap region as UC minus in the case of !pat_enabled and wc request, we can return error. Eric Anholt mentioned that caller (like X) typically follows up with UC minus pci mmap request and if there is a free mtrr slot, caller will manage adding WC mtrr. Jesse Barnes says: > Older versions of libpciaccess will behave better if we do it that way > (iirc it only allocates an MTRR if the resource_wc file doesn't exist or > fails to get mapped). Reported-by: Thomas Schlichter <thomas.schlichter@web.de> Signed-off-by: Thomas Schlichter <thomas.schlichter@web.de> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com> Acked-by: Eric Anholt <eric@anholt.net> Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'arch/x86/pci/visws.c')
0 files changed, 0 insertions, 0 deletions