Searched hist:"9 bad40a27dac1f88012a1e2db0bfc5ae58fa0370" (Results 1 – 5 of 5) sorted by relevance
/linux/drivers/gpu/drm/i915/gt/ |
H A D | selftest_ring_submission.c | diff 9bad40a27dac1f88012a1e2db0bfc5ae58fa0370 Mon May 11 16:13:03 CEST 2020 Chris Wilson <chris@chris-wilson.co.uk> drm/i915/selftests: Always flush before unpining after writing
Be consistent, and even when we know we had used a WC, flush the mapped object after writing into it. The flush understands the mapping type and will only clflush if !I915_MAP_WC, but will always insert a wmb [sfence] so that we can be sure that all writes are visible.
v2: Add the unconditional wmb so we are know that we always flush the writes to memory/HW at that point.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200511141304.599-1-chris@chris-wilson.co.uk
|
H A D | selftest_rps.c | diff 9bad40a27dac1f88012a1e2db0bfc5ae58fa0370 Mon May 11 16:13:03 CEST 2020 Chris Wilson <chris@chris-wilson.co.uk> drm/i915/selftests: Always flush before unpining after writing
Be consistent, and even when we know we had used a WC, flush the mapped object after writing into it. The flush understands the mapping type and will only clflush if !I915_MAP_WC, but will always insert a wmb [sfence] so that we can be sure that all writes are visible.
v2: Add the unconditional wmb so we are know that we always flush the writes to memory/HW at that point.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200511141304.599-1-chris@chris-wilson.co.uk
|
/linux/drivers/gpu/drm/i915/gem/selftests/ |
H A D | igt_gem_utils.c | diff 9bad40a27dac1f88012a1e2db0bfc5ae58fa0370 Mon May 11 16:13:03 CEST 2020 Chris Wilson <chris@chris-wilson.co.uk> drm/i915/selftests: Always flush before unpining after writing
Be consistent, and even when we know we had used a WC, flush the mapped object after writing into it. The flush understands the mapping type and will only clflush if !I915_MAP_WC, but will always insert a wmb [sfence] so that we can be sure that all writes are visible.
v2: Add the unconditional wmb so we are know that we always flush the writes to memory/HW at that point.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200511141304.599-1-chris@chris-wilson.co.uk
|
H A D | i915_gem_coherency.c | diff 9bad40a27dac1f88012a1e2db0bfc5ae58fa0370 Mon May 11 16:13:03 CEST 2020 Chris Wilson <chris@chris-wilson.co.uk> drm/i915/selftests: Always flush before unpining after writing
Be consistent, and even when we know we had used a WC, flush the mapped object after writing into it. The flush understands the mapping type and will only clflush if !I915_MAP_WC, but will always insert a wmb [sfence] so that we can be sure that all writes are visible.
v2: Add the unconditional wmb so we are know that we always flush the writes to memory/HW at that point.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200511141304.599-1-chris@chris-wilson.co.uk
|
/linux/drivers/gpu/drm/i915/selftests/ |
H A D | i915_request.c | diff 9bad40a27dac1f88012a1e2db0bfc5ae58fa0370 Mon May 11 16:13:03 CEST 2020 Chris Wilson <chris@chris-wilson.co.uk> drm/i915/selftests: Always flush before unpining after writing
Be consistent, and even when we know we had used a WC, flush the mapped object after writing into it. The flush understands the mapping type and will only clflush if !I915_MAP_WC, but will always insert a wmb [sfence] so that we can be sure that all writes are visible.
v2: Add the unconditional wmb so we are know that we always flush the writes to memory/HW at that point.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200511141304.599-1-chris@chris-wilson.co.uk
|