Hi Krzysztof,
> > - /*
> > -* While we should be able allocate everything without any flag
> > -* restrictions, if we consider I915_BO_ALLOC_CONTIGUOUS then we are
> > -* actually limited to the largest power-of-two for the region size i.e
> > -* max_order, due to the inner worki
Hi Krzysztof,
[...]
> > > I guess a check for contiguousness does not hurt, but the test behavior
> > > is fundamentally different here. Maybe manually rounding size up to the
> > > nearest larger power of two would be a better idea here?
> >
> > Before changes were made to the allocator we knew
Hi Krzysztof,
On 2025-03-18 at 10:39:41 GMT, Krzysztof Karas wrote:
> Hi Krzysztof,
>
> > > - /*
> > > - * While we should be able allocate everything without any flag
> > > - * restrictions, if we consider I915_BO_ALLOC_CONTIGUOUS then we are
> > > - * actually limited to the largest power-o
Hi Mikolaj,
On 2025-03-14 at 15:42:23 GMT, Mikolaj Wasiak wrote:
> Due to changes in allocator, the size of the allocation for
> contiguous region is not rounded up to a power-of-two and
> instead allocated as is. Thus, change the part of test that
> expected the allocation to fail.
>
> Closes: h
Due to changes in allocator, the size of the allocation for
contiguous region is not rounded up to a power-of-two and
instead allocated as is. Thus, change the part of test that
expected the allocation to fail.
Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9311
Signed-off-by: Mi