diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2020-12-02 20:34:44 +0300 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2020-12-02 23:59:29 +0300 |
| commit | 7d1a31e128d3cb939cd70c95f898c13f85155571 (patch) | |
| tree | 5cdffe81cc1fdb8d5a58437c9fa99061ef048fab /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | a2843b3bd17e5a1c6b270709dc5bb0091eba1074 (diff) | |
| download | linux-7d1a31e128d3cb939cd70c95f898c13f85155571.tar.xz | |
Revert "drm/i915/lmem: Limit block size to 4G"
Mixing I915_ALLOC_CONTIGUOUS and I915_ALLOC_MAX_SEGMENT_SIZE fared
badly. The two directives conflict, with the contiguous request setting
the min_order to the full size of the object, and the max-segment-size
setting the max_order to the limit of the DMA mapper. This results in a
situation where max_order < min_order, causing our sanity checks to
fail.
Instead of limiting the buddy block size, in the previous patch we split
the oversized buddy into multiple scatterlist elements.
Fixes: d2cf0125d4a1 ("drm/i915/lmem: Limit block size to 4G")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: Matthew Auld <matthew.auld@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20201202173444.14903-2-chris@chris-wilson.co.uk
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions