diff options
| author |   Matthew Auld <matthew.auld@intel.com> | 2017-06-22 10:58:36 +0100 |
|---|---|---|
| committer |   Chris Wilson <chris@chris-wilson.co.uk> | 2017-06-22 16:48:50 +0100 |
| commit | 4a234c5fae1686c8327edeaabc0f2d6fb86db470 (patch) | |
| tree | 8ae6b7f57219f2ca1caa55585d9c83d9bb3c9759 /tools/perf/scripts/python | |
| parent | drm/i915: Clear execbuf's vma backpointer upon release (diff) | |
| download | linux-dev-4a234c5fae1686c8327edeaabc0f2d6fb86db470.tar.xz linux-dev-4a234c5fae1686c8327edeaabc0f2d6fb86db470.zip | |
drm/i915: pass the vma to insert_entries
The vma already contains most of the information we need for insertion.
But also in preparation for supporting huge gtt pages, it would be
useful to know the details of the vma, such that we can we can easily
determine the page sizes we are allowed to use when inserting into the
48b PPGTT. This is especially true for 64K where we can't just
arbitrarily use it, since we require aligning/padding the vm space to
2M, which sometimes we can't enforce in the upper levels.
Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: http://patchwork.freedesktop.org/patch/msgid/20170622095836.6800-1-matthew.auld@intel.com
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions