09a729b178
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: |
||
---|---|---|
.. | ||
i915_active.c | ||
i915_buddy.c | ||
i915_gem_evict.c | ||
i915_gem_gtt.c | ||
i915_gem.c | ||
i915_live_selftests.h | ||
i915_mock_selftests.h | ||
i915_perf_selftests.h | ||
i915_perf.c | ||
i915_random.c | ||
i915_random.h | ||
i915_request.c | ||
i915_selftest.c | ||
i915_sw_fence.c | ||
i915_syncmap.c | ||
i915_vma.c | ||
igt_atomic.c | ||
igt_atomic.h | ||
igt_flush_test.c | ||
igt_flush_test.h | ||
igt_live_test.c | ||
igt_live_test.h | ||
igt_mmap.c | ||
igt_mmap.h | ||
igt_reset.c | ||
igt_reset.h | ||
igt_spinner.c | ||
igt_spinner.h | ||
intel_memory_region.c | ||
intel_uncore.c | ||
lib_sw_fence.c | ||
lib_sw_fence.h | ||
librapl.c | ||
librapl.h | ||
mock_drm.h | ||
mock_gem_device.c | ||
mock_gem_device.h | ||
mock_gtt.c | ||
mock_gtt.h | ||
mock_region.c | ||
mock_region.h | ||
mock_request.c | ||
mock_request.h | ||
mock_uncore.c | ||
mock_uncore.h | ||
scatterlist.c |