diff options
author | Dave Airlie <airlied@redhat.com> | 2019-11-28 03:39:50 +0100 |
---|---|---|
committer | Dave Airlie <airlied@redhat.com> | 2019-11-28 05:33:01 +0100 |
commit | 0a6cad5df541108cfd3fbd79eef48eb824c89bdc (patch) | |
tree | 767d41bf88ec067b85fe3d87a190ef08e59a1ce7 /net/ipv4/af_inet.c | |
parent | Merge tag 'drm-next-5.5-2019-11-22' of git://people.freedesktop.org/~agd5f/li... (diff) | |
parent | drm/vmwgfx: Add surface dirty-tracking callbacks (diff) | |
download | linux-0a6cad5df541108cfd3fbd79eef48eb824c89bdc.tar.xz linux-0a6cad5df541108cfd3fbd79eef48eb824c89bdc.zip |
Merge branch 'vmwgfx-coherent' of git://people.freedesktop.org/~thomash/linux into drm-next
Graphics APIs like OpenGL 4.4 and Vulkan require the graphics driver
to provide coherent graphics memory, meaning that the GPU sees any
content written to the coherent memory on the next GPU operation that
touches that memory, and the CPU sees any content written by the GPU
to that memory immediately after any fence object trailing the GPU
operation is signaled.
Paravirtual drivers that otherwise require explicit synchronization
needs to do this by hooking up dirty tracking to pagefault handlers
and buffer object validation.
Provide mm helpers needed for this and that also allow for huge pmd-
and pud entries (patch 1-3), and the associated vmwgfx code (patch 4-7).
The code has been tested and exercised by a tailored version of mesa
where we disable all explicit synchronization and assume graphics memory
is coherent. The performance loss varies of course; a typical number is
around 5%.
Signed-off-by: Dave Airlie <airlied@redhat.com>
From: Thomas Hellstrom <thomas_os@shipmail.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20191113131639.4653-1-thomas_os@shipmail.org
Diffstat (limited to 'net/ipv4/af_inet.c')
0 files changed, 0 insertions, 0 deletions