summaryrefslogtreecommitdiffstats
path: root/arch/x86/kernel/stacktrace.c
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2017-01-27 16:55:30 +0000
committerChris Wilson <chris@chris-wilson.co.uk>2017-01-31 11:16:07 +0000
commitc88473878d47131ccfc67a00ba688d4d7d0f4519 (patch)
tree772660e15b308c4333da02d556840c71900b7327 /arch/x86/kernel/stacktrace.c
parent4703b0472e126c715019a9671ea0fe38556114bb (diff)
downloadblackbird-op-linux-c88473878d47131ccfc67a00ba688d4d7d0f4519.tar.gz
blackbird-op-linux-c88473878d47131ccfc67a00ba688d4d7d0f4519.zip
drm/i915: Treat stolen memory as DMA addresses
The conversion of stolen to use phys_addr_t (from essentially u32) sparked an interesting discussion. We treat stolen memory as only accessible from the GPU (the DMA device) - an attempt to use it from the CPU will generate a MCE on gen6 onwards, although it is in theory a physical address that can be dereferenced from the CPU as demonstrated by earlier generations. As such, using phys_addr_t has the wrong connotations and as we pass the address into the DMA device via dma_addr_t (through the scatterlists used to program the GTT entries), we should treat it as dma_addr_t throughout. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Paulo Zanoni <paulo.r.zanoni@intel.com> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/20170127165531.28135-1-chris@chris-wilson.co.uk Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Diffstat (limited to 'arch/x86/kernel/stacktrace.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud