search for: config_vfio_mdev_device

On 01.04.20 14:50, Jason Wang wrote: > > On 2020/4/1 ??7:21, Christian Borntraeger wrote: >> On 26.03.20 15:01, Jason Wang wrote: >>> Currently, CONFIG_VHOST depends on CONFIG_VIRTUALIZATION. But vhost is >>> not necessarily for VM since it's a generic userspace and kernel >>> communication protocol. Such dependency may prevent archs without >>>

On 01.04.20 14:50, Jason Wang wrote: > > On 2020/4/1 ??7:21, Christian Borntraeger wrote: >> On 26.03.20 15:01, Jason Wang wrote: >>> Currently, CONFIG_VHOST depends on CONFIG_VIRTUALIZATION. But vhost is >>> not necessarily for VM since it's a generic userspace and kernel >>> communication protocol. Such dependency may prevent archs without >>>

.../s390/configs/debug_defconfig +++ b/arch/s390/configs/debug_defconfig @@ -57,8 +57,6 @@ CONFIG_PROTECTED_VIRTUALIZATION_GUEST=y CONFIG_CMM=m CONFIG_APPLDATA_BASE=y CONFIG_KVM=m -CONFIG_VHOST_NET=m -CONFIG_VHOST_VSOCK=m CONFIG_OPROFILE=m CONFIG_KPROBES=y CONFIG_JUMP_LABEL=y @@ -561,6 +559,9 @@ CONFIG_VFIO_MDEV_DEVICE=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m CONFIG_VIRTIO_INPUT=y +CONFIG_VHOST=m +CONFIG_VHOST_NET=m +CONFIG_VHOST_VSOCK=m CONFIG_S390_CCW_IOMMU=y CONFIG_S390_AP_IOMMU=y CONFIG_EXT4_FS=y diff --git a/arch/s390/configs/defconfig b/arch/s390/configs/defconfig index 7cd0648c1f4e..39e69c4e8cf7...

...ROTECTED_VIRTUALIZATION_GUEST=y > > CONFIG_CMM=m > > CONFIG_APPLDATA_BASE=y > > CONFIG_KVM=m > > -CONFIG_VHOST_NET=m > > -CONFIG_VHOST_VSOCK=m > > CONFIG_OPROFILE=m > > CONFIG_KPROBES=y > > CONFIG_JUMP_LABEL=y > > @@ -561,6 +559,9 @@ CONFIG_VFIO_MDEV_DEVICE=m > > CONFIG_VIRTIO_PCI=m > > CONFIG_VIRTIO_BALLOON=m > > CONFIG_VIRTIO_INPUT=y > > +CONFIG_VHOST=m > > +CONFIG_VHOST_NET=m > > +CONFIG_VHOST_VSOCK=m > > CONFIG_S390_CCW_IOMMU=y > > CONFIG_S390_AP_IOMMU=y > > CONFIG_EXT4_FS=y > &g...

...bug_defconfig > @@ -57,8 +57,6 @@ CONFIG_PROTECTED_VIRTUALIZATION_GUEST=y > CONFIG_CMM=m > CONFIG_APPLDATA_BASE=y > CONFIG_KVM=m > -CONFIG_VHOST_NET=m > -CONFIG_VHOST_VSOCK=m > CONFIG_OPROFILE=m > CONFIG_KPROBES=y > CONFIG_JUMP_LABEL=y > @@ -561,6 +559,9 @@ CONFIG_VFIO_MDEV_DEVICE=m > CONFIG_VIRTIO_PCI=m > CONFIG_VIRTIO_BALLOON=m > CONFIG_VIRTIO_INPUT=y > +CONFIG_VHOST=m > +CONFIG_VHOST_NET=m > +CONFIG_VHOST_VSOCK=m > CONFIG_S390_CCW_IOMMU=y > CONFIG_S390_AP_IOMMU=y > CONFIG_EXT4_FS=y > diff --git a/arch/s390/configs/defconfig b/arch...

...bug_defconfig > @@ -57,8 +57,6 @@ CONFIG_PROTECTED_VIRTUALIZATION_GUEST=y > CONFIG_CMM=m > CONFIG_APPLDATA_BASE=y > CONFIG_KVM=m > -CONFIG_VHOST_NET=m > -CONFIG_VHOST_VSOCK=m > CONFIG_OPROFILE=m > CONFIG_KPROBES=y > CONFIG_JUMP_LABEL=y > @@ -561,6 +559,9 @@ CONFIG_VFIO_MDEV_DEVICE=m > CONFIG_VIRTIO_PCI=m > CONFIG_VIRTIO_BALLOON=m > CONFIG_VIRTIO_INPUT=y > +CONFIG_VHOST=m > +CONFIG_VHOST_NET=m > +CONFIG_VHOST_VSOCK=m > CONFIG_S390_CCW_IOMMU=y > CONFIG_S390_AP_IOMMU=y > CONFIG_EXT4_FS=y > diff --git a/arch/s390/configs/defconfig b/arch...

