From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Longpeng(Mike)" <longpeng2@huawei.com>
Cc: stefanha@redhat.com, jasowang@redhat.com, sgarzare@redhat.com,
cohuck@redhat.com, pbonzini@redhat.com, arei.gonglei@huawei.com,
yechuan@huawei.com, huangzhichao@huawei.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH v10 5/5] docs: Add generic vhost-vdpa device documentation
Date: Tue, 20 Dec 2022 10:27:32 -0500 [thread overview]
Message-ID: <20221220102712-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221205084943.2259-6-longpeng2@huawei.com>
On Mon, Dec 05, 2022 at 04:49:43PM +0800, Longpeng(Mike) wrote:
> From: Longpeng <longpeng2@huawei.com>
>
> Signed-off-by: Longpeng <longpeng2@huawei.com>
Dropped 5/5 for now due to comments and build errors.
> ---
> .../devices/vhost-vdpa-generic-device.rst | 66 +++++++++++++++++++
> 1 file changed, 66 insertions(+)
> create mode 100644 docs/system/devices/vhost-vdpa-generic-device.rst
>
> diff --git a/docs/system/devices/vhost-vdpa-generic-device.rst b/docs/system/devices/vhost-vdpa-generic-device.rst
> new file mode 100644
> index 0000000000..7d13359ea1
> --- /dev/null
> +++ b/docs/system/devices/vhost-vdpa-generic-device.rst
> @@ -0,0 +1,66 @@
> +
> +=========================
> +vhost-vDPA generic device
> +=========================
> +
> +This document explains the usage of the vhost-vDPA generic device.
> +
> +Description
> +-----------
> +
> +vDPA(virtio data path acceleration) device is a device that uses a datapath
> +which complies with the virtio specifications with vendor specific control
> +path.
> +
> +QEMU provides two types of vhost-vDPA devices to enable the vDPA device, one
> +is type sensitive which means QEMU needs to know the actual device type
> +(e.g. net, blk, scsi) and another is called "vhost-vDPA generic device" which
> +is type insensitive.
> +
> +The vhost-vDPA generic device builds on the vhost-vdpa subsystem and virtio
> +subsystem. It is quite small, but it can support any type of virtio device.
> +
> +Examples
> +--------
> +
> +1. Please make sure the modules listed bellow are installed:
> + vhost.ko
> + vhost_iotlb.ko
> + vdpa.ko
> + vhost_vdpa.ko
> +
> +
> +2. Prepare the vhost-vDPA backends, here is an example using vdpa_sim_blk
> + device:
> +
> +::
> + host# modprobe vdpa_sim_blk
> + host# vdpa dev add mgmtdev vdpasim_blk name blk0
> + (...you can see the vhost-vDPA device under /dev directory now...)
> + host# ls -l /dev/vhost-vdpa-*
> + crw------- 1 root root 236, 0 Nov 2 00:49 /dev/vhost-vdpa-0
> +
> +Note:
> +It needs some vendor-specific steps to provision the vDPA device if you're
> +using real HW devices, such as installing the vendor-specific vDPA driver
> +and binding the device to the driver.
> +
> +
> +3. Start the virtual machine:
> +
> +Start QEMU with virtio-mmio bus:
> +
> +::
> + host# qemu-system \
> + -M microvm -m 512 -smp 2 -kernel ... -initrd ... \
> + -device vhost-vdpa-device,vhostdev=/dev/vhost-vdpa-0 \
> + ...
> +
> +
> +Start QEMU with virtio-pci bus:
> +
> +::
> + host# qemu-system \
> + -M pc -m 512 -smp 2 \
> + -device vhost-vdpa-device-pci,vhostdev=/dev/vhost-vdpa-0 \
> + ...
> --
> 2.23.0
next prev parent reply other threads:[~2022-12-20 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 8:49 [PATCH v10 0/5] add generic vDPA device support Longpeng(Mike) via
2022-12-05 8:49 ` [PATCH v10 1/5] virtio: get class_id and pci device id by the virtio id Longpeng(Mike) via
2022-12-05 8:49 ` [PATCH v10 2/5] vdpa: add vdpa-dev support Longpeng(Mike) via
2022-12-05 8:49 ` [PATCH v10 3/5] vdpa: add vdpa-dev-pci support Longpeng(Mike) via
2022-12-05 8:49 ` [PATCH v10 4/5] vdpa-dev: mark the device as unmigratable Longpeng(Mike) via
2022-12-05 8:49 ` [PATCH v10 5/5] docs: Add generic vhost-vdpa device documentation Longpeng(Mike) via
2022-12-13 14:35 ` Stefano Garzarella
2022-12-13 15:37 ` longpeng2--- via
2022-12-13 15:49 ` Stefano Garzarella
2022-12-20 15:27 ` Michael S. Tsirkin [this message]
2022-12-20 15:26 ` [PATCH v10 0/5] add generic vDPA device support Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221220102712-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=cohuck@redhat.com \
--cc=huangzhichao@huawei.com \
--cc=jasowang@redhat.com \
--cc=longpeng2@huawei.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=yechuan@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).