diff options
| author | Jonathan Cavitt <jonathan.cavitt@intel.com> | 2023-04-26 23:28:49 +0200 |
|---|---|---|
| committer | Andrzej Hajda <andrzej.hajda@intel.com> | 2023-04-28 13:20:05 +0200 |
| commit | eee44c2903e5222632536f86ad5cf0ff9bbfc61b (patch) | |
| tree | 74120a5c53f7b1305610e905e323eb8cf6cd2340 /tools/perf/scripts/python/bin/export-to-sqlite-record | |
| parent | drm/i915: Migrate platform-dependent mock hugepage selftests to live (diff) | |
| download | linux-eee44c2903e5222632536f86ad5cf0ff9bbfc61b.tar.gz linux-eee44c2903e5222632536f86ad5cf0ff9bbfc61b.zip | |
drm/i915: Use correct huge page manager for MTL
MTL currently uses gen8_ppgtt_insert_huge when managing huge pages.
This is because MTL reports as not supporting 64K pages, or more
accurately, the system that reports whether a platform has 64K pages
reports false for MTL. This is only half correct, as the 64K page support
reporting system only cares about 64K page support for LMEM, which MTL
doesn't have.
MTL should be using xehpsdv_ppgtt_insert_huge. However, simply changing
over to using that manager doesn't resolve the issue because MTL is
expecting the virtual address space for the page table to be flushed after
initialization, so we must also add a flush statement there.
Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230425-hugepage-migrate-v8-2-7868d54eaa27@intel.com
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-sqlite-record')
0 files changed, 0 insertions, 0 deletions