summaryrefslogtreecommitdiff
path: root/drivers/message
diff options
context:
space:
mode:
authorMatthew Auld <matthew.auld@intel.com>2020-10-21 11:36:06 +0100
committerRodrigo Vivi <rodrigo.vivi@intel.com>2020-10-29 14:20:17 -0400
commit09a729b178be1cb20ffce620f7e5bfc04c4a13c0 (patch)
tree0474df19c322f284488428049e1f4dee5edb0e35 /drivers/message
parent3650b228f83adda7e5ee532e2b90429c03f7b9ec (diff)
drm/i915/region: fix max size calculation
We are incorrectly limiting the max allocation size as per the mm max_order, which is effectively the largest power-of-two that we can fit in the region size. However, it's normal to setup the region or allocator with a non-power-of-two size(for example 3G), which we should already handle correctly, except it seems for the early too-big-check. v2: make sure we also exercise the I915_BO_ALLOC_CONTIGUOUS path, which is quite different, since for that we are actually limited by the largest power-of-two that we can fit within the region size. (Chris) Fixes: b908be543e44 ("drm/i915: support creating LMEM objects") Signed-off-by: Matthew Auld <matthew.auld@intel.com> Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: CQ Tang <cq.tang@intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Link: https://patchwork.freedesktop.org/patch/msgid/20201021103606.241395-1-matthew.auld@intel.com (cherry picked from commit 83ebef47f8ebe320d5c5673db82f9903a4f40a69) Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Diffstat (limited to 'drivers/message')
0 files changed, 0 insertions, 0 deletions