aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorMatthew Auld <[email protected]>2020-11-09 11:12:49 +0000
committerChris Wilson <[email protected]>2020-11-09 13:38:41 +0000
commit330b7d33056bb0fa7d7f672d4a98495f200fe9d4 (patch)
treec67a8f83e20bcd070ff2d59a4fca43fbd8668427 /tools/perf/scripts/python/bin
parent2dae0c852940189af35b65895443f9ab05e1b319 (diff)
drm/i915/region: fix order when adding blocks
When performing an allocation we try split it down into the largest possible power-of-two blocks/pages-sizes, and for the common case we expect to allocate the blocks in descending order. This also naturally fits with our GTT alignment tricks(including the hugepages selftest), where we sometimes try to align to the largest possible GTT page-size for the allocation, in the hope that translates to bigger GTT page-sizes. Currently, we seem to incorrectly add the blocks in the opposite order, which is definitely not the intended behaviour. Reported-by: CQ Tang <[email protected]> Signed-off-by: Matthew Auld <[email protected]> Cc: Chris Wilson <[email protected]> Cc: CQ Tang <[email protected]> Reviewed-by: Chris Wilson <[email protected]> Signed-off-by: Chris Wilson <[email protected]> Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions