diff options
| author | Chris Wilson <[email protected]> | 2017-01-27 16:55:30 +0000 |
|---|---|---|
| committer | Chris Wilson <[email protected]> | 2017-01-31 11:16:07 +0000 |
| commit | c88473878d47131ccfc67a00ba688d4d7d0f4519 (patch) | |
| tree | 772660e15b308c4333da02d556840c71900b7327 /tools/perf/scripts/python | |
| parent | 4703b0472e126c715019a9671ea0fe38556114bb (diff) | |
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 <[email protected]>
Cc: Paulo Zanoni <[email protected]>
Cc: Ville Syrjälä <[email protected]>
Link: http://patchwork.freedesktop.org/patch/msgid/[email protected]
Reviewed-by: Paulo Zanoni <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions