diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2020-05-04 17:06:29 +0300 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2020-05-04 17:15:04 +0300 |
commit | e3d291301f99ef98d71bf858478bd4a3c5525bfe (patch) | |
tree | 55d477512b601e3ce49bba5722f080469e03abbf /crypto/twofish_common.c | |
parent | f5b62bdbb6262de1c46205cd4167b4e90cb0d4cf (diff) | |
download | linux-e3d291301f99ef98d71bf858478bd4a3c5525bfe.tar.xz |
drm/i915/gem: Implement legacy MI_STORE_DATA_IMM
The older arches did not convert MI_STORE_DATA_IMM to using the GTT, but
left them writing to a physical address. The notes suggest that the
primary reason would be so that the writes were cache coherent, as the
CPU cache uses physical tagging. As such we did not implement the
legacy variant of MI_STORE_DATA_IMM and so left all the relocations
synchronous -- but with a small function to convert from the vma address
into the physical address, we can implement asynchronous relocs on these
older arches, fixing up a few tests that require them.
In order to be able to test the legacy paths, refactor the gpu
relocations so that we can hook them up to a selftest.
v2: Use an array of offsets not enum labels for the selftest
v3: Refactor the common igt_hexdump()
Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/757
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20200504140629.28240-1-chris@chris-wilson.co.uk
Diffstat (limited to 'crypto/twofish_common.c')
0 files changed, 0 insertions, 0 deletions