summaryrefslogtreecommitdiffstats
path: root/mm/memory.c
diff options
context:
space:
mode:
authorJason Wang <jasowang@redhat.com>2020-07-20 16:50:43 +0800
committerMichael S. Tsirkin <mst@redhat.com>2020-08-05 11:08:41 -0400
commit6234f80574d7569444d8718355fa2838e92b158b (patch)
tree5bd8b550a99af20448f685df9350f27485e14682 /mm/memory.c
parent481a0d7422db26fb63e2d64f0652667a5c6d0f3e (diff)
downloadlinux-stable-6234f80574d7569444d8718355fa2838e92b158b.tar.gz
linux-stable-6234f80574d7569444d8718355fa2838e92b158b.tar.bz2
linux-stable-6234f80574d7569444d8718355fa2838e92b158b.zip
vhost: vdpa: remove per device feature whitelist
We used to have a per device feature whitelist to filter out the unsupported virtio features. But this seems unnecessary since: - the main idea behind feature whitelist is to block control vq feature until we finalize the control virtqueue API. But the current vhost-vDPA uAPI is sufficient to support control virtqueue. For device that has hardware control virtqueue, the vDPA device driver can just setup the hardware virtqueue and let userspace to use hardware virtqueue directly. For device that doesn't have a control virtqueue, the vDPA device driver need to use e.g vringh to emulate a software control virtqueue. - we don't do it in virtio-vDPA driver So remove this limitation. Signed-off-by: Jason Wang <jasowang@redhat.com> Link: https://lore.kernel.org/r/20200720085043.16485-1-jasowang@redhat.com Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'mm/memory.c')
0 files changed, 0 insertions, 0 deletions