summary refs log tree commit diff stats
path: root/contrib/vhost-user-gpu/main.c
diff options
context:
space:
mode:
authorPankaj Gupta <pagupta@redhat.com>2019-06-19 15:19:04 +0530
committerMichael S. Tsirkin <mst@redhat.com>2019-07-04 17:00:32 -0400
commitadf0748a494151fd7c10050820f2a3988768828a (patch)
treecca8530108748fdeb7522c68415f283f76f3352c /contrib/vhost-user-gpu/main.c
parent9f583bdd47189416c7ba331f1baf3a890f2671a6 (diff)
downloadfocaccia-qemu-adf0748a494151fd7c10050820f2a3988768828a.tar.gz
focaccia-qemu-adf0748a494151fd7c10050820f2a3988768828a.zip
virtio-pci: Proxy for virtio-pmem
We need a proxy device for virtio-pmem, and this device has to be the
actual memory device so we can cleanly hotplug it.

Forward memory device class functions either to the actual device or use
properties of the virtio-pmem device to implement these in the proxy.

virtio-pmem will only be compiled for selected, supported architectures
(that can deal with virtio/pci devices being memory devices). An
architecture that is prepared for that can simply enable
CONFIG_VIRTIO_PMEM to make it work.

As not all architectures support memory devices (and CONFIG_VIRTIO_PMEM
will be enabled per supported architecture), we have to move the PCI proxy
to a separate file.

Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
[ split up patches, memory-device changes, move pci proxy]
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20190619094907.10131-5-pagupta@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'contrib/vhost-user-gpu/main.c')
0 files changed, 0 insertions, 0 deletions