blob: 798f7792d8a63b2bb27f3c3b15bbfb8f4a228995 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
graphic: 0.718
device: 0.608
architecture: 0.521
vnc: 0.347
PID: 0.317
mistranslation: 0.311
ppc: 0.305
virtual: 0.299
x86: 0.286
kernel: 0.274
semantic: 0.268
boot: 0.249
risc-v: 0.244
network: 0.238
peripherals: 0.231
permissions: 0.225
performance: 0.221
socket: 0.217
hypervisor: 0.213
files: 0.200
VMM: 0.193
TCG: 0.162
i386: 0.155
arm: 0.144
user-level: 0.134
register: 0.131
debug: 0.126
KVM: 0.054
assembly: 0.050
[RFC] dma buf: support sprite plane
QEMU does not support sprite/overlay in DMA-buf mode for Intel gvt vGPUs. Some use cases relies on sprite plane support, e.g. hw accelerated video playback in Windows 10 guest.
To support this feature, functions in both kernel and QEMU should be implemented:
- query support for plane info in kernel:
in vgpu_get_plane_info() of drm/i915/gvt/dmabuf.c, calls to intel_vgpu_decode_sprite_plane() shall be made;
- struct to hold VFIODMABuf object in QEMU:
in struct VFIODisplay of include/hw/vfio/vfio-common.h;
- copying of data in QEMU:
in vfio_display_get_dmabuf() of hw/vfio/display.c;
- drawing of sprite plane in QEMU:
in vfio_display_dmabuf_update() of hw/vfio/display.c;
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/169
|