virgl/vtest: receive and handle shared memory fd
authorGurchetan Singh <gurchetansingh@chromium.org>
Wed, 12 Dec 2018 17:49:35 +0000 (09:49 -0800)
committerGurchetan Singh <gurchetansingh@chromium.org>
Thu, 18 Apr 2019 22:39:05 +0000 (15:39 -0700)
commit96c3418e063d0a2e2ac1b83dc11a5a25cbef9555
treed70731db544bd6123f718a236fb7900c4407d7ac
parent9a638bc7c2626e757321655068169b0cd588d88b
virgl/vtest: receive and handle shared memory fd

The only tricky part is with protocol 0 we can either have
a display target or resource backing store.  With protocol
2 we can have both.  Make the map/unmap functions only deal
with the resource backing store.

v2: Handle MSAA texture case.
v3: spelling
v4: Fix dangling else (@prak)
v5: mmap --> os_mmap (@prak) + added comments (@gerddie)

Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
Reviewed-By: Gert Wollny <gert.wollny@collabora.com>
Reviewed-By: Piotr Rak <p.rak@samsung.com>
src/gallium/winsys/virgl/vtest/virgl_vtest_socket.c
src/gallium/winsys/virgl/vtest/virgl_vtest_winsys.c