From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Karl Rister <krister@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org
Subject: [Qemu-devel] [PATCH v2 0/6] block: Add VFIO based driver for NVMe device
Date: Thu, 23 Feb 2017 17:18:39 +0800 [thread overview]
Message-ID: <20170223091845.18523-1-famz@redhat.com> (raw)
This is a refresh of the NVMe VFIO driver patches.
The first three patches add the driver, the others are to make qemu-img more
efficient with the new driver.
v2:
- Implement "split vfio addr space" appraoch. [Paolo]
- Add back 'device reset' in nvme_close(). [Paolo]
- Better variable namings. [Stefan]
- "Reuse" macro definitions from NVMe emulation code.
- Rebase onto current master which has polling by default and update
performance results accordingly.
- Update MAINTAINERS.
- Specify namespace in URI.
- The sporadical I/O error from v1 "disappeared" in this version.
- Tests one: qemu-img bench, fio, bonnie++ and installation of
ubuntu/fedora/rhel on QEMU emulated nvme and a Intel P3700 card.
Fam Zheng (6):
nvme: Move NVMe definitions to a separate header
stubs: Add stubs for ram block notifier API
block: Add VFIO based NVMe driver
block: Introduce bdrv_dma_map and bdrv_dma_unmap
block/nvme: Implement .bdrv_dma_map and .bdrv_dma_unmap
qemu-img: dma map buffers
MAINTAINERS | 6 +
block/Makefile.objs | 1 +
block/block-backend.c | 10 +
block/io.c | 24 +
block/nvme-vfio.c | 664 +++++++++++++++++++++++++
block/nvme-vfio.h | 31 ++
block/nvme.c | 1073 ++++++++++++++++++++++++++++++++++++++++
block/trace-events | 27 +
hw/block/nvme.h | 629 +----------------------
include/block/block.h | 2 +
include/block/block_int.h | 4 +
include/block/nvme.h | 632 +++++++++++++++++++++++
include/sysemu/block-backend.h | 3 +
qemu-img.c | 15 +
stubs/Makefile.objs | 1 +
stubs/ram-block-notifier.c | 10 +
16 files changed, 2504 insertions(+), 628 deletions(-)
create mode 100644 block/nvme-vfio.c
create mode 100644 block/nvme-vfio.h
create mode 100644 block/nvme.c
create mode 100644 include/block/nvme.h
create mode 100644 stubs/ram-block-notifier.c
--
2.9.3
next reply other threads:[~2017-02-23 9:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 9:18 Fam Zheng [this message]
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 1/6] nvme: Move NVMe definitions to a separate header Fam Zheng
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 2/6] stubs: Add stubs for ram block notifier API Fam Zheng
2017-02-23 9:49 ` Paolo Bonzini
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 3/6] block: Add VFIO based NVMe driver Fam Zheng
2017-02-23 9:43 ` Paolo Bonzini
2017-02-23 10:01 ` Fam Zheng
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 4/6] block: Introduce bdrv_dma_map and bdrv_dma_unmap Fam Zheng
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 5/6] block/nvme: Implement .bdrv_dma_map and .bdrv_dma_unmap Fam Zheng
2017-02-23 9:18 ` [Qemu-devel] [PATCH v2 6/6] qemu-img: dma map buffers Fam Zheng
2017-02-23 9:28 ` [Qemu-devel] [PATCH v2 0/6] block: Add VFIO based driver for NVMe device no-reply
2017-02-23 10:48 ` Fam Zheng
2017-02-23 10:50 ` Paolo Bonzini
2017-02-23 11:19 ` Fam Zheng
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=20170223091845.18523-1-famz@redhat.com \
--to=famz@redhat.com \
--cc=krister@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).