drm/i915: Always allocate an object/vma for the HWSP
Currently we only allocate an object and vma if we are using a GGTT virtual HWSP, and a plain struct page for a physical HWSP. For convenience later on with global timelines, it will be useful to always have the status page being tracked by a struct i915_vma. Make it so. Signed-off-by:Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by:
Matthew Auld <matthew.auld@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190128102356.15037-4-chris@chris-wilson.co.uk
Showing
- drivers/gpu/drm/i915/intel_engine_cs.c 55 additions, 54 deletionsdrivers/gpu/drm/i915/intel_engine_cs.c
- drivers/gpu/drm/i915/intel_guc_submission.c 6 additions, 0 deletionsdrivers/gpu/drm/i915/intel_guc_submission.c
- drivers/gpu/drm/i915/intel_lrc.c 9 additions, 3 deletionsdrivers/gpu/drm/i915/intel_lrc.c
- drivers/gpu/drm/i915/intel_ringbuffer.c 16 additions, 5 deletionsdrivers/gpu/drm/i915/intel_ringbuffer.c
- drivers/gpu/drm/i915/intel_ringbuffer.h 6 additions, 17 deletionsdrivers/gpu/drm/i915/intel_ringbuffer.h
- drivers/gpu/drm/i915/selftests/mock_engine.c 1 addition, 1 deletiondrivers/gpu/drm/i915/selftests/mock_engine.c
Loading
Please register or sign in to comment