diff options
author | Mauro Carvalho Chehab <mchehab@kernel.org> | 2022-07-27 15:29:56 +0300 |
---|---|---|
committer | Andi Shyti <andi.shyti@linux.intel.com> | 2022-07-28 15:02:27 +0300 |
commit | d1051db85f6496ed9c825802bef3709f2e7d816f (patch) | |
tree | a327cb5c8ce70d28da6f5a55d097700163b81490 /tools/perf/scripts/python/stackcollapse.py | |
parent | 5d36acb7198b0e5eb88e6b701f9ad7b9448f8df9 (diff) | |
download | linux-d1051db85f6496ed9c825802bef3709f2e7d816f.tar.xz |
drm/i915/gt: describe the new tlb parameter at i915_vma_resource
TLB cache invalidation can happen on two different situations:
1. synchronously, at __vma_put_pages();
2. asynchronously.
On the first case, TLB cache invalidation happens inside
__vma_put_pages(). So, no need to do it later on.
However, on the second case, the pages will keep in memory
until __i915_vma_evict() is called.
So, we need to store the TLB data at struct i915_vma_resource,
in order to do a TLB cache invalidation before allowing
userspace to re-use the same memory.
So, i915_vma_resource_unbind() has gained a new parameter
in order to store the TLB data at the second case.
Document it.
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/aa55eef7e63b8f3d0f69b525db2dd2eb87e9db6b.1658924372.git.mchehab@kernel.org
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions