On to, 2017-05-18 at 10:46 +0100, Chris Wilson wrote:
> During execbuf, a mandatory step is that we add this request (this
> fence) to each object's reservation_object. Inside execbuf, we track the
> vma, and to add the fence to the reservation_object then means having to
> first chase the obj, incurring another cache miss. We can reduce the
> number of cache misses by stashing a pointer to the reservation_object
> in the vma itself.
>
> Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
<SNIP>
> +++ b/drivers/gpu/drm/i915/i915_vma.h
> @@ -50,6 +50,7 @@ struct i915_vma {
> struct drm_i915_gem_object *obj;
> struct i915_address_space *vm;
> struct drm_i915_fence_reg *fence;
> + struct reservation_object *resv;
Add a kerneldoc that this is an alias.
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
