drm-vmwgfx-Use-the-common-gem-mmap-instead-of-the-custom-code/20230128-112136
base: git://anongit.freedesktop.org/drm-intel for-linux-next-fixes
patch link:https://lore.kernel.org/r/20230126173813.602748-7-zack%40kde.org
patch subject: [PATCH 6/7] drm/vmwgfx: Abstract placement selection
co
Hi
Am 26.01.23 um 18:38 schrieb Zack Rusin:
From: Zack Rusin
Problem with explicit placement selection in vmwgfx is that by the time
the buffer object needs to be validated the information about which
placement was supposed to be used is lost. To workaround this the driver
had a bunch of state
From: Zack Rusin
Problem with explicit placement selection in vmwgfx is that by the time
the buffer object needs to be validated the information about which
placement was supposed to be used is lost. To workaround this the driver
had a bunch of state in various places e.g. as_mob or cpu_blit to
s
