[PATCH 1/2] drm/i915: Allow evicting to use the requested placement

Thanks to Justin Brewer for bisecting the issue. Fixes: a78a8da51b36 ("drm/ttm: replace busy placement with flags v6") Fixes: 4a0e7b3c3753 ("drm/i915: fix applying placement flag") Link: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11255 Signed-off-by: David Gow

[PATCH 2/2] drm/i915: Attempt to get pages without eviction first

tm_palcement, as the individual placements are marked 'const', so hot-patching the flags is even more dodgy than before. Thanks to Justin Brewer for bisecting this. Fixes: a78a8da51b36 ("drm/ttm: replace busy placement with flags v6") Link: https://gitlab.freedesktop.org/drm/i915/ke

[PATCH 0/2] drm/i915: Fix ttm small BAR placement handling

From: David Gow As described in [1], there have been a couple of regressions in the TTM placement handling for i915, which adversely affect DG2 systems with small BAR. In particular, performance become very poor when eviction from the mappable BAR memory is required, as suboptimal placements

[PATCH] drm/i915: Allow evicting to use the requested placement

tin Brewer for bisecting the issue. Fixes: a78a8da51b36 ("drm/ttm: replace busy placement with flags v6") Fixes: 4a0e7b3c3753 ("drm/i915: fix applying placement flag") Link: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11255 Signed-off-by: David Gow --- I'm no

Re: linux-next: build failure after merge of the kunit-next tree

On Thu, 29 Feb 2024 at 23:07, Shuah Khan wrote: > > Hi Stephen, > > On 2/28/24 21:26, Stephen Rothwell wrote: > > Hi all, > > > > After merging the kunit-next tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > In file included from drivers/gpu/drm/tests/drm_buddy_te

[PATCH] kunit: device: Unregister the kunit_bus on shutdown

e value of kunit_bus_device. It is: - a valid struct device* if the kunit_bus initialised correctly. - an ERR_PTR if it failed to initialise. - NULL before initialisation and after shutdown. Fixes: d03c720e03bd ("kunit: Add APIs for managing devices") Signed-off-by: David Gow --- This will hopef

Re: [Intel-gfx] [RFC PATCH] kunit: Fix test log size limit too low for some tests

On Wed, 30 Aug 2023 at 15:55, Janusz Krzysztofik wrote: > > Now we have memory space available to a kunit test case log exposed via > debugfs limited to 2048 bytes, while some parametrized test cases, e.g., > drm_framebuffer.drm_test_framebuffer_create, need more. For this reason, > debugfs resul

Re: [Intel-gfx] KUnit issues - Was: [igt-dev] [PATCH RFC v2 8/8] drm/i915: check if current->mm is not NULL

On Thu, Nov 3, 2022 at 11:23 PM Mauro Carvalho Chehab wrote: > > Hi, > > I'm facing a couple of issues when testing KUnit with the i915 driver. > > The DRM subsystem and the i915 driver has, for a long time, his own > way to do unit tests, which seems to be added before KUnit. > > I'm now checking