From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PULL 10/14] block/nvme: Implement .bdrv_(un)register_buf
Date: Thu, 25 Jan 2018 13:46:44 +0800 [thread overview]
Message-ID: <20180125054648.18747-11-famz@redhat.com> (raw)
In-Reply-To: <20180125054648.18747-1-famz@redhat.com>
Forward these two calls to the IOVA manager.
Signed-off-by: Fam Zheng <famz@redhat.com>
Message-Id: <20180110091846.10699-6-famz@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20180116060901.17413-6-famz@redhat.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
---
block/nvme.c | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/block/nvme.c b/block/nvme.c
index 99cc7702ad..30616f50c7 100644
--- a/block/nvme.c
+++ b/block/nvme.c
@@ -1145,6 +1145,27 @@ static void nvme_aio_unplug(BlockDriverState *bs)
}
}
+static void nvme_register_buf(BlockDriverState *bs, void *host, size_t size)
+{
+ int ret;
+ BDRVNVMeState *s = bs->opaque;
+
+ ret = qemu_vfio_dma_map(s->vfio, host, size, false, NULL);
+ if (ret) {
+ /* FIXME: we may run out of IOVA addresses after repeated
+ * bdrv_register_buf/bdrv_unregister_buf, because nvme_vfio_dma_unmap
+ * doesn't reclaim addresses for fixed mappings. */
+ error_report("nvme_register_buf failed: %s", strerror(-ret));
+ }
+}
+
+static void nvme_unregister_buf(BlockDriverState *bs, void *host)
+{
+ BDRVNVMeState *s = bs->opaque;
+
+ qemu_vfio_dma_unmap(s->vfio, host);
+}
+
static BlockDriver bdrv_nvme = {
.format_name = "nvme",
.protocol_name = "nvme",
@@ -1170,6 +1191,9 @@ static BlockDriver bdrv_nvme = {
.bdrv_io_plug = nvme_aio_plug,
.bdrv_io_unplug = nvme_aio_unplug,
+
+ .bdrv_register_buf = nvme_register_buf,
+ .bdrv_unregister_buf = nvme_unregister_buf,
};
static void bdrv_nvme_init(void)
--
2.14.3
next prev parent reply other threads:[~2018-01-25 5:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 5:46 [Qemu-devel] [PULL 00/14] Block and docker patches Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 01/14] docker: change Fedora base image to fedora:27 Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 02/14] lockable: add QemuLockable Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 03/14] coroutine-lock: convert CoQueue to use QemuLockable Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 04/14] coroutine-lock: make qemu_co_enter_next thread-safe Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 05/14] curl: convert to CoQueue Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 06/14] stubs: Add stubs for ram block API Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 07/14] util: Introduce vfio helpers Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 08/14] block: Add VFIO based NVMe driver Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 09/14] block: Introduce buf register API Fam Zheng
2018-01-25 5:46 ` Fam Zheng [this message]
2018-01-25 5:46 ` [Qemu-devel] [PULL 11/14] qemu-img: Map bench buffer Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 12/14] block: Move NVMe constants to a separate header Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 13/14] docs: Add section for NVMe VFIO driver Fam Zheng
2018-01-25 5:46 ` [Qemu-devel] [PULL 14/14] qapi: Add NVMe driver options to the schema Fam Zheng
2018-01-25 13:51 ` [Qemu-devel] [PULL 00/14] Block and docker patches Peter Maydell
2018-01-25 14:16 ` 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=20180125054648.18747-11-famz@redhat.com \
--to=famz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).