| commit | 2bfa996e031bdc6de1567ee05438f8a310fa7a4c | |
| author | Chris Wilson <chris@chris-wilson.co.uk> | |
| Thu, 4 Aug 2016 06:52:25 +0000 (4 07:52 +0100) | ||
| committer | Chris Wilson <chris@chris-wilson.co.uk> | |
| Thu, 4 Aug 2016 07:09:17 +0000 (4 08:09 +0100) | ||
| tree | 219aab8667b8d964ee9c7053f1dc61bb14760238 | treesnapshot (tar.gz zip) |
| parent | 34c998b4ebf6c48154c76ea9bc9bffabd91a8af2 | commitdiff |
drm/i915: Store owning file on the i915_address_space
For the global GTT (and aliasing GTT), the address space is owned by the
device (it is a global resource) and so the per-file owner field is
NULL. For per-process GTT (where we create an address space per
context), each is owned by the opening file. We can use this ownership
information to both distinguish GGTT and ppGTT address spaces, as well
as occasionally inspect the owner.
v2: Whitespace, tells us who owns i915_address_space
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1470293567-10811-6-git-send-email-chris@chris-wilson.co.uk
For the global GTT (and aliasing GTT), the address space is owned by the
device (it is a global resource) and so the per-file owner field is
NULL. For per-process GTT (where we create an address space per
context), each is owned by the opening file. We can use this ownership
information to both distinguish GGTT and ppGTT address spaces, as well
as occasionally inspect the owner.
v2: Whitespace, tells us who owns i915_address_space
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1470293567-10811-6-git-send-email-chris@chris-wilson.co.uk