...vers/vfio/mdev/Makefile index >> 101516fdf375..99d31e29c23e 100644 >> --- a/drivers/vfio/mdev/Makefile >> +++ b/drivers/vfio/mdev/Makefile >> @@ -4,3 +4,4 @@ mdev-y := mdev_core.o mdev_sysfs.o mdev_driver.o >> >> obj-$(CONFIG_VFIO_MDEV) += mdev.o >> obj-$(CONFIG_VFIO_MDEV_DEVICE) += vfio_mdev.o >> +obj-$(CONFIG_VIRTIO_MDEV_DEVICE) += virtio_mdev.o >> diff --git a/drivers/vfio/mdev/virtio_mdev.c b/drivers/vfio/mdev/virtio_mdev.c >> new file mode 100644 index 000000000000..919a082adc9c >> --- /dev/null >> +++ b/drivers/vfio/mdev/virtio_mdev.c &g...

...diated devices. diff --git a/drivers/vfio/mdev/Makefile b/drivers/vfio/mdev/Makefile index 101516fdf375..99d31e29c23e 100644 --- a/drivers/vfio/mdev/Makefile +++ b/drivers/vfio/mdev/Makefile @@ -4,3 +4,4 @@ mdev-y := mdev_core.o mdev_sysfs.o mdev_driver.o obj-$(CONFIG_VFIO_MDEV) += mdev.o obj-$(CONFIG_VFIO_MDEV_DEVICE) += vfio_mdev.o +obj-$(CONFIG_VIRTIO_MDEV_DEVICE) += virtio_mdev.o diff --git a/drivers/vfio/mdev/virtio_mdev.c b/drivers/vfio/mdev/virtio_mdev.c new file mode 100644 index 000000000000..5ff09089297e --- /dev/null +++ b/drivers/vfio/mdev/virtio_mdev.c @@ -0,0 +1,500 @@ +// SPDX-License-Identifier:...

...s/vfio/mdev/Makefile b/drivers/vfio/mdev/Makefile > index 101516fdf375..99d31e29c23e 100644 > --- a/drivers/vfio/mdev/Makefile > +++ b/drivers/vfio/mdev/Makefile > @@ -4,3 +4,4 @@ mdev-y := mdev_core.o mdev_sysfs.o mdev_driver.o > > obj-$(CONFIG_VFIO_MDEV) += mdev.o > obj-$(CONFIG_VFIO_MDEV_DEVICE) += vfio_mdev.o > +obj-$(CONFIG_VIRTIO_MDEV_DEVICE) += virtio_mdev.o > diff --git a/drivers/vfio/mdev/virtio_mdev.c b/drivers/vfio/mdev/virtio_mdev.c > new file mode 100644 > index 000000000000..5ff09089297e > --- /dev/null > +++ b/drivers/vfio/mdev/virtio_mdev.c > @@ -0,0 +1,5...

...s/vfio/mdev/Makefile b/drivers/vfio/mdev/Makefile > index 101516fdf375..99d31e29c23e 100644 > --- a/drivers/vfio/mdev/Makefile > +++ b/drivers/vfio/mdev/Makefile > @@ -4,3 +4,4 @@ mdev-y := mdev_core.o mdev_sysfs.o mdev_driver.o > > obj-$(CONFIG_VFIO_MDEV) += mdev.o > obj-$(CONFIG_VFIO_MDEV_DEVICE) += vfio_mdev.o > +obj-$(CONFIG_VIRTIO_MDEV_DEVICE) += virtio_mdev.o > diff --git a/drivers/vfio/mdev/virtio_mdev.c b/drivers/vfio/mdev/virtio_mdev.c > new file mode 100644 > index 000000000000..5ff09089297e > --- /dev/null > +++ b/drivers/vfio/mdev/virtio_mdev.c > @@ -0,0 +1,5...

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

This patch series aims to move the logical block size checking to the block code. This was inspired by missing check for valid logical block size in virtio-blk which causes the kernel to crash in a weird way later on when it is invalid. I added blk_is_valid_logical_block_size which returns true iff the block size is one of supported sizes. I added this check to virtio-blk, and also converted

This patch series aims to move the logical block size checking to the block code. This was inspired by missing check for valid logical block size in virtio-blk which causes the kernel to crash in a weird way later on when it is invalid. I added blk_is_valid_logical_block_size which returns true iff the block size is one of supported sizes. I added this check to virtio-blk, and also converted