2013-03-01 12:59:19 +00:00
|
|
|
common-obj-y += block.o cdrom.o hd-geometry.o
|
|
|
|
|
common-obj-$(CONFIG_FDC) += fdc.o
|
|
|
|
|
common-obj-$(CONFIG_SSI_M25P80) += m25p80.o
|
|
|
|
|
common-obj-$(CONFIG_NAND) += nand.o
|
|
|
|
|
common-obj-$(CONFIG_PFLASH_CFI01) += pflash_cfi01.o
|
|
|
|
|
common-obj-$(CONFIG_PFLASH_CFI02) += pflash_cfi02.o
|
2019-01-08 14:48:48 +00:00
|
|
|
common-obj-$(CONFIG_XEN) += xen-block.o
|
2013-03-01 12:59:19 +00:00
|
|
|
common-obj-$(CONFIG_ECC) += ecc.o
|
2013-02-05 11:55:04 +00:00
|
|
|
common-obj-$(CONFIG_ONENAND) += onenand.o
|
2013-06-04 15:17:10 +00:00
|
|
|
common-obj-$(CONFIG_NVME_PCI) += nvme.o
|
2013-02-05 11:55:04 +00:00
|
|
|
|
|
|
|
|
obj-$(CONFIG_SH4) += tc58128.o
|
2013-02-05 11:42:31 +00:00
|
|
|
|
2018-05-22 19:48:22 +00:00
|
|
|
obj-$(CONFIG_VIRTIO_BLK) += virtio-blk.o
|
vhost-user-blk: introduce a new vhost-user-blk host device
This commit introduces a new vhost-user device for block, it uses a
chardev to connect with the backend, same with Qemu virito-blk device,
Guest OS still uses the virtio-blk frontend driver.
To use it, start QEMU with command line like this:
qemu-system-x86_64 \
-chardev socket,id=char0,path=/path/vhost.socket \
-device vhost-user-blk-pci,chardev=char0,num-queues=2, \
bootindex=2... \
Users can use different parameters for `num-queues` and `bootindex`.
Different with exist Qemu virtio-blk host device, it makes more easy
for users to implement their own I/O processing logic, such as all
user space I/O stack against hardware block device. It uses the new
vhost messages(VHOST_USER_GET_CONFIG) to get block virtio config
information from backend process.
Signed-off-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2018-01-04 01:53:32 +00:00
|
|
|
obj-$(CONFIG_VHOST_USER_BLK) += vhost-user-blk.o
|
2019-02-07 17:37:38 +00:00
|
|
|
|
|
|
|
|
obj-y += dataplane/
|