Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
* Rework TTMs busy handling
@ 2024-01-12 12:51 Christian König
  2024-01-12 12:51 ` [PATCH 1/5] drm/vmwgfx: remove vmw_vram_gmr_placement Christian König
                   ` (8 more replies)
  0 siblings, 9 replies; 28+ messages in thread
From: Christian König @ 2024-01-12 12:51 UTC (permalink / raw)
  To: dri-devel, intel-gfx, thomas.hellstrom, nouveau, jani.nikula,
	kherbst, lyude, zackr, michel.daenzer

Hi guys,

same as the last time. Things I've changed:

Implemented the requirements from Zack to correctly fill in the busy
placements for VMWGFX.

Renamed the placement flags to desired and fallback as suggested by
Michel.

Rebased on drm-tip instead of drm-misc-next and fixed XE as well.

Please review and comment,
Christian.



^ permalink raw reply	[flat|nested] 28+ messages in thread
* Rework TTMs busy handling
@ 2024-01-26 14:09 Christian König
  0 siblings, 0 replies; 28+ messages in thread
From: Christian König @ 2024-01-26 14:09 UTC (permalink / raw)
  To: thomas.hellstrom, dri-devel, intel-gfx, nouveau

Hi guys,

so pushed the first few patches from this series. I hope that I
correctly managed to resolve the silent Xe merge conflict in drm-tip,
but would be nice if somebody could double check.

Then for the two remaining patches I've implemented most of what
Thomas suggest, e.g. the existing functionality sticks around for
eviction and hobs, but ttm_bo_validate will now try to always move
things into the non-fallback placements on validation first.

What I haven't done yet is to split up the preferred placement since
I couldn't immediately see an use case for this, but it's really
something we might do in the future as well.

Please review and comment,
Christian.



^ permalink raw reply	[flat|nested] 28+ messages in thread
* Rework TTMs busy handling
@ 2024-01-09  7:47 Christian König
  2024-01-09  8:14 ` Thomas Hellström
  0 siblings, 1 reply; 28+ messages in thread
From: Christian König @ 2024-01-09  7:47 UTC (permalink / raw)
  To: zack.rusin, thomas.hellstrom, lyude, kherbst, jani.nikula,
	nouveau, intel-gfx, dri-devel

Hi guys,

I'm trying to make this functionality a bit more useful for years now
since we multiple reports that behavior of drivers can be suboptimal
when multiple placements be given.

So basically instead of hacking around the TTM behavior in the driver
once more I've gone ahead and changed the idle/busy placement list
into idle/busy placement flags. This not only saves a bunch of code,
but also allows setting some placements as fallback which are used if
allocating from the preferred ones didn't worked.

Zack pointed out that some removed VMWGFX code was brought back because
of rebasing, fixed in this version.

Intel CI seems to be happy with those patches, so any more comments?

Regards,
Christian.



^ permalink raw reply	[flat|nested] 28+ messages in thread
* Rework TTMs busy handling
@ 2024-01-04 15:05 Christian König
  0 siblings, 0 replies; 28+ messages in thread
From: Christian König @ 2024-01-04 15:05 UTC (permalink / raw)
  To: dri-devel, intel-gfx, thomas.hellstrom, nouveau, jani.nikula,
	kherbst, lyude, zackr

Hi guys,

I'm trying to make this functionality a bit more useful for years now
since we multiple reports that behavior of drivers can be suboptimal
when multiple placements be given.

So basically instead of hacking around the TTM behavior in the driver
once more I've gone ahead and changed the idle/busy placement list
into idle/busy placement flags. This not only saves a bunch of code,
but also allows setting some placements as fallback which are used if
allocating from the preferred ones didn't worked.

Intel CI seems to be happy with those patches, so any more comments?

Regards,
Christian.



^ permalink raw reply	[flat|nested] 28+ messages in thread

end of thread, other threads:[~2024-01-29 11:00 UTC | newest]

Thread overview: 28+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-01-12 12:51 Rework TTMs busy handling Christian König
2024-01-12 12:51 ` [PATCH 1/5] drm/vmwgfx: remove vmw_vram_gmr_placement Christian König
2024-01-12 12:51 ` [PATCH 2/5] drm/ttm: return ENOSPC from ttm_bo_mem_space Christian König
2024-01-17 10:18   ` Thomas Hellström
2024-01-12 12:51 ` [PATCH 3/5] drm/ttm: replace busy placement with flags v6 Christian König
2024-01-17  8:01   ` Thomas Zimmermann
2024-01-17 10:47   ` Thomas Hellström
2024-01-17 12:27     ` Thomas Hellström
2024-01-18 16:38       ` Thomas Hellström
2024-01-26 22:16         ` Lucas De Marchi
2024-01-26 22:22           ` Lucas De Marchi
2024-01-27 15:43             ` Zeng, Oak
2024-01-29 11:00             ` Thomas Hellström
2024-01-12 12:51 ` [PATCH 4/5] drm/ttm: improve idle/busy handling v3 Christian König
2024-01-18 14:24   ` Thomas Hellström
2024-01-18 16:48     ` Thomas Hellström
2024-01-12 12:51 ` [PATCH 5/5] drm/amdgpu: use GTT only as fallback for VRAM|GTT Christian König
2024-01-12 14:04 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/vmwgfx: remove vmw_vram_gmr_placement Patchwork
2024-01-12 14:04 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-01-12 14:22 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-01-16  9:57 ` Rework TTMs busy handling Christian König
2024-01-17  3:13   ` Zack Rusin
  -- strict thread matches above, loose matches on Subject: below --
2024-01-26 14:09 Christian König
2024-01-09  7:47 Christian König
2024-01-09  8:14 ` Thomas Hellström
2024-01-09  8:34   ` Christian König
2024-01-10  9:03     ` Michel Dänzer
2024-01-04 15:05 Christian König

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox