[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-block] [PATCH v4 8/9] docs: Add section for NVMe VFIO driver
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-block] [PATCH v4 8/9] docs: Add section for NVMe VFIO driver |
Date: |
Wed, 10 Jan 2018 19:05:58 +0000 |
User-agent: |
Mutt/1.9.1 (2017-09-22) |
On Wed, Jan 10, 2018 at 05:18:45PM +0800, Fam Zheng wrote:
> Signed-off-by: Fam Zheng <address@hidden>
> ---
> docs/qemu-block-drivers.texi | 32 ++++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/docs/qemu-block-drivers.texi b/docs/qemu-block-drivers.texi
> index 503c1847aa..66b27cc4f7 100644
> --- a/docs/qemu-block-drivers.texi
> +++ b/docs/qemu-block-drivers.texi
> @@ -785,6 +785,38 @@ warning: ssh server @code{ssh.example.com:22} does not
> support fsync
> With sufficiently new versions of libssh2 and OpenSSH, @code{fsync} is
> supported.
>
> address@hidden disk_images_nvme
> address@hidden NVMe disk images
> +
> +You can access disk images on a NVMe controller with the built-in VFIO based
> +NVMe driver. Before starting QEMU, bind the host NVMe controller to vfio-pci.
The text dives straight into vfio-pci without any explanation of this
feature. Please include something like:
NVM Express (NVMe) storage controllers can be accessed directly by a
userspace driver in QEMU. This bypasses the host kernel file system and
block layers while retaining QEMU block layer functionality, such as
block jobs, I/O throttling, etc. Disk I/O performance is typically
higher than with -drive file=/dev/sda.
> +For example:
> +
> address@hidden
> +# modprobe vfio-pci
> +# lspci -n -s 0000:06:0d.0
> +06:0d.0 0401: 1102:0002 (rev 08)
> +# echo 0000:06:0d.0 > /sys/bus/pci/devices/0000:06:0d.0/driver/unbind
> +# echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id
> +
> +# qemu-system-x86_64 -drive
> file=nvme://@var{host}:@var{bus}:@address@hidden/@var{namespace}
> address@hidden example
> +
> +Alternative syntax using properties:
> +
> address@hidden
> +qemu-system-x86_64 -drive
> file.driver=nvme,address@hidden:@var{bus}:@address@hidden,address@hidden
> address@hidden example
> +
> address@hidden:@var{bus}:@address@hidden is the NVMe controller's PCI device
> +address on the host.
> +
> address@hidden is the NVMe namespace number, starting from 1.
> +
> +The controller will be exclusively used by the QEMU process once started. To
> be
> +able to share storage between multiple VMs and other applications on the
> host,
> +please use file based protocols.
I suggest moving this up to the beginning in the hopes that people will
read it before asking questions on IRC or qemu-devel :).
signature.asc
Description: PGP signature
- Re: [Qemu-block] [PATCH v4 3/9] block: Add VFIO based NVMe driver, (continued)
- [Qemu-block] [PATCH v4 4/9] block: Introduce buf register API, Fam Zheng, 2018/01/10
- [Qemu-block] [PATCH v4 5/9] block/nvme: Implement .bdrv_(un)register_buf, Fam Zheng, 2018/01/10
- [Qemu-block] [PATCH v4 6/9] qemu-img: Map bench buffer, Fam Zheng, 2018/01/10
- [Qemu-block] [PATCH v4 8/9] docs: Add section for NVMe VFIO driver, Fam Zheng, 2018/01/10
- Re: [Qemu-block] [PATCH v4 8/9] docs: Add section for NVMe VFIO driver,
Stefan Hajnoczi <=
- [Qemu-block] [PATCH v4 7/9] block: Move NVMe constants to a separate header, Fam Zheng, 2018/01/10
- [Qemu-block] [PATCH v4 9/9] qapi: Add NVMe driver options to the schema, Fam Zheng, 2018/01/10