kvm "fake DAX" device flushing
Subsystems (4)
v3 cover kvm "fake DAX" device flushing
This is RFC V3 for 'fake DAX' flushing interface sharing for review. This patchset has two parts:
- Guest virtio-pmem driver
Guest driver reads persistent memory range from paravirt device and registers with 'nvdimm_bus'. 'nvdimm/pmem' driver uses this information to allocate persistent memory range. Also, we have implemented guest side of VIRTIO flushing interface.
- Qemu virtio-pmem device
It exposes a persistent memory range to KVM guest which at host side is file backed memory and works as persistent memory device. In addition to this it provides virtio device handling of flushing interface. KVM guest performs Qemu side asynchronous sync using this interface.
Changes from RFC v2:
- Add flush function in the nd_region in place of switching on a flag - Dan & Stefan
- Add flush completion function with proper locking and wait for host side flush completion - Stefan & Dan
- Keep userspace API in uapi header file - Stefan, MST
- Use LE fields & New device id - MST
- Indentation & spacing suggestions - MST & Eric
- Remove extra header files & add licensing - Stefan
Changes from RFC v1:
- Reuse existing 'pmem' code for registering persistent memory and other operations instead of creating an entirely new block driver.
- Use VIRTIO driver to register memory information with nvdimm_bus and create region_type accordingly.
- Call VIRTIO flush from existing pmem driver.
Details of project idea for 'fake DAX' flushing interface is shared [2] & [3].
Pankaj Gupta (2):
Add virtio-pmem guest driver
pmem: device flush over VIRTIO
[1] https://marc.info/?l=linux-mm&m=150782346802290&w=2
[2] https://www.spinics.net/lists/kvm/msg149761.html
[3] https://www.spinics.net/lists/kvm/msg153095.html
drivers/nvdimm/nd.h | 1 drivers/nvdimm/pmem.c | 4 drivers/nvdimm/region_devs.c | 24 +++- drivers/virtio/Kconfig | 9 + drivers/virtio/Makefile | 1 drivers/virtio/virtio_pmem.c | 190 +++++++++++++++++++++++++++++++++++++++ include/linux/libnvdimm.h | 5 - include/linux/virtio_pmem.h | 44 +++++++++ include/uapi/linux/virtio_ids.h | 1 include/uapi/linux/virtio_pmem.h | 40 ++++++++ 10 files changed, 310 insertions(+), 9 deletions(-)
RFC v3 1/2 libnvdimm: Add flush callback for virtio pmem
This patch adds functionality to perform flush from guest to host over VIRTIO. We are registering a callback based on 'nd_region' type. As virtio_pmem driver requires this special flush interface, for rest of the region types we are registering existing flush function. Also report the error returned by virtio flush interface.
--- drivers/nvdimm/nd.h | 1 + drivers/nvdimm/pmem.c | 4 ++-- drivers/nvdimm/region_devs.c | 24 ++++++++++++++++++------ include/linux/libnvdimm.h | 5 ++++- 4 files changed, 25 insertions(+), 9 deletions(-)
drivers/nvdimm/nd.h +1 -0
@@ -159,6 +159,7 @@ struct nd_region {struct badblocks bb;struct nd_interleave_set *nd_set;struct nd_percpu_lane __percpu *lane; +int (*flush)(struct device *dev);struct nd_mapping mapping[0 ]; };
drivers/nvdimm/pmem.c +2 -2
@@ -180,7 +180,7 @@ static blk_qc_t pmem_make_request(struct request_queue *q, struct bio *bio)struct nd_region *nd_region =to_region (pmem);if (bio->bi_opf &REQ_FLUSH ) -nvdimm_flush (nd_region); + bio->bi_status =nvdimm_flush (nd_region); do_acct =nd_iostat_start (bio, &start);bio_for_each_segment (bvec, bio, iter) {
@@ -196,7 +196,7 @@ static blk_qc_t pmem_make_request(struct request_queue *q, struct bio *bio)nd_iostat_end (bio, start);if (bio->bi_opf &REQ_FUA ) -nvdimm_flush (nd_region); + bio->bi_status =nvdimm_flush (nd_region);bio_endio (bio);return BLK_QC_T_NONE ;
drivers/nvdimm/region_devs.c +18 -6
@@ -1025,6 +1025,7 @@ static struct nd_region *nd_region_create(struct nvdimm_bus *nvdimm_bus, dev->of_node = ndr_desc->of_node; nd_region->ndr_size =resource_size (ndr_desc->res); nd_region->ndr_start = ndr_desc->res->start; + nd_region->flush = ndr_desc->flush;nd_device_register (dev);return nd_region;
@@ -1065,13 +1066,10 @@ struct nd_region *nvdimm_volatile_region_create(struct nvdimm_bus *nvdimm_bus, }EXPORT_SYMBOL_GPL (nvdimm_volatile_region_create); -/** -* nvdimm_flush - flush any posted write queues between the cpu and pmem media -* @nd_region: blk or interleaved pmem region -*/ -void nvdimm_flush (struct nd_region *nd_region) +void pmem_flush (struct device *dev) { -struct nd_region_data *ndrd =dev_get_drvdata (&nd_region->dev); +struct nd_region_data *ndrd =dev_get_drvdata (dev); +struct nd_region *nd_region =to_nd_region (dev);int i, idx;/*
@@ -1094,6 +1092,20 @@ void nvdimm_flush(struct nd_region *nd_region)writeq (1 ,ndrd_get_flush_wpq (ndrd, i, idx));wmb (); } + +/** +* nvdimm_flush - flush any posted write queues between the cpu and pmem media +* @nd_region: blk or interleaved pmem region +*/ +int nvdimm_flush (struct nd_region *nd_region) +{ +if (nd_region->flush) +return (nd_region->flush (&nd_region->dev)); + +pmem_flush (&nd_region->dev); + +return 0 ; +}EXPORT_SYMBOL_GPL (nvdimm_flush);/**
include/linux/libnvdimm.h +4 -1
@@ -126,6 +126,7 @@ struct nd_region_desc {int numa_node;unsigned long flags;struct device_node *of_node; +int (*flush)(struct device *dev); };struct device ;
@@ -201,7 +202,9 @@ unsigned long nd_blk_memremap_flags(struct nd_blk_region *ndbr);unsigned int nd_region_acquire_lane (struct nd_region *nd_region);void nd_region_release_lane (struct nd_region *nd_region,unsigned int lane);u64 nd_fletcher64 (void *addr,size_t len,bool le); -void nvdimm_flush (struct nd_region *nd_region); +int nvdimm_flush (struct nd_region *nd_region); +void pmem_set_flush (struct nd_region *nd_region,void (*flush) + (struct device *));int nvdimm_has_flush (struct nd_region *nd_region);int nvdimm_has_cache (struct nd_region *nd_region);
Signature · 1 line
2.9.3
Re: [RFC v3 1/2] libnvdimm: Add flush callback for virtio pmem
Quoted 5 lines · On Fri, 13 Jul 2018 13:22:30 +0530 Pankaj Gupta <[email protected]> wrote:
This patch adds functionality to perform flush from guest to host over VIRTIO. We are registering a callback based on '
nd_region' type. Asvirtio_pmemdriver requires this special flush interface, for rest of the region types we are registering existing flush function. Also report the error returned by virtio flush interface.
This patch doesn't apply against latest upstream. A few more comments below.
Quoted 77 lines
Signed-off-by Pankaj Gupta <[email protected]>--- drivers/nvdimm/nd.h | 1 + drivers/nvdimm/pmem.c | 4 ++-- drivers/nvdimm/region_devs.c | 24 ++++++++++++++++++------ include/linux/libnvdimm.h | 5 ++++- 4 files changed, 25 insertions(+), 9 deletions(-)drivers/nvdimm/nd.h +1
-0@@ -159,6 +159,7 @@ struct nd_region {struct badblocks bb;struct nd_interleave_set *nd_set;struct nd_percpu_lane __percpu *lane; +int (*flush)(struct device *dev);struct nd_mapping mapping[0 ]; };drivers/nvdimm/pmem.c +2
-2@@ -180,7 +180,7 @@ static blk_qc_t pmem_make_request(struct request_queue *q, struct bio *bio)struct nd_region *nd_region =to_region (pmem);if (bio->bi_opf &REQ_FLUSH ) -nvdimm_flush (nd_region); + bio->bi_status =nvdimm_flush (nd_region); do_acct =nd_iostat_start (bio, &start);bio_for_each_segment (bvec, bio, iter) {@@ -196,7 +196,7 @@ static blk_qc_t pmem_make_request(struct request_queue *q, struct bio *bio)nd_iostat_end (bio, start);if (bio->bi_opf &REQ_FUA ) -nvdimm_flush (nd_region); + bio->bi_status =nvdimm_flush (nd_region);bio_endio (bio);return BLK_QC_T_NONE ;drivers/nvdimm/region_devs.c +5
-6@@ -1025,6 +1025,7 @@ static struct nd_region *nd_region_create(struct nvdimm_bus *nvdimm_bus, dev->of_node = ndr_desc->of_node; nd_region->ndr_size =resource_size (ndr_desc->res); nd_region->ndr_start = ndr_desc->res->start; + nd_region->flush = ndr_desc->flush;nd_device_register (dev);return nd_region;@@ -1065,13 +1066,10 @@ struct nd_region *nvdimm_volatile_region_create(struct nvdimm_bus *nvdimm_bus, }EXPORT_SYMBOL_GPL (nvdimm_volatile_region_create); -/** -* nvdimm_flush - flush any posted write queues between the cpu and pmem media -* @nd_region: blk or interleaved pmem region -*/ -void nvdimm_flush (struct nd_region *nd_region) +void pmem_flush (struct device *dev) { -struct nd_region_data *ndrd =dev_get_drvdata (&nd_region->dev); +struct nd_region_data *ndrd =dev_get_drvdata (dev); +struct nd_region *nd_region =to_nd_region (dev);int i, idx;/* @@ -1094,6 +1092,20 @@ void nvdimm_flush(struct nd_region *nd_region)writeq (1 ,ndrd_get_flush_wpq (ndrd, i, idx));wmb (); } +
drivers/nvdimm/region_devs.c void nvdimm_flush(struct nd_region *nd_region) · line 1105
Quoted 10 lines
drivers/nvdimm/region_devs.c +10
-0+/** +* nvdimm_flush - flush any posted write queues between the cpu and pmem media +* @nd_region: blk or interleaved pmem region +*/ +int nvdimm_flush (struct nd_region *nd_region) +{ +if (nd_region->flush) +return (nd_region->flush (&nd_region->dev)); + +pmem_flush (&nd_region->dev);
IMHO, a better way of doing this would be to allow nvdimm_flush() to be overridden. That is, in nd_region_create() you set nd_region->flush to the original nvdimm_flush() if ndr_desc->flush is NULL. And then always call nd_region->flush() where nvdimm_flush() is called today.
Quoted 19 lines
drivers/nvdimm/region_devs.c +3
-0+ +return 0 ; +}EXPORT_SYMBOL_GPL (nvdimm_flush);/** include/linux/libnvdimm.h +1
-0@@ -126,6 +126,7 @@ struct nd_region_desc {int numa_node;unsigned long flags;struct device_node *of_node; +int (*flush)(struct device *dev); };struct device ;
include/linux/libnvdimm.h unsigned long nd_blk_memremap_flags(struct nd_blk_region *ndbr); · line 207
Quoted 7 lines
include/linux/libnvdimm.h +3
-1@@ -201,7 +202,9 @@ unsigned long nd_blk_memremap_flags(struct nd_blk_region *ndbr);unsigned int nd_region_acquire_lane (struct nd_region *nd_region);void nd_region_release_lane (struct nd_region *nd_region,unsigned int lane);u64 nd_fletcher64 (void *addr,size_t len,bool le); -void nvdimm_flush (struct nd_region *nd_region); +int nvdimm_flush (struct nd_region *nd_region); +void pmem_set_flush (struct nd_region *nd_region,void (*flush) + (struct device *));
It seems pmem_set_flush() doesn't exist.
Quoted 3 lines
include/linux/libnvdimm.h +0
-0int nvdimm_has_flush (struct nd_region *nd_region);int nvdimm_has_cache (struct nd_region *nd_region);
Re: [RFC v3 1/2] libnvdimm: Add flush callback for virtio pmem
Hi Luiz,
Quoted 9 lines
Quoted 6 lines
This patch adds functionality to perform flush from guest to host over VIRTIO. We are registering a callback based on '
nd_region' type. Asvirtio_pmemdriver requires this special flush interface, for rest of the region types we are registering existing flush function. Also report the error returned by virtio flush interface.This patch doesn't apply against latest upstream. A few more comments below.
My bad, I tested it with 4.17-rc1. Will rebase it.
Quoted 91 lines
Quoted 91 lines
Signed-off-by Pankaj Gupta <[email protected]>--- drivers/nvdimm/nd.h | 1 + drivers/nvdimm/pmem.c | 4 ++-- drivers/nvdimm/region_devs.c | 24 ++++++++++++++++++------ include/linux/libnvdimm.h | 5 ++++- 4 files changed, 25 insertions(+), 9 deletions(-)drivers/nvdimm/nd.h +1
-0@@ -159,6 +159,7 @@ struct nd_region {struct badblocks bb;struct nd_interleave_set *nd_set;struct nd_percpu_lane __percpu *lane; +int (*flush)(struct device *dev);struct nd_mapping mapping[0 ]; };drivers/nvdimm/pmem.c +1
-1@@ -180,7 +180,7 @@ static blk_qc_t pmem_make_request(struct request_queue *q, struct bio *bio)struct nd_region *nd_region =to_region (pmem);if (bio->bi_opf &REQ_FLUSH ) -nvdimm_flush (nd_region); + bio->bi_status =nvdimm_flush (nd_region); do_acct =nd_iostat_start (bio, &start);drivers/nvdimm/pmem.c +1
-1bio_for_each_segment (bvec, bio, iter) {@@ -196,7 +196,7 @@ static blk_qc_t pmem_make_request(struct request_queue *q, struct bio *bio)nd_iostat_end (bio, start);if (bio->bi_opf &REQ_FUA ) -nvdimm_flush (nd_region); + bio->bi_status =nvdimm_flush (nd_region);bio_endio (bio);drivers/nvdimm/pmem.c +0
-0return BLK_QC_T_NONE ;drivers/nvdimm/region_devs.c +1
-0@@ -1025,6 +1025,7 @@ static struct nd_region *nd_region_create(struct nvdimm_bus *nvdimm_bus, dev->of_node = ndr_desc->of_node; nd_region->ndr_size =resource_size (ndr_desc->res); nd_region->ndr_start = ndr_desc->res->start; + nd_region->flush = ndr_desc->flush;nd_device_register (dev);drivers/nvdimm/region_devs.c +0
-2return nd_region;@@ -1065,13 +1066,10 @@ struct nd_region *nvdimm_volatile_region_create(struct nvdimm_bus *nvdimm_bus, } EXPORT_SYMBOL_GPL(nvdimm_volatile_region_create); -/** -* nvdimm_flush - flush any posted write queues between the cpu and pmem media
- * @nd_region: blk or interleaved pmem region
- */drivers/nvdimm/region_devs.c +6
-2-void nvdimm_flush (struct nd_region *nd_region) +void pmem_flush (struct device *dev) { -struct nd_region_data *ndrd =dev_get_drvdata (&nd_region->dev); +struct nd_region_data *ndrd =dev_get_drvdata (dev); +struct nd_region *nd_region =to_nd_region (dev);int i, idx;/* @@ -1094,6 +1092,20 @@ void nvdimm_flush(struct nd_region *nd_region)writeq (1 ,ndrd_get_flush_wpq (ndrd, i, idx));wmb (); } + +/** +* nvdimm_flush - flush any posted write queues between the cpu and pmem media
+ * @nd_region: blk or interleaved pmem region
+ */drivers/nvdimm/region_devs.c +3
-0+int nvdimm_flush (struct nd_region *nd_region) +{ +if (nd_region->flush)
Quoted 8 lines
drivers/nvdimm/region_devs.c void nvdimm_flush(struct nd_region *nd_region) · line 1105
Quoted 3 lines
drivers/nvdimm/region_devs.c +3
-0+return (nd_region->flush (&nd_region->dev)); + +pmem_flush (&nd_region->dev);IMHO, a better way of doing this would be to allow
nvdimm_flush()to be overridden. That is, innd_region_create()you setnd_region->flushto the originalnvdimm_flush()ifndr_desc->flushis NULL. And then always callnd_region->flush()wherenvdimm_flush()is called today.
I wanted to do minimal changes for actual 'nvdimm_flush' function because it does not return an error or return status for fsync. So, I needed to differentiate between 'fake DAX' & 'NVDIMM' at the time of calling 'flush', otherwise I need to change 'nvdimm_flush' to return zero for all the calls.
Looks like I am already doing this, will change as suggested.
Quoted 18 lines
Quoted 18 lines
drivers/nvdimm/region_devs.c +3
-0+ +return 0 ; +}EXPORT_SYMBOL_GPL (nvdimm_flush);/** include/linux/libnvdimm.h +1
-0@@ -126,6 +126,7 @@ struct nd_region_desc {int numa_node;unsigned long flags;struct device_node *of_node; +int (*flush)(struct device *dev); };
Quoted 13 lines
include/linux/libnvdimm.h unsigned long nd_blk_memremap_flags(struct · line 209
Quoted 11 lines
include/linux/libnvdimm.h +3
-1struct device ;@@ -201,7 +202,9 @@ unsigned long nd_blk_memremap_flags(struct nd_blk_region *ndbr);unsigned int nd_region_acquire_lane (struct nd_region *nd_region);void nd_region_release_lane (struct nd_region *nd_region,unsigned int lane);u64 nd_fletcher64 (void *addr,size_t len,bool le); -void nvdimm_flush (struct nd_region *nd_region); +int nvdimm_flush (struct nd_region *nd_region); +void pmem_set_flush (struct nd_region *nd_region,void (*flush) + (struct device *));It seems
pmem_set_flush()doesn't exist.
Sorry! will remove it.
Quoted 6 lines
Quoted 4 lines
include/linux/libnvdimm.h +0
-0int nvdimm_has_flush (struct nd_region *nd_region);int
nvdimm_has_cache(struct nd_region *nd_region);
Thanks,
Pankaj
RFC v3 2/2 virtio-pmem: Add virtio pmem driver
In reply to Pankaj GuptaThis patch adds virtio-pmem driver for KVM guest.
Guest reads the persistent memory range information from Qemu over VIRTIO and registers it on nvdimm_bus. It also creates a nd_region object with the persistent memory range information so that existing 'nvdimm/pmem' driver can reserve this into system memory map. This way 'virtio-pmem' driver uses existing functionality of pmem driver to register persistent memory compatible for DAX capable filesystems.
This also provides function to perform guest flush over VIRTIO from 'pmem' driver when userspace performs flush on DAX memory range.
--- drivers/virtio/Kconfig | 9 ++ drivers/virtio/Makefile | 1 + drivers/virtio/virtio_pmem.c | 190 +++++++++++++++++++++++++++++++++++++++ include/linux/virtio_pmem.h | 44 +++++++++ include/uapi/linux/virtio_ids.h | 1 + include/uapi/linux/virtio_pmem.h | 40 +++++++++ 6 files changed, 285 insertions(+) create mode 100644 drivers/virtio/virtio_pmem.c create mode 100644 include/linux/virtio_pmem.h create mode 100644 include/uapi/linux/virtio_pmem.h
drivers/virtio/Kconfig +9 -0
@@ -42,6 +42,15 @@ config VIRTIO_PCI_LEGACY If unsure, say Y. +config VIRTIO_PMEM + tristate "Support for virtio pmem driver" + depends on VIRTIO + help + This driver provides support for virtio based flushing interface + for persistent memory range. + + If unsure, say M. + config VIRTIO_BALLOON tristate "Virtio balloon driver" depends on VIRTIO
drivers/virtio/Makefile +1 -0
@@ -6,3 +6,4 @@ virtio_pci-y := virtio_pci_modern.o virtio_pci_common.o virtio_pci-$(CONFIG_VIRTIO_PCI_LEGACY) += virtio_pci_legacy.o obj-$(CONFIG_VIRTIO_BALLOON) += virtio_balloon.o obj-$(CONFIG_VIRTIO_INPUT) += virtio_input.o +obj-$(CONFIG_VIRTIO_PMEM) += virtio_pmem.o
drivers/virtio/virtio_pmem.c new file +190 -0
190 lines not on this page · raw message
include/linux/virtio_pmem.h new file +44 -0
44 lines not on this page · raw message
include/uapi/linux/virtio_ids.h +1 -0
@@ -43,5 +43,6 @@#define VIRTIO_ID_INPUT 18/* virtio input */ #define VIRTIO_ID_VSOCK 19/* virtio vsock transport */ #define VIRTIO_ID_CRYPTO 20/* virtio crypto */ +#define VIRTIO_ID_PMEM 25/* virtio pmem */ #endif /* _LINUX_VIRTIO_IDS_H */
include/uapi/linux/virtio_pmem.h new file +40 -0
@@ -0,0 +1,40 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* This header, excluding the #ifdef __KERNEL__ part, is BSD licensed so +* anyone can use the definitions to implement compatible drivers/servers: +* +* +* Redistribution and use in source and binary forms, with or without +* modification, are permitted provided that the following conditions +* are met: +* 1. Redistributions of source code must retain the above copyright +* notice, this list of conditions and the following disclaimer. +* 2. Redistributions in binary form must reproduce the above copyright +* notice, this list of conditions and the following disclaimer in the +* documentation and/or other materials provided with the distribution. +* 3. Neither the name of IBM nor the names of its contributors +* may be used to endorse or promote products derived from this software +* without specific prior written permission. +* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' +* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +* ARE DISCLAIMED. IN NO EVENT SHALL IBM OR CONTRIBUTORS BE LIABLE +* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +* SUCH DAMAGE. +* +* Copyright (C) Red Hat, Inc., 2018-2019 +* Copyright (C) Pankaj Gupta <[email protected]>, 2018 +*/ +#ifndef _UAPI_LINUX_VIRTIO_PMEM_H +#define _UAPI_LINUX_VIRTIO_PMEM_H + +struct virtio_pmem_config { +__le64 start; +__le64 size; +}; +#endif
Signature · 1 line
2.9.3
Re: [RFC v3 2/2] virtio-pmem: Add virtio pmem driver
Quoted 81 lines · On Fri, 13 Jul 2018 13:22:31 +0530 Pankaj Gupta…
This patch adds virtio-pmem driver for KVM guest.
Guest reads the persistent memory range information from Qemu over VIRTIO and registers it on
nvdimm_bus. It also creates and_regionobject with the persistent memory range information so that existing 'nvdimm/pmem' driver can reserve this into system memory map. This way 'virtio-pmem' driver uses existing functionality of pmem driver to register persistent memory compatible for DAX capable filesystems.This also provides function to perform guest flush over VIRTIO from 'pmem' driver when userspace performs flush on DAX memory range.
Signed-off-by Pankaj Gupta <[email protected]>--- drivers/virtio/Kconfig | 9 ++ drivers/virtio/Makefile | 1 + drivers/virtio/virtio_pmem.c | 190 +++++++++++++++++++++++++++++++++++++++ include/linux/virtio_pmem.h | 44 +++++++++ include/uapi/linux/virtio_ids.h | 1 + include/uapi/linux/virtio_pmem.h | 40 +++++++++ 6 files changed, 285 insertions(+) create mode 100644 drivers/virtio/virtio_pmem.c create mode 100644 include/linux/virtio_pmem.h create mode 100644 include/uapi/linux/virtio_pmem.hdrivers/virtio/Kconfig +9
-0@@ -42,6 +42,15 @@ config VIRTIO_PCI_LEGACY If unsure, say Y. +config VIRTIO_PMEM + tristate "Support for virtio pmem driver" + depends on VIRTIO + help + This driver provides support for virtio based flushing interface + for persistent memory range. + + If unsure, say M. + config VIRTIO_BALLOON tristate "Virtio balloon driver" depends on VIRTIOdrivers/virtio/Makefile +1
-0@@ -6,3 +6,4 @@ virtio_pci-y := virtio_pci_modern.o virtio_pci_common.o virtio_pci-$(CONFIG_VIRTIO_PCI_LEGACY) += virtio_pci_legacy.o obj-$(CONFIG_VIRTIO_BALLOON) += virtio_balloon.o obj-$(CONFIG_VIRTIO_INPUT) += virtio_input.o +obj-$(CONFIG_VIRTIO_PMEM) += virtio_pmem.odrivers/virtio/virtio_pmem.c new file +21
-0@@ -0,0 +1,190 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* virtio_pmem.c: Virtio pmem Driver +* +* Discovers persistent memory range information +* from host and provides a virtio based flushing +* interface. +*/ +#include <linux/virtio.h> +#include <linux/module.h> +#include <linux/virtio_pmem.h> + +static struct virtio_device_id id_table[] = { + {VIRTIO_ID_PMEM ,VIRTIO_DEV_ANY_ID }, + {0 }, +}; + +/* The interrupt handler */ +static void host_ack (struct virtqueue *vq) +{ +unsigned int len;
drivers/virtio/virtio_pmem.c line 31
Quoted 10 lines
drivers/virtio/virtio_pmem.c new file +10
-0+unsigned long flags; +struct virtio_pmem_request *req; +struct virtio_pmem *vpmem = vq->vdev->priv; + +spin_lock_irqsave (&vpmem->pmem_lock, flags); +while ((req =virtqueue_get_buf (vq, &len)) !=NULL ) { + req->done = true; +wake_up (&req->acked); + } +spin_unlock_irqrestore (&vpmem->pmem_lock, flags);
Honest question: why do you need to disable interrupts here?
Quoted 15 lines
drivers/virtio/virtio_pmem.c new file +15
-0+} +/* Initialize virt queue */ +static int init_vq (struct virtio_pmem *vpmem) +{ +struct virtqueue *vq; + +/* single vq */ + vpmem->req_vq = vq =virtio_find_single_vq (vpmem->vdev, + host_ack,"flush_queue" ); +if (IS_ERR (vq)) +return PTR_ERR (vq); +spin_lock_init (&vpmem->pmem_lock); + +return 0 ; +};
drivers/virtio/virtio_pmem.c line 56
Quoted 10 lines
drivers/virtio/virtio_pmem.c new file +10
-0+ +/* The request submission function */ +static int virtio_pmem_flush (struct device *dev) +{ +int err; +unsigned long flags; +struct scatterlist *sgs[2 ], sg, ret; +struct virtio_device *vdev =dev_to_virtio (dev->parent->parent); +struct virtio_pmem *vpmem = vdev->priv; +struct virtio_pmem_request *req =kmalloc (sizeof (*req),GFP_KERNEL );
Not checking kmalloc() return.
drivers/virtio/virtio_pmem.c line 60
Quoted 4 lines
drivers/virtio/virtio_pmem.c new file +4
-0+ + req->done = false; +init_waitqueue_head (&req->acked); +spin_lock_irqsave (&vpmem->pmem_lock, flags);
Why do you need spin_lock_irqsave()? There are two points consider:
1. Will virtio_pmem_flush() ever be called with interrupts disabled? If yes, then it's broken since you should be using GFP_ATOMIC in the kmalloc() call and you can't call wait_event()
2. If virtio_pmem_flush() is never called with interrupts disabled, do you really need to disable interrupts? If yes, why?
Another point to consider is whether or not virtio_pmem_flush() can be called from atomic context. nvdimm_flush() itself is called from a few atomic sites, but I can't tell if virtio_pmem_flush() will ever be called from those sites. If it can be called atomic context, then item 1 applies here. If you're sure it can't, then you should probably call might_sleep().
Quoted 237 lines
drivers/virtio/virtio_pmem.c new file +130
-0+ +sg_init_one (&sg, req,sizeof (req)); + sgs[0 ] = &sg; +sg_init_one (&ret, &req->ret,sizeof (req->ret)); + sgs[1 ] = &ret; + err =virtqueue_add_sgs (vpmem->req_vq, sgs,1 ,1 , req,GFP_ATOMIC ); +if (err) { +dev_err (&vdev->dev,"failed to send command to virtio pmem device\n" ); +spin_unlock_irqrestore (&vpmem->pmem_lock, flags); +return -ENOSPC ; + } +virtqueue_kick (vpmem->req_vq); +spin_unlock_irqrestore (&vpmem->pmem_lock, flags); + +/* When host has read buffer, this completes via host_ack */ +wait_event (req->acked, req->done); + err = req->ret; +kfree (req); + +return err; +}; + +static int virtio_pmem_probe (struct virtio_device *vdev) +{ +int err =0 ; +struct resource res; +struct virtio_pmem *vpmem; +struct nvdimm_bus *nvdimm_bus; +struct nd_region_desc ndr_desc; +int nid =dev_to_node (&vdev->dev); +struct nd_region *nd_region; + +if (!vdev->config->get) { +dev_err (&vdev->dev,"%s failure: config disabled\n" , + __func__); +return -EINVAL ; + } + + vdev->priv = vpmem =devm_kzalloc (&vdev->dev,sizeof (*vpmem), +GFP_KERNEL ); +if (!vpmem) { + err = -ENOMEM ; + goto out_err; + } + + vpmem->vdev = vdev; + err =init_vq (vpmem); +if (err) + goto out_err; + + virtio_cread(vpmem->vdev, struct virtio_pmem_config, + start, &vpmem->start); + virtio_cread(vpmem->vdev, struct virtio_pmem_config, + size, &vpmem->size); + + res.start = vpmem->start; + res.end = vpmem->start + vpmem->size-1 ; + vpmem->nd_desc.provider_name ="virtio-pmem" ; + vpmem->nd_desc.module =THIS_MODULE ; + + vpmem->nvdimm_bus = nvdimm_bus =nvdimm_bus_register (&vdev->dev, + &vpmem->nd_desc); +if (!nvdimm_bus) + goto out_vq; + +dev_set_drvdata (&vdev->dev, nvdimm_bus); +memset (&ndr_desc,0 ,sizeof (ndr_desc)); + + ndr_desc.res = &res; + ndr_desc.numa_node = nid; + ndr_desc.flush = virtio_pmem_flush; +set_bit (ND_REGION_PAGEMAP , &ndr_desc.flags); + nd_region =nvdimm_pmem_region_create (nvdimm_bus, &ndr_desc); + +if (!nd_region) + goto out_nd; + +virtio_device_ready (vdev); +return 0 ; +out_nd: + err = -ENXIO ; +nvdimm_bus_unregister (nvdimm_bus); +out_vq: + vdev->config->del_vqs (vdev); +out_err: +dev_err (&vdev->dev,"failed to register virtio pmem memory\n" ); +return err; +} + +static void virtio_pmem_remove (struct virtio_device *vdev) +{ +struct virtio_pmem *vpmem = vdev->priv; +struct nvdimm_bus *nvdimm_bus =dev_get_drvdata (&vdev->dev); + +nvdimm_bus_unregister (nvdimm_bus); + vdev->config->del_vqs (vdev); +kfree (vpmem); +} + +#ifdef CONFIG_PM_SLEEP +static int virtio_pmem_freeze (struct virtio_device *vdev) +{ +/* todo: handle freeze function */ +return -EPERM ; +} + +static int virtio_pmem_restore (struct virtio_device *vdev) +{ +/* todo: handle restore function */ +return -EPERM ; +} +#endif + + +static struct virtio_driver virtio_pmem_driver = { + .driver.name =KBUILD_MODNAME , + .driver.owner =THIS_MODULE , + .id_table = id_table, + .probe = virtio_pmem_probe, + .remove = virtio_pmem_remove, +#ifdef CONFIG_PM_SLEEP + .freeze = virtio_pmem_freeze, + .restore = virtio_pmem_restore, +#endif +}; + +module_virtio_driver (virtio_pmem_driver); +MODULE_DEVICE_TABLE (virtio, id_table); +MODULE_DESCRIPTION ("Virtio pmem driver" ); +MODULE_LICENSE ("GPL" );include/linux/virtio_pmem.h new file +44
-0@@ -0,0 +1,44 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* virtio_pmem.h: virtio pmem Driver +* +* Discovers persistent memory range information +* from host and provides a virtio based flushing +* interface. +*/ +#ifndef _LINUX_VIRTIO_PMEM_H +#define _LINUX_VIRTIO_PMEM_H + +#include <linux/virtio_ids.h> +#include <linux/virtio_config.h> +#include <uapi/linux/virtio_pmem.h> +#include <linux/libnvdimm.h> +#include <linux/spinlock.h> + +struct virtio_pmem_request { +/* Host return status corresponding to flush request */ +int ret; + +/* Wait queue to process deferred work after ack from host */ +wait_queue_head_t acked; +bool done; +}; + +struct virtio_pmem { +struct virtio_device *vdev; + +/* Virtio pmem request queue */ +struct virtqueue *req_vq; + +/* nvdimm bus registers virtio pmem device */ +struct nvdimm_bus *nvdimm_bus; +struct nvdimm_bus_descriptor nd_desc; + +/* Synchronize virtqueue data */ +spinlock_t pmem_lock; + +/* Memory region information */ +uint64_t start; +uint64_t size; +}; +#endif include/uapi/linux/virtio_ids.h +1
-0@@ -43,5 +43,6 @@#define VIRTIO_ID_INPUT 18/* virtio input */ #define VIRTIO_ID_VSOCK 19/* virtio vsock transport */ #define VIRTIO_ID_CRYPTO 20/* virtio crypto */ +#define VIRTIO_ID_PMEM 25/* virtio pmem */ #endif /* _LINUX_VIRTIO_IDS_H */ include/uapi/linux/virtio_pmem.h new file +40
-0@@ -0,0 +1,40 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* This header, excluding the #ifdef __KERNEL__ part, is BSD licensed so +* anyone can use the definitions to implement compatible drivers/servers: +* +* +* Redistribution and use in source and binary forms, with or without +* modification, are permitted provided that the following conditions +* are met: +* 1. Redistributions of source code must retain the above copyright +* notice, this list of conditions and the following disclaimer. +* 2. Redistributions in binary form must reproduce the above copyright +* notice, this list of conditions and the following disclaimer in the +* documentation and/or other materials provided with the distribution. +* 3. Neither the name of IBM nor the names of its contributors +* may be used to endorse or promote products derived from this software +* without specific prior written permission. +* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' +* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +* ARE DISCLAIMED. IN NO EVENT SHALL IBM OR CONTRIBUTORS BE LIABLE +* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +* SUCH DAMAGE. +* +* Copyright (C) Red Hat, Inc., 2018-2019 +* Copyright (C) Pankaj Gupta <[email protected]>, 2018 +*/ +#ifndef _UAPI_LINUX_VIRTIO_PMEM_H +#define _UAPI_LINUX_VIRTIO_PMEM_H + +struct virtio_pmem_config { +__le64 start; +__le64 size; +}; +#endif
Re: [Qemu-devel] [RFC v3 2/2] virtio-pmem: Add virtio pmem driver
Quoted 89 lines
Quoted 89 lines
This patch adds virtio-pmem driver for KVM guest.
Guest reads the persistent memory range information from Qemu over VIRTIO and registers it on
nvdimm_bus. It also creates and_regionobject with the persistent memory range information so that existing 'nvdimm/pmem' driver can reserve this into system memory map. This way 'virtio-pmem' driver uses existing functionality of pmem driver to register persistent memory compatible for DAX capable filesystems.This also provides function to perform guest flush over VIRTIO from 'pmem' driver when userspace performs flush on DAX memory range.
Signed-off-by Pankaj Gupta <[email protected]>--- drivers/virtio/Kconfig | 9 ++ drivers/virtio/Makefile | 1 + drivers/virtio/virtio_pmem.c | 190 +++++++++++++++++++++++++++++++++++++++ include/linux/virtio_pmem.h | 44 +++++++++ include/uapi/linux/virtio_ids.h | 1 + include/uapi/linux/virtio_pmem.h | 40 +++++++++ 6 files changed, 285 insertions(+) create mode 100644 drivers/virtio/virtio_pmem.c create mode 100644 include/linux/virtio_pmem.h create mode 100644 include/uapi/linux/virtio_pmem.hdrivers/virtio/Kconfig +9
-0@@ -42,6 +42,15 @@ config VIRTIO_PCI_LEGACY If unsure, say Y. +config VIRTIO_PMEM + tristate "Support for virtio pmem driver" + depends on VIRTIO + help + This driver provides support for virtio based flushing interface + for persistent memory range. + + If unsure, say M. + config VIRTIO_BALLOON tristate "Virtio balloon driver" depends on VIRTIOdrivers/virtio/Makefile +1
-0@@ -6,3 +6,4 @@ virtio_pci-y := virtio_pci_modern.o virtio_pci_common.o virtio_pci-$(CONFIG_VIRTIO_PCI_LEGACY) += virtio_pci_legacy.o obj-$(CONFIG_VIRTIO_BALLOON) += virtio_balloon.o obj-$(CONFIG_VIRTIO_INPUT) += virtio_input.o +obj-$(CONFIG_VIRTIO_PMEM) += virtio_pmem.odrivers/virtio/virtio_pmem.c new file +25
-0@@ -0,0 +1,190 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* virtio_pmem.c: Virtio pmem Driver +* +* Discovers persistent memory range information +* from host and provides a virtio based flushing +* interface. +*/ +#include <linux/virtio.h> +#include <linux/module.h> +#include <linux/virtio_pmem.h> + +static struct virtio_device_id id_table[] = { + {VIRTIO_ID_PMEM ,VIRTIO_DEV_ANY_ID }, + {0 }, +}; + +/* The interrupt handler */ +static void host_ack (struct virtqueue *vq) +{ +unsigned int len; +unsigned long flags; +struct virtio_pmem_request *req; +struct virtio_pmem *vpmem = vq->vdev->priv; +
Quoted 8 lines
drivers/virtio/virtio_pmem.c line 31
Quoted 6 lines
drivers/virtio/virtio_pmem.c new file +6
-0+spin_lock_irqsave (&vpmem->pmem_lock, flags); +while ((req =virtqueue_get_buf (vq, &len)) !=NULL ) { + req->done = true; +wake_up (&req->acked); + } +spin_unlock_irqrestore (&vpmem->pmem_lock, flags);Honest question: why do you need to disable interrupts here?
To avoid interrupt for VQ trying to take same spinlock already taken by process context and resulting in deadlock. Looks like interrupts are already disabled in function call, see [1]. But still to protect with any future work.
[1]
vp_interrupt
vp_vring_interrupt
vring_interrupt
Quoted 20 lines
Quoted 20 lines
drivers/virtio/virtio_pmem.c new file +19
-0+} +/* Initialize virt queue */ +static int init_vq (struct virtio_pmem *vpmem) +{ +struct virtqueue *vq; + +/* single vq */ + vpmem->req_vq = vq =virtio_find_single_vq (vpmem->vdev, + host_ack,"flush_queue" ); +if (IS_ERR (vq)) +return PTR_ERR (vq); +spin_lock_init (&vpmem->pmem_lock); + +return 0 ; +}; + +/* The request submission function */ +static int virtio_pmem_flush (struct device *dev) +{
Quoted 8 lines
drivers/virtio/virtio_pmem.c line 56
Quoted 6 lines
drivers/virtio/virtio_pmem.c new file +6
-0+int err; +unsigned long flags; +struct scatterlist *sgs[2 ], sg, ret; +struct virtio_device *vdev =dev_to_virtio (dev->parent->parent); +struct virtio_pmem *vpmem = vdev->priv; +struct virtio_pmem_request *req =kmalloc (sizeof (*req),GFP_KERNEL );Not checking
kmalloc()return.
Will add it.
Quoted 11 lines
drivers/virtio/virtio_pmem.c line 60
Quoted 5 lines
drivers/virtio/virtio_pmem.c new file +4
-0+ + req->done = false; +init_waitqueue_head (&req->acked); +spin_lock_irqsave (&vpmem->pmem_lock, flags);Why do you need
spin_lock_irqsave()? There are two points consider:1. Will
virtio_pmem_flush()ever be called with interrupts disabled? If yes, then it's broken since you should be usingGFP_ATOMICin thekmalloc()call and you can't callwait_event()
Yes, GFP_ATOMIC should be right thing.
Quoted 3 lines
2. If
virtio_pmem_flush()is never called with interrupts disabled, do you really need to disable interrupts? If yes, why?
Same reason as discussed above. Data is shared between interrupt handler and process context 'virtio-pmem_flush' function. To avoid a deadlock resulting between interrupt context and process context on same spinlock.
Quoted 7 lines
Another point to consider is whether or not
virtio_pmem_flush()can be called from atomic context.nvdimm_flush()itself is called from a few atomic sites, but I can't tell ifvirtio_pmem_flush()will ever be called from those sites. If it can be called atomic context, then item 1 applies here. If you're sure it can't, then you should probably callmight_sleep().
I think 'virtio_pmem_flush' can be called from atomic context.
Thanks,
Pankaj
Quoted 250 lines
Quoted 247 lines
drivers/virtio/virtio_pmem.c new file +130
-0+ +sg_init_one (&sg, req,sizeof (req)); + sgs[0 ] = &sg; +sg_init_one (&ret, &req->ret,sizeof (req->ret)); + sgs[1 ] = &ret; + err =virtqueue_add_sgs (vpmem->req_vq, sgs,1 ,1 , req,GFP_ATOMIC ); +if (err) { +dev_err (&vdev->dev,"failed to send command to virtio pmem device\n" ); +spin_unlock_irqrestore (&vpmem->pmem_lock, flags); +return -ENOSPC ; + } +virtqueue_kick (vpmem->req_vq); +spin_unlock_irqrestore (&vpmem->pmem_lock, flags); + +/* When host has read buffer, this completes via host_ack */ +wait_event (req->acked, req->done); + err = req->ret; +kfree (req); + +return err; +}; + +static int virtio_pmem_probe (struct virtio_device *vdev) +{ +int err =0 ; +struct resource res; +struct virtio_pmem *vpmem; +struct nvdimm_bus *nvdimm_bus; +struct nd_region_desc ndr_desc; +int nid =dev_to_node (&vdev->dev); +struct nd_region *nd_region; + +if (!vdev->config->get) { +dev_err (&vdev->dev,"%s failure: config disabled\n" , + __func__); +return -EINVAL ; + } + + vdev->priv = vpmem =devm_kzalloc (&vdev->dev,sizeof (*vpmem), +GFP_KERNEL ); +if (!vpmem) { + err = -ENOMEM ; + goto out_err; + } + + vpmem->vdev = vdev; + err =init_vq (vpmem); +if (err) + goto out_err; + + virtio_cread(vpmem->vdev, struct virtio_pmem_config, + start, &vpmem->start); + virtio_cread(vpmem->vdev, struct virtio_pmem_config, + size, &vpmem->size); + + res.start = vpmem->start; + res.end = vpmem->start + vpmem->size-1 ; + vpmem->nd_desc.provider_name ="virtio-pmem" ; + vpmem->nd_desc.module =THIS_MODULE ; + + vpmem->nvdimm_bus = nvdimm_bus =nvdimm_bus_register (&vdev->dev, + &vpmem->nd_desc); +if (!nvdimm_bus) + goto out_vq; + +dev_set_drvdata (&vdev->dev, nvdimm_bus); +memset (&ndr_desc,0 ,sizeof (ndr_desc)); + + ndr_desc.res = &res; + ndr_desc.numa_node = nid; + ndr_desc.flush = virtio_pmem_flush; +set_bit (ND_REGION_PAGEMAP , &ndr_desc.flags); + nd_region =nvdimm_pmem_region_create (nvdimm_bus, &ndr_desc); + +if (!nd_region) + goto out_nd; + +virtio_device_ready (vdev); +return 0 ; +out_nd: + err = -ENXIO ; +nvdimm_bus_unregister (nvdimm_bus); +out_vq: + vdev->config->del_vqs (vdev); +out_err: +dev_err (&vdev->dev,"failed to register virtio pmem memory\n" ); +return err; +} + +static void virtio_pmem_remove (struct virtio_device *vdev) +{ +struct virtio_pmem *vpmem = vdev->priv; +struct nvdimm_bus *nvdimm_bus =dev_get_drvdata (&vdev->dev); + +nvdimm_bus_unregister (nvdimm_bus); + vdev->config->del_vqs (vdev); +kfree (vpmem); +} + +#ifdef CONFIG_PM_SLEEP +static int virtio_pmem_freeze (struct virtio_device *vdev) +{ +/* todo: handle freeze function */ +return -EPERM ; +} + +static int virtio_pmem_restore (struct virtio_device *vdev) +{ +/* todo: handle restore function */ +return -EPERM ; +} +#endif + + +static struct virtio_driver virtio_pmem_driver = { + .driver.name =KBUILD_MODNAME , + .driver.owner =THIS_MODULE , + .id_table = id_table, + .probe = virtio_pmem_probe, + .remove = virtio_pmem_remove, +#ifdef CONFIG_PM_SLEEP + .freeze = virtio_pmem_freeze, + .restore = virtio_pmem_restore, +#endif +}; + +module_virtio_driver (virtio_pmem_driver); +MODULE_DEVICE_TABLE (virtio, id_table); +MODULE_DESCRIPTION ("Virtio pmem driver" ); +MODULE_LICENSE ("GPL" );include/linux/virtio_pmem.h new file +44
-0@@ -0,0 +1,44 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* virtio_pmem.h: virtio pmem Driver +* +* Discovers persistent memory range information +* from host and provides a virtio based flushing +* interface. +*/ +#ifndef _LINUX_VIRTIO_PMEM_H +#define _LINUX_VIRTIO_PMEM_H + +#include <linux/virtio_ids.h> +#include <linux/virtio_config.h> +#include <uapi/linux/virtio_pmem.h> +#include <linux/libnvdimm.h> +#include <linux/spinlock.h> + +struct virtio_pmem_request { +/* Host return status corresponding to flush request */ +int ret; + +/* Wait queue to process deferred work after ack from host */ +wait_queue_head_t acked; +bool done; +}; + +struct virtio_pmem { +struct virtio_device *vdev; + +/* Virtio pmem request queue */ +struct virtqueue *req_vq; + +/* nvdimm bus registers virtio pmem device */ +struct nvdimm_bus *nvdimm_bus; +struct nvdimm_bus_descriptor nd_desc; + +/* Synchronize virtqueue data */ +spinlock_t pmem_lock; + +/* Memory region information */ +uint64_t start; +uint64_t size; +}; +#endif include/uapi/linux/virtio_ids.h +1
-0@@ -43,5 +43,6 @@#define VIRTIO_ID_INPUT 18/* virtio input */ #define VIRTIO_ID_VSOCK 19/* virtio vsock transport */ #define VIRTIO_ID_CRYPTO 20/* virtio crypto */ +#define VIRTIO_ID_PMEM 25/* virtio pmem */ #endif /* _LINUX_VIRTIO_IDS_H */ include/uapi/linux/virtio_pmem.h new file +16
-0@@ -0,0 +1,40 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* This header, excluding the #ifdef __KERNEL__ part, is BSD licensed so +* anyone can use the definitions to implement compatible drivers/servers: +* +* +* Redistribution and use in source and binary forms, with or without +* modification, are permitted provided that the following conditions +* are met: +* 1. Redistributions of source code must retain the above copyright +* notice, this list of conditions and the following disclaimer. +* 2. Redistributions in binary form must reproduce the above copyright +* notice, this list of conditions and the following disclaimer in the +* documentation and/or other materials provided with the distribution. +* 3. Neither the name of IBM nor the names of its contributors +* may be used to endorse or promote products derived from this software
+ * without specific prior written permission.
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS''
+ * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED. IN NO EVENT SHALL IBM OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ *
+ * Copyright (C) Red Hat, Inc., 2018-2019
+ * Copyright (C) Pankaj Gupta <[email protected]>, 2018
+ */include/uapi/linux/virtio_pmem.h new file +8
-0+#ifndef _UAPI_LINUX_VIRTIO_PMEM_H +#define _UAPI_LINUX_VIRTIO_PMEM_H + +struct virtio_pmem_config { +__le64 start; +__le64 size; +}; +#endif
Re: [Qemu-devel] [RFC v3 2/2] virtio-pmem: Add virtio pmem driver
Quoted 96 lines · On Mon, 16 Jul 2018 07:46:30 -0400 (EDT) Pankaj Gupta…
Quoted 87 lines
Quoted 87 lines
This patch adds virtio-pmem driver for KVM guest.
Guest reads the persistent memory range information from Qemu over VIRTIO and registers it on
nvdimm_bus. It also creates and_regionobject with the persistent memory range information so that existing 'nvdimm/pmem' driver can reserve this into system memory map. This way 'virtio-pmem' driver uses existing functionality of pmem driver to register persistent memory compatible for DAX capable filesystems.This also provides function to perform guest flush over VIRTIO from 'pmem' driver when userspace performs flush on DAX memory range.
Signed-off-by Pankaj Gupta <[email protected]>--- drivers/virtio/Kconfig | 9 ++ drivers/virtio/Makefile | 1 + drivers/virtio/virtio_pmem.c | 190 +++++++++++++++++++++++++++++++++++++++ include/linux/virtio_pmem.h | 44 +++++++++ include/uapi/linux/virtio_ids.h | 1 + include/uapi/linux/virtio_pmem.h | 40 +++++++++ 6 files changed, 285 insertions(+) create mode 100644 drivers/virtio/virtio_pmem.c create mode 100644 include/linux/virtio_pmem.h create mode 100644 include/uapi/linux/virtio_pmem.hdrivers/virtio/Kconfig +9
-0@@ -42,6 +42,15 @@ config VIRTIO_PCI_LEGACY If unsure, say Y. +config VIRTIO_PMEM + tristate "Support for virtio pmem driver" + depends on VIRTIO + help + This driver provides support for virtio based flushing interface + for persistent memory range. + + If unsure, say M. + config VIRTIO_BALLOON tristate "Virtio balloon driver" depends on VIRTIOdrivers/virtio/Makefile +1
-0@@ -6,3 +6,4 @@ virtio_pci-y := virtio_pci_modern.o virtio_pci_common.o virtio_pci-$(CONFIG_VIRTIO_PCI_LEGACY) += virtio_pci_legacy.o obj-$(CONFIG_VIRTIO_BALLOON) += virtio_balloon.o obj-$(CONFIG_VIRTIO_INPUT) += virtio_input.o +obj-$(CONFIG_VIRTIO_PMEM) += virtio_pmem.odrivers/virtio/virtio_pmem.c new file +25
-0@@ -0,0 +1,190 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* virtio_pmem.c: Virtio pmem Driver +* +* Discovers persistent memory range information +* from host and provides a virtio based flushing +* interface. +*/ +#include <linux/virtio.h> +#include <linux/module.h> +#include <linux/virtio_pmem.h> + +static struct virtio_device_id id_table[] = { + {VIRTIO_ID_PMEM ,VIRTIO_DEV_ANY_ID }, + {0 }, +}; + +/* The interrupt handler */ +static void host_ack (struct virtqueue *vq) +{ +unsigned int len; +unsigned long flags; +struct virtio_pmem_request *req; +struct virtio_pmem *vpmem = vq->vdev->priv; +Quoted 8 lines
drivers/virtio/virtio_pmem.c line 31
Quoted 6 lines
drivers/virtio/virtio_pmem.c new file +6
-0+spin_lock_irqsave (&vpmem->pmem_lock, flags); +while ((req =virtqueue_get_buf (vq, &len)) !=NULL ) { + req->done = true; +wake_up (&req->acked); + } +spin_unlock_irqrestore (&vpmem->pmem_lock, flags);Honest question: why do you need to disable interrupts here?
Quoted 8 lines
To avoid interrupt for VQ trying to take same spinlock already taken by process context and resulting in deadlock. Looks like interrupts are already disabled in function call, see [1]. But still to protect with any future work.
[1]
vp_interrupt
vp_vring_interrupt
vring_interrupt
I think you're right, and I think I may have caused some confusion. See below.
Quoted 53 lines
Quoted 20 lines
Quoted 20 lines
drivers/virtio/virtio_pmem.c new file +19
-0+} +/* Initialize virt queue */ +static int init_vq (struct virtio_pmem *vpmem) +{ +struct virtqueue *vq; + +/* single vq */ + vpmem->req_vq = vq =virtio_find_single_vq (vpmem->vdev, + host_ack,"flush_queue" ); +if (IS_ERR (vq)) +return PTR_ERR (vq); +spin_lock_init (&vpmem->pmem_lock); + +return 0 ; +}; + +/* The request submission function */ +static int virtio_pmem_flush (struct device *dev) +{Quoted 8 lines
drivers/virtio/virtio_pmem.c line 56
Quoted 6 lines
drivers/virtio/virtio_pmem.c new file +6
-0+int err; +unsigned long flags; +struct scatterlist *sgs[2 ], sg, ret; +struct virtio_device *vdev =dev_to_virtio (dev->parent->parent); +struct virtio_pmem *vpmem = vdev->priv; +struct virtio_pmem_request *req =kmalloc (sizeof (*req),GFP_KERNEL );Not checking
kmalloc()return.Will add it.
Quoted 11 lines
drivers/virtio/virtio_pmem.c line 60
Quoted 5 lines
drivers/virtio/virtio_pmem.c new file +4
-0+ + req->done = false; +init_waitqueue_head (&req->acked); +spin_lock_irqsave (&vpmem->pmem_lock, flags);Why do you need
spin_lock_irqsave()? There are two points consider:1. Will
virtio_pmem_flush()ever be called with interrupts disabled? If yes, then it's broken since you should be usingGFP_ATOMICin thekmalloc()call and you can't callwait_event()Yes,
GFP_ATOMICshould be right thing.Quoted 3 lines
2. If
virtio_pmem_flush()is never called with interrupts disabled, do you really need to disable interrupts? If yes, why?Same reason as discussed above. Data is shared between interrupt handler and process context 'virtio-pmem_flush' function. To avoid a deadlock resulting between interrupt context and process context on same spinlock.
Quoted 1 line
Quoted 8 lines
Quoted 6 lines
Another point to consider is whether or not
virtio_pmem_flush()can be called from atomic context.nvdimm_flush()itself is called from a few atomic sites, but I can't tell ifvirtio_pmem_flush()will ever be called from those sites. If it can be called atomic context, then item 1 applies here. If you're sure it can't, then you should probably callmight_sleep().I think '
virtio_pmem_flush' can be called from atomic context.
If you're certain of this, then everything I said in my previous email should be correct (ie. GFP_ATOMIC in kmalloc() and the fact that you can't sleep).
Now, if for some reason virtio_pmem_flush() is not called from atomic context (say, because it's never called from the ACPI code), then my review was wrong and I think your code is correct, since you're disabling irqs to protect the virtqueue against the interrupt handler. In this case you can sleep outside the atomic context.
Quoted 255 lines
Thanks,
PankajQuoted 250 lines
Quoted 247 lines
drivers/virtio/virtio_pmem.c new file +130
-0+ +sg_init_one (&sg, req,sizeof (req)); + sgs[0 ] = &sg; +sg_init_one (&ret, &req->ret,sizeof (req->ret)); + sgs[1 ] = &ret; + err =virtqueue_add_sgs (vpmem->req_vq, sgs,1 ,1 , req,GFP_ATOMIC ); +if (err) { +dev_err (&vdev->dev,"failed to send command to virtio pmem device\n" ); +spin_unlock_irqrestore (&vpmem->pmem_lock, flags); +return -ENOSPC ; + } +virtqueue_kick (vpmem->req_vq); +spin_unlock_irqrestore (&vpmem->pmem_lock, flags); + +/* When host has read buffer, this completes via host_ack */ +wait_event (req->acked, req->done); + err = req->ret; +kfree (req); + +return err; +}; + +static int virtio_pmem_probe (struct virtio_device *vdev) +{ +int err =0 ; +struct resource res; +struct virtio_pmem *vpmem; +struct nvdimm_bus *nvdimm_bus; +struct nd_region_desc ndr_desc; +int nid =dev_to_node (&vdev->dev); +struct nd_region *nd_region; + +if (!vdev->config->get) { +dev_err (&vdev->dev,"%s failure: config disabled\n" , + __func__); +return -EINVAL ; + } + + vdev->priv = vpmem =devm_kzalloc (&vdev->dev,sizeof (*vpmem), +GFP_KERNEL ); +if (!vpmem) { + err = -ENOMEM ; + goto out_err; + } + + vpmem->vdev = vdev; + err =init_vq (vpmem); +if (err) + goto out_err; + + virtio_cread(vpmem->vdev, struct virtio_pmem_config, + start, &vpmem->start); + virtio_cread(vpmem->vdev, struct virtio_pmem_config, + size, &vpmem->size); + + res.start = vpmem->start; + res.end = vpmem->start + vpmem->size-1 ; + vpmem->nd_desc.provider_name ="virtio-pmem" ; + vpmem->nd_desc.module =THIS_MODULE ; + + vpmem->nvdimm_bus = nvdimm_bus =nvdimm_bus_register (&vdev->dev, + &vpmem->nd_desc); +if (!nvdimm_bus) + goto out_vq; + +dev_set_drvdata (&vdev->dev, nvdimm_bus); +memset (&ndr_desc,0 ,sizeof (ndr_desc)); + + ndr_desc.res = &res; + ndr_desc.numa_node = nid; + ndr_desc.flush = virtio_pmem_flush; +set_bit (ND_REGION_PAGEMAP , &ndr_desc.flags); + nd_region =nvdimm_pmem_region_create (nvdimm_bus, &ndr_desc); + +if (!nd_region) + goto out_nd; + +virtio_device_ready (vdev); +return 0 ; +out_nd: + err = -ENXIO ; +nvdimm_bus_unregister (nvdimm_bus); +out_vq: + vdev->config->del_vqs (vdev); +out_err: +dev_err (&vdev->dev,"failed to register virtio pmem memory\n" ); +return err; +} + +static void virtio_pmem_remove (struct virtio_device *vdev) +{ +struct virtio_pmem *vpmem = vdev->priv; +struct nvdimm_bus *nvdimm_bus =dev_get_drvdata (&vdev->dev); + +nvdimm_bus_unregister (nvdimm_bus); + vdev->config->del_vqs (vdev); +kfree (vpmem); +} + +#ifdef CONFIG_PM_SLEEP +static int virtio_pmem_freeze (struct virtio_device *vdev) +{ +/* todo: handle freeze function */ +return -EPERM ; +} + +static int virtio_pmem_restore (struct virtio_device *vdev) +{ +/* todo: handle restore function */ +return -EPERM ; +} +#endif + + +static struct virtio_driver virtio_pmem_driver = { + .driver.name =KBUILD_MODNAME , + .driver.owner =THIS_MODULE , + .id_table = id_table, + .probe = virtio_pmem_probe, + .remove = virtio_pmem_remove, +#ifdef CONFIG_PM_SLEEP + .freeze = virtio_pmem_freeze, + .restore = virtio_pmem_restore, +#endif +}; + +module_virtio_driver (virtio_pmem_driver); +MODULE_DEVICE_TABLE (virtio, id_table); +MODULE_DESCRIPTION ("Virtio pmem driver" ); +MODULE_LICENSE ("GPL" );include/linux/virtio_pmem.h new file +44
-0@@ -0,0 +1,44 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* virtio_pmem.h: virtio pmem Driver +* +* Discovers persistent memory range information +* from host and provides a virtio based flushing +* interface. +*/ +#ifndef _LINUX_VIRTIO_PMEM_H +#define _LINUX_VIRTIO_PMEM_H + +#include <linux/virtio_ids.h> +#include <linux/virtio_config.h> +#include <uapi/linux/virtio_pmem.h> +#include <linux/libnvdimm.h> +#include <linux/spinlock.h> + +struct virtio_pmem_request { +/* Host return status corresponding to flush request */ +int ret; + +/* Wait queue to process deferred work after ack from host */ +wait_queue_head_t acked; +bool done; +}; + +struct virtio_pmem { +struct virtio_device *vdev; + +/* Virtio pmem request queue */ +struct virtqueue *req_vq; + +/* nvdimm bus registers virtio pmem device */ +struct nvdimm_bus *nvdimm_bus; +struct nvdimm_bus_descriptor nd_desc; + +/* Synchronize virtqueue data */ +spinlock_t pmem_lock; + +/* Memory region information */ +uint64_t start; +uint64_t size; +}; +#endif include/uapi/linux/virtio_ids.h +1
-0@@ -43,5 +43,6 @@#define VIRTIO_ID_INPUT 18/* virtio input */ #define VIRTIO_ID_VSOCK 19/* virtio vsock transport */ #define VIRTIO_ID_CRYPTO 20/* virtio crypto */ +#define VIRTIO_ID_PMEM 25/* virtio pmem */ #endif /* _LINUX_VIRTIO_IDS_H */ include/uapi/linux/virtio_pmem.h new file +16
-0@@ -0,0 +1,40 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* This header, excluding the #ifdef __KERNEL__ part, is BSD licensed so +* anyone can use the definitions to implement compatible drivers/servers: +* +* +* Redistribution and use in source and binary forms, with or without +* modification, are permitted provided that the following conditions +* are met: +* 1. Redistributions of source code must retain the above copyright +* notice, this list of conditions and the following disclaimer. +* 2. Redistributions in binary form must reproduce the above copyright +* notice, this list of conditions and the following disclaimer in the +* documentation and/or other materials provided with the distribution. +* 3. Neither the name of IBM nor the names of its contributors +* may be used to endorse or promote products derived from this software
+ * without specific prior written permission.
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS''
+ * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED. IN NO EVENT SHALL IBM OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ *
+ * Copyright (C) Red Hat, Inc., 2018-2019
+ * Copyright (C) Pankaj Gupta <[email protected]>, 2018
+ */include/uapi/linux/virtio_pmem.h new file +8
-0+#ifndef _UAPI_LINUX_VIRTIO_PMEM_H +#define _UAPI_LINUX_VIRTIO_PMEM_H + +struct virtio_pmem_config { +__le64 start; +__le64 size; +}; +#endif
Re: [Qemu-devel] [RFC v3 2/2] virtio-pmem: Add virtio pmem driver
Quoted 174 lines
Quoted 105 lines
Quoted 90 lines
Quoted 90 lines
This patch adds virtio-pmem driver for KVM guest.
Guest reads the persistent memory range information from Qemu over VIRTIO and registers it on
nvdimm_bus. It also creates and_regionobject with the persistent memory range information so that existing 'nvdimm/pmem' driver can reserve this into system memory map. This way 'virtio-pmem' driver uses existing functionality of pmem driver to register persistent memory compatible for DAX capable filesystems.This also provides function to perform guest flush over VIRTIO from 'pmem' driver when userspace performs flush on DAX memory range.
Signed-off-by Pankaj Gupta <[email protected]>--- drivers/virtio/Kconfig | 9 ++ drivers/virtio/Makefile | 1 + drivers/virtio/virtio_pmem.c | 190 +++++++++++++++++++++++++++++++++++++++ include/linux/virtio_pmem.h | 44 +++++++++ include/uapi/linux/virtio_ids.h | 1 + include/uapi/linux/virtio_pmem.h | 40 +++++++++ 6 files changed, 285 insertions(+) create mode 100644 drivers/virtio/virtio_pmem.c create mode 100644 include/linux/virtio_pmem.h create mode 100644 include/uapi/linux/virtio_pmem.hdrivers/virtio/Kconfig +9
-0@@ -42,6 +42,15 @@ config VIRTIO_PCI_LEGACY If unsure, say Y. +config VIRTIO_PMEM + tristate "Support for virtio pmem driver" + depends on VIRTIO + help + This driver provides support for virtio based flushing interface + for persistent memory range. + + If unsure, say M. + config VIRTIO_BALLOON tristate "Virtio balloon driver" depends on VIRTIOdrivers/virtio/Makefile +1
-0@@ -6,3 +6,4 @@ virtio_pci-y := virtio_pci_modern.o virtio_pci_common.o virtio_pci-$(CONFIG_VIRTIO_PCI_LEGACY) += virtio_pci_legacy.o obj-$(CONFIG_VIRTIO_BALLOON) += virtio_balloon.o obj-$(CONFIG_VIRTIO_INPUT) += virtio_input.o +obj-$(CONFIG_VIRTIO_PMEM) += virtio_pmem.odrivers/virtio/virtio_pmem.c new file +25
-0@@ -0,0 +1,190 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* virtio_pmem.c: Virtio pmem Driver +* +* Discovers persistent memory range information +* from host and provides a virtio based flushing +* interface. +*/ +#include <linux/virtio.h> +#include <linux/module.h> +#include <linux/virtio_pmem.h> + +static struct virtio_device_id id_table[] = { + {VIRTIO_ID_PMEM ,VIRTIO_DEV_ANY_ID }, + {0 }, +}; + +/* The interrupt handler */ +static void host_ack (struct virtqueue *vq) +{ +unsigned int len; +unsigned long flags; +struct virtio_pmem_request *req; +struct virtio_pmem *vpmem = vq->vdev->priv; +Quoted 8 lines
drivers/virtio/virtio_pmem.c line 31
Quoted 6 lines
drivers/virtio/virtio_pmem.c new file +6
-0+spin_lock_irqsave (&vpmem->pmem_lock, flags); +while ((req =virtqueue_get_buf (vq, &len)) !=NULL ) { + req->done = true; +wake_up (&req->acked); + } +spin_unlock_irqrestore (&vpmem->pmem_lock, flags);Honest question: why do you need to disable interrupts here?
To avoid interrupt for VQ trying to take same spinlock already taken by process
context and resulting in deadlock. Looks like interrupts are already disabled in
function call, see [1]. But still to protect with any future work.Quoted 4 lines
[1]
vp_interrupt
vp_vring_interrupt
vring_interruptI think you're right, and I think I may have caused some confusion. See below.
Quoted 61 lines
Quoted 20 lines
Quoted 20 lines
drivers/virtio/virtio_pmem.c new file +19
-0+} +/* Initialize virt queue */ +static int init_vq (struct virtio_pmem *vpmem) +{ +struct virtqueue *vq; + +/* single vq */ + vpmem->req_vq = vq =virtio_find_single_vq (vpmem->vdev, + host_ack,"flush_queue" ); +if (IS_ERR (vq)) +return PTR_ERR (vq); +spin_lock_init (&vpmem->pmem_lock); + +return 0 ; +}; + +/* The request submission function */ +static int virtio_pmem_flush (struct device *dev) +{Quoted 8 lines
drivers/virtio/virtio_pmem.c line 56
Quoted 6 lines
drivers/virtio/virtio_pmem.c new file +6
-0+int err; +unsigned long flags; +struct scatterlist *sgs[2 ], sg, ret; +struct virtio_device *vdev =dev_to_virtio (dev->parent->parent); +struct virtio_pmem *vpmem = vdev->priv; +struct virtio_pmem_request *req =kmalloc (sizeof (*req),GFP_KERNEL );Not checking
kmalloc()return.Will add it.
Quoted 11 lines
drivers/virtio/virtio_pmem.c line 60
Quoted 5 lines
drivers/virtio/virtio_pmem.c new file +4
-0+ + req->done = false; +init_waitqueue_head (&req->acked); +spin_lock_irqsave (&vpmem->pmem_lock, flags);Why do you need
spin_lock_irqsave()? There are two points consider:1. Will
virtio_pmem_flush()ever be called with interrupts disabled? If yes, then it's broken since you should be usingGFP_ATOMICin thekmalloc()call and you can't callwait_event()Yes,
GFP_ATOMICshould be right thing.Quoted 3 lines
2. If
virtio_pmem_flush()is never called with interrupts disabled, do you really need to disable interrupts? If yes, why?Same reason as discussed above. Data is shared between interrupt handler and process context 'virtio-pmem_flush' function. To avoid a deadlock resulting
between interrupt context and process context on same spinlock.Quoted 7 lines
Another point to consider is whether or not
virtio_pmem_flush()can be called from atomic context.nvdimm_flush()itself is called from a few atomic sites, but I can't tell ifvirtio_pmem_flush()will ever be called from those sites. If it can be called atomic context, then item 1 applies here. If you're sure it can't, then you should probably callmight_sleep().
Quoted 5 lines
Quoted 1 line
I think '
virtio_pmem_flush' can be called from atomic context.If you're certain of this, then everything I said in my previous email should be correct (ie.
GFP_ATOMICinkmalloc()and the fact that you can't sleep).
A correction:
AFAICS for virtio_pmem there is no atomic path so this can sleep. wait_event is doing same thing outside spinlock.
Quoted 6 lines
Now, if for some reason
virtio_pmem_flush()is not called from atomic context (say, because it's never called from the ACPI code), then my review was wrong and I think your code is correct, since you're disabling irqs to protect the virtqueue against the interrupt handler. In this case you can sleep outside the atomic context.
yes, we are sleeping outside the spinlock.
Thanks,
Pankaj
Quoted 270 lines
Quoted 267 lines
Thanks,
PankajQuoted 261 lines
Quoted 258 lines
drivers/virtio/virtio_pmem.c new file +8
-0+ +sg_init_one (&sg, req,sizeof (req)); + sgs[0 ] = &sg; +sg_init_one (&ret, &req->ret,sizeof (req->ret)); + sgs[1 ] = &ret; + err =virtqueue_add_sgs (vpmem->req_vq, sgs,1 ,1 , req,GFP_ATOMIC ); +if (err) { + dev_err(&vdev->dev, "failed to send command to virtio pmemdevice\n");
drivers/virtio/virtio_pmem.c new file +122
-0+spin_unlock_irqrestore (&vpmem->pmem_lock, flags); +return -ENOSPC ; + } +virtqueue_kick (vpmem->req_vq); +spin_unlock_irqrestore (&vpmem->pmem_lock, flags); + +/* When host has read buffer, this completes via host_ack */ +wait_event (req->acked, req->done); + err = req->ret; +kfree (req); + +return err; +}; + +static int virtio_pmem_probe (struct virtio_device *vdev) +{ +int err =0 ; +struct resource res; +struct virtio_pmem *vpmem; +struct nvdimm_bus *nvdimm_bus; +struct nd_region_desc ndr_desc; +int nid =dev_to_node (&vdev->dev); +struct nd_region *nd_region; + +if (!vdev->config->get) { +dev_err (&vdev->dev,"%s failure: config disabled\n" , + __func__); +return -EINVAL ; + } + + vdev->priv = vpmem =devm_kzalloc (&vdev->dev,sizeof (*vpmem), +GFP_KERNEL ); +if (!vpmem) { + err = -ENOMEM ; + goto out_err; + } + + vpmem->vdev = vdev; + err =init_vq (vpmem); +if (err) + goto out_err; + + virtio_cread(vpmem->vdev, struct virtio_pmem_config, + start, &vpmem->start); + virtio_cread(vpmem->vdev, struct virtio_pmem_config, + size, &vpmem->size); + + res.start = vpmem->start; + res.end = vpmem->start + vpmem->size-1 ; + vpmem->nd_desc.provider_name ="virtio-pmem" ; + vpmem->nd_desc.module =THIS_MODULE ; + + vpmem->nvdimm_bus = nvdimm_bus =nvdimm_bus_register (&vdev->dev, + &vpmem->nd_desc); +if (!nvdimm_bus) + goto out_vq; + +dev_set_drvdata (&vdev->dev, nvdimm_bus); +memset (&ndr_desc,0 ,sizeof (ndr_desc)); + + ndr_desc.res = &res; + ndr_desc.numa_node = nid; + ndr_desc.flush = virtio_pmem_flush; +set_bit (ND_REGION_PAGEMAP , &ndr_desc.flags); + nd_region =nvdimm_pmem_region_create (nvdimm_bus, &ndr_desc); + +if (!nd_region) + goto out_nd; + +virtio_device_ready (vdev); +return 0 ; +out_nd: + err = -ENXIO ; +nvdimm_bus_unregister (nvdimm_bus); +out_vq: + vdev->config->del_vqs (vdev); +out_err: +dev_err (&vdev->dev,"failed to register virtio pmem memory\n" ); +return err; +} + +static void virtio_pmem_remove (struct virtio_device *vdev) +{ +struct virtio_pmem *vpmem = vdev->priv; +struct nvdimm_bus *nvdimm_bus =dev_get_drvdata (&vdev->dev); + +nvdimm_bus_unregister (nvdimm_bus); + vdev->config->del_vqs (vdev); +kfree (vpmem); +} + +#ifdef CONFIG_PM_SLEEP +static int virtio_pmem_freeze (struct virtio_device *vdev) +{ +/* todo: handle freeze function */ +return -EPERM ; +} + +static int virtio_pmem_restore (struct virtio_device *vdev) +{ +/* todo: handle restore function */ +return -EPERM ; +} +#endif + + +static struct virtio_driver virtio_pmem_driver = { + .driver.name =KBUILD_MODNAME , + .driver.owner =THIS_MODULE , + .id_table = id_table, + .probe = virtio_pmem_probe, + .remove = virtio_pmem_remove, +#ifdef CONFIG_PM_SLEEP + .freeze = virtio_pmem_freeze, + .restore = virtio_pmem_restore, +#endif +}; + +module_virtio_driver (virtio_pmem_driver); +MODULE_DEVICE_TABLE (virtio, id_table); +MODULE_DESCRIPTION ("Virtio pmem driver" ); +MODULE_LICENSE ("GPL" );include/linux/virtio_pmem.h new file +44
-0@@ -0,0 +1,44 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* virtio_pmem.h: virtio pmem Driver +* +* Discovers persistent memory range information +* from host and provides a virtio based flushing +* interface. +*/ +#ifndef _LINUX_VIRTIO_PMEM_H +#define _LINUX_VIRTIO_PMEM_H + +#include <linux/virtio_ids.h> +#include <linux/virtio_config.h> +#include <uapi/linux/virtio_pmem.h> +#include <linux/libnvdimm.h> +#include <linux/spinlock.h> + +struct virtio_pmem_request { +/* Host return status corresponding to flush request */ +int ret; + +/* Wait queue to process deferred work after ack from host */ +wait_queue_head_t acked; +bool done; +}; + +struct virtio_pmem { +struct virtio_device *vdev; + +/* Virtio pmem request queue */ +struct virtqueue *req_vq; + +/* nvdimm bus registers virtio pmem device */ +struct nvdimm_bus *nvdimm_bus; +struct nvdimm_bus_descriptor nd_desc; + +/* Synchronize virtqueue data */ +spinlock_t pmem_lock; + +/* Memory region information */ +uint64_t start; +uint64_t size; +}; +#endif include/uapi/linux/virtio_ids.h +1
-0@@ -43,5 +43,6 @@#define VIRTIO_ID_INPUT 18/* virtio input */ #define VIRTIO_ID_VSOCK 19/* virtio vsock transport */ #define VIRTIO_ID_CRYPTO 20/* virtio crypto */ +#define VIRTIO_ID_PMEM 25/* virtio pmem */ #endif /* _LINUX_VIRTIO_IDS_H */ include/uapi/linux/virtio_pmem.h new file +3
-0@@ -0,0 +1,40 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* This header, excluding the #ifdef __KERNEL__ part, is BSD licensed so
+ * anyone can use the definitions to implement compatibledrivers/servers:
+ *
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of source code must retain the above copyright
+ * notice, this list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above
copyright
+ * notice, this list of conditions and the following disclaimer in
the
+ * documentation and/or other materials provided with the
distribution.
+ * 3. Neither the name of IBM nor the names of its contributors
+ * may be used to endorse or promote products derived from this
software
+ * without specific prior written permission.
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS''
+ * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED. IN NO EVENT SHALL IBM OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY
+ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ *
+ * Copyright (C) Red Hat, Inc., 2018-2019
+ * Copyright (C) Pankaj Gupta <[email protected]>, 2018
+ */include/uapi/linux/virtio_pmem.h new file +8
-0+#ifndef _UAPI_LINUX_VIRTIO_PMEM_H +#define _UAPI_LINUX_VIRTIO_PMEM_H + +struct virtio_pmem_config { +__le64 start; +__le64 size; +}; +#endif
Re: [RFC v3 2/2] virtio-pmem: Add virtio pmem driver
In reply to Pankaj GuptaQuoted 5 lines · Pankaj Gupta
+ /* The request submission function */
drivers/virtio/virtio_pmem.c new file +4
-0+static int virtio_pmem_flush (struct device *dev) +{ +int err; +unsigned long flags;
drivers/virtio/virtio_pmem.c line 62
Quoted 10 lines
drivers/virtio/virtio_pmem.c new file +10
-0+struct scatterlist *sgs[2 ], sg, ret; +struct virtio_device *vdev =dev_to_virtio (dev->parent->parent); +struct virtio_pmem *vpmem = vdev->priv; +struct virtio_pmem_request *req =kmalloc (sizeof (*req),GFP_KERNEL ); + + req->done = false; +init_waitqueue_head (&req->acked); +spin_lock_irqsave (&vpmem->pmem_lock, flags); + +sg_init_one (&sg, req,sizeof (req));
What are you trying to do here?
sizeof(req) == sizeof(struct virtio_pmem_request *) == sizeof(void *)
Did you mean sizeof(*req)?
But why map struct virtio_pmem_request to the device? struct virtio_pmem_request is the driver-internal request state and is not part of the hardware interface.
drivers/virtio/virtio_pmem.c line 68
Quoted 6 lines
drivers/virtio/virtio_pmem.c new file +6
-0+ sgs[0 ] = &sg; +sg_init_one (&ret, &req->ret,sizeof (req->ret)); + sgs[1 ] = &ret; + err =virtqueue_add_sgs (vpmem->req_vq, sgs,1 ,1 , req,GFP_ATOMIC ); +if (err) { +dev_err (&vdev->dev,"failed to send command to virtio pmem device\n" );
This can happen if the virtqueue is full. Printing a message and failing the flush isn't appropriate. This thread needs to wait until virtqueue space becomes available.
Review
Quoted 2 lines
(quoted diff) +2
-0+ spin_unlock_irqrestore(&vpmem->pmem_lock, flags); + return -ENOSPC;
req is leaked.
drivers/virtio/virtio_pmem.c line 138
Quoted 1 line
drivers/virtio/virtio_pmem.c new file +1
-0+virtio_device_ready (vdev);
This call isn't needed. Driver use it when they wish to submit buffers on virtqueues before ->probe() returns.
include/linux/virtio_pmem.h
Quoted 5 lines
include/linux/virtio_pmem.h new file +0
-0
include/ is for declarations (e.g. kernel APIs) needed by other compilation units. The contents of this header are internal to the virtio_pmem driver implementation and can therefore be in virtio_pmem.c. include/linux/virtio_pmem.h isn't necessary since nothing besides virtio_pmem.c will need to include it.
Re: [RFC v3 2/2] virtio-pmem: Add virtio pmem driver
Hi Stefan,
Quoted 18 lines
Quoted 5 lines
+ /* The request submission function */
drivers/virtio/virtio_pmem.c new file +4
-0+static int virtio_pmem_flush (struct device *dev) +{ +int err; +unsigned long flags;drivers/virtio/virtio_pmem.c line 62
Quoted 10 lines
drivers/virtio/virtio_pmem.c new file +10
-0+struct scatterlist *sgs[2 ], sg, ret; +struct virtio_device *vdev =dev_to_virtio (dev->parent->parent); +struct virtio_pmem *vpmem = vdev->priv; +struct virtio_pmem_request *req =kmalloc (sizeof (*req),GFP_KERNEL ); + + req->done = false; +init_waitqueue_head (&req->acked); +spin_lock_irqsave (&vpmem->pmem_lock, flags); + +sg_init_one (&sg, req,sizeof (req));What are you trying to do here?
Quoted 3 lines
sizeof(req) ==
sizeof(struct virtio_pmem_request *)==sizeof(void *)Did you mean
sizeof(*req)?
yes, I meant: sizeof(struct virtio_pmem_request)
Thanks for catching this.
Quoted 4 lines
But why map struct
virtio_pmem_requestto the device? structvirtio_pmem_requestis the driver-internal request state and is not part of the hardware interface.
o.k. I will separate out request from 'virtio_pmem_request' struct and use that.
Quoted 11 lines
drivers/virtio/virtio_pmem.c line 68
Quoted 7 lines
drivers/virtio/virtio_pmem.c new file +6
-0+ sgs[0 ] = &sg; +sg_init_one (&ret, &req->ret,sizeof (req->ret)); + sgs[1 ] = &ret; + err =virtqueue_add_sgs (vpmem->req_vq, sgs,1 ,1 , req,GFP_ATOMIC ); +if (err) { +dev_err (&vdev->dev,"failed to send command to virtio pmem device\n" );This can happen if the virtqueue is full. Printing a message and failing the flush isn't appropriate. This thread needs to wait until virtqueue space becomes available.
o.k. I will implement this.
Quoted 5 lines
Review
Quoted 3 lines
(quoted diff) +2
-0+ spin_unlock_irqrestore(&vpmem->pmem_lock, flags); + return -ENOSPC;req is leaked.
will free req.
Quoted 5 lines
drivers/virtio/virtio_pmem.c line 138
Quoted 2 lines
drivers/virtio/virtio_pmem.c new file +1
-0+virtio_device_ready (vdev);This call isn't needed. Driver use it when they wish to submit buffers on virtqueues before ->probe() returns.
o.k. I will remove it.
Quoted 12 lines
include/linux/virtio_pmem.h
Quoted 6 lines
include/linux/virtio_pmem.h new file +0
-0
include/is for declarations (e.g. kernel APIs) needed by other compilation units. The contents of this header are internal to thevirtio_pmemdriver implementation and can therefore be invirtio_pmem.c.include/linux/virtio_pmem.hisn't necessary since nothing besidesvirtio_pmem.cwill need to include it.
Agree. Will move declarations from virtio_pmem.h to virtio_pmem.c
Thanks,
Pankaj
RFC v3 1/1 qemu: Add virtio pmem device
In reply to Pankaj GuptaThis patch adds virtio-pmem Qemu device.
This device presents memory address range information to guest which is backed by file backend type. It acts like persistent memory device for KVM guest. Guest can perform read and persistent write operations on this memory range with the help of DAX capable filesystem.
Persistent guest writes are assured with the help of virtio based flushing interface. When guest userspace space performs fsync on file fd on pmem device, a flush command is send to Qemu over VIRTIO and host side flush/sync is done on backing image file.
Changes from RFC v2:
- Use aio_worker() to avoid Qemu from hanging with blocking fsync call - Stefan
- Use virtio_st*_p() for endianess - Stefan
- Correct indentation in qapi/misc.json - Eric
--- hw/virtio/Makefile.objs | 3 + hw/virtio/virtio-pci.c | 44 +++++ hw/virtio/virtio-pci.h | 14 ++ hw/virtio/virtio-pmem.c | 241 ++++++++++++++++++++++++++++ include/hw/pci/pci.h | 1 + include/hw/virtio/virtio-pmem.h | 42 +++++ include/standard-headers/linux/virtio_ids.h | 1 + qapi/misc.json | 26 ++- 8 files changed, 371 insertions(+), 1 deletion(-) create mode 100644 hw/virtio/virtio-pmem.c create mode 100644 include/hw/virtio/virtio-pmem.h
hw/virtio/Makefile.objs +3 -0
@@ -10,6 +10,9 @@ obj-$(CONFIG_VIRTIO_CRYPTO) += virtio-crypto.o obj-$(call land,$(CONFIG_VIRTIO_CRYPTO),$(CONFIG_VIRTIO_PCI)) += virtio-crypto-pci.o obj-$(CONFIG_LINUX) += vhost.o vhost-backend.o vhost-user.o +ifeq ($(CONFIG_MEM_HOTPLUG),y) +obj-$(CONFIG_LINUX) += virtio-pmem.o +endif obj-$(CONFIG_VHOST_VSOCK) += vhost-vsock.o endif
hw/virtio/virtio-pci.c +44 -0
56 lines not on this page · raw message
hw/virtio/virtio-pci.h +14 -0
@@ -19,6 +19,7 @@#include "hw/virtio/virtio-blk.h" #include "hw/virtio/virtio-net.h" #include "hw/virtio/virtio-rng.h" +#include "hw/virtio/virtio-pmem.h" #include "hw/virtio/virtio-serial.h" #include "hw/virtio/virtio-scsi.h" #include "hw/virtio/virtio-balloon.h"
@@ -57,6 +58,7 @@ typedef struct VirtIOInputHostPCI VirtIOInputHostPCI;typedef struct VirtIOGPUPCI VirtIOGPUPCI ;typedef struct VHostVSockPCI VHostVSockPCI ;typedef struct VirtIOCryptoPCI VirtIOCryptoPCI ; +typedef struct VirtIOPMEMPCI VirtIOPMEMPCI ;/* virtio-pci-bus */
@@ -274,6 +276,18 @@ struct VirtIOBlkPCI {VirtIOBlock vdev; }; +/* +* virtio-pmem-pci: This extends VirtioPCIProxy. +*/ +#define TYPE_VIRTIO_PMEM_PCI "virtio-pmem-pci" +#define VIRTIO_PMEM_PCI (obj) \ + OBJECT_CHECK(VirtIOPMEMPCI, (obj), TYPE_VIRTIO_PMEM_PCI) + +struct VirtIOPMEMPCI { +VirtIOPCIProxy parent_obj; +VirtIOPMEM vdev; +}; +/* * virtio-balloon-pci: This extends VirtioPCIProxy. */
hw/virtio/virtio-pmem.c new file +241 -0
241 lines not on this page · raw message
include/hw/pci/pci.h +1 -0
@@ -85,6 +85,7 @@ extern bool pci_available;#define PCI_DEVICE_ID_VIRTIO_RNG 0x1005#define PCI_DEVICE_ID_VIRTIO_9P 0x1009#define PCI_DEVICE_ID_VIRTIO_VSOCK 0x1012 +#define PCI_DEVICE_ID_VIRTIO_PMEM 0x1013#define PCI_VENDOR_ID_REDHAT 0x1b36#define PCI_DEVICE_ID_REDHAT_BRIDGE 0x0001
include/hw/virtio/virtio-pmem.h new file +42 -0
42 lines not on this page · raw message
include/standard-headers/linux/virtio_ids.h +1 -0
@@ -43,5 +43,6 @@#define VIRTIO_ID_INPUT 18/* virtio input */ #define VIRTIO_ID_VSOCK 19/* virtio vsock transport */ #define VIRTIO_ID_CRYPTO 20/* virtio crypto */ +#define VIRTIO_ID_PMEM 25/* virtio pmem */ #endif /* _LINUX_VIRTIO_IDS_H */
qapi/misc.json +25 -1
@@ -2907,6 +2907,29 @@ } } +## +# @VirtioPMemDeviceInfo: +# +# VirtioPMem state information +# +# @id: device's ID +# +# @start: physical address, where device is mapped +# +# @size: size of memory that the device provides +# +# @memdev: memory backend linked with device +# +# Since: 2.13 +## +{ 'struct': 'VirtioPMemDeviceInfo', + 'data': { '*id': 'str', + 'start': 'size', + 'size': 'size', + 'memdev': 'str' + } +} + ## # @MemoryDeviceInfo: #
@@ -2916,7 +2939,8 @@ ## { 'union': 'MemoryDeviceInfo', 'data': { 'dimm': 'PCDIMMDeviceInfo', - 'nvdimm': 'PCDIMMDeviceInfo' + 'nvdimm': 'PCDIMMDeviceInfo', + 'virtio-pmem': 'VirtioPMemDeviceInfo' } }
Signature · 1 line
2.14.3
Re: [RFC v3] qemu: Add virtio pmem device
Quoted 187 lines · On Fri, 13 Jul 2018 13:22:32 +0530 Pankaj Gupta…
This patch adds virtio-pmem Qemu device.
This device presents memory address range information to guest which is backed by file backend type. It acts like persistent memory device for KVM guest. Guest can perform read and persistent write operations on this memory range with the help of DAX capable filesystem.
Persistent guest writes are assured with the help of virtio based flushing interface. When guest userspace space performs fsync on file fd on pmem device, a flush command is send to Qemu over VIRTIO and host side flush/sync is done on backing image file.
Changes from RFC v2:
- Useaio_worker()to avoid Qemu from hanging with blocking fsync call - Stefan
- Use virtio_st*_p() for endianess - Stefan
- Correct indentation inqapi/misc.json- EricSigned-off-by Pankaj Gupta <[email protected]>--- hw/virtio/Makefile.objs | 3 + hw/virtio/virtio-pci.c | 44 +++++ hw/virtio/virtio-pci.h | 14 ++ hw/virtio/virtio-pmem.c | 241 ++++++++++++++++++++++++++++ include/hw/pci/pci.h | 1 + include/hw/virtio/virtio-pmem.h | 42 +++++ include/standard-headers/linux/virtio_ids.h | 1 + qapi/misc.json | 26 ++- 8 files changed, 371 insertions(+), 1 deletion(-) create mode 100644 hw/virtio/virtio-pmem.c create mode 100644 include/hw/virtio/virtio-pmem.hhw/virtio/Makefile.objs +3
-0@@ -10,6 +10,9 @@ obj-$(CONFIG_VIRTIO_CRYPTO) += virtio-crypto.o obj-$(call land,$(CONFIG_VIRTIO_CRYPTO),$(CONFIG_VIRTIO_PCI)) += virtio-crypto-pci.o obj-$(CONFIG_LINUX) += vhost.o vhost-backend.o vhost-user.o +ifeq ($(CONFIG_MEM_HOTPLUG),y) +obj-$(CONFIG_LINUX) += virtio-pmem.o +endif obj-$(CONFIG_VHOST_VSOCK) += vhost-vsock.o endifhw/virtio/virtio-pci.c +44
-0@@ -2521,6 +2521,49 @@ static const TypeInfo virtio_rng_pci_info = { .class_init = virtio_rng_pci_class_init, }; +/* virtio-pmem-pci */ + +static void virtio_pmem_pci_realize (VirtIOPCIProxy *vpci_dev,Error **errp) +{ +VirtIOPMEMPCI *vpmem =VIRTIO_PMEM_PCI (vpci_dev); +DeviceState *vdev =DEVICE (&vpmem->vdev); + +qdev_set_parent_bus (vdev,BUS (&vpci_dev->bus)); +object_property_set_bool (OBJECT (vdev), true,"realized" , errp); +} + +static void virtio_pmem_pci_class_init (ObjectClass *klass,void *data) +{ +DeviceClass *dc =DEVICE_CLASS (klass); +VirtioPCIClass *k =VIRTIO_PCI_CLASS (klass); +PCIDeviceClass *pcidev_k =PCI_DEVICE_CLASS (klass); + k->realize = virtio_pmem_pci_realize; +set_bit (DEVICE_CATEGORY_MISC , dc->categories); + pcidev_k->vendor_id =PCI_VENDOR_ID_REDHAT_QUMRANET ; + pcidev_k->device_id =PCI_DEVICE_ID_VIRTIO_PMEM ; + pcidev_k->revision =VIRTIO_PCI_ABI_VERSION ; + pcidev_k->class_id =PCI_CLASS_OTHERS ; +} + +static void virtio_pmem_pci_instance_init (Object *obj) +{ +VirtIOPMEMPCI *dev =VIRTIO_PMEM_PCI (obj); + +virtio_instance_init_common (obj, &dev->vdev,sizeof (dev->vdev), +TYPE_VIRTIO_PMEM ); +object_property_add_alias (obj,"memdev" ,OBJECT (&dev->vdev),"memdev" , + &error_abort); +} + +static const TypeInfo virtio_pmem_pci_info = { + .name =TYPE_VIRTIO_PMEM_PCI , + .parent =TYPE_VIRTIO_PCI , + .instance_size =sizeof (VirtIOPMEMPCI), + .instance_init = virtio_pmem_pci_instance_init, + .class_init = virtio_pmem_pci_class_init, +}; + +/* virtio-input-pci */ static Property virtio_input_pci_properties[] = {@@ -2714,6 +2757,7 @@ static void virtio_pci_register_types(void)type_register_static (&virtio_balloon_pci_info);type_register_static (&virtio_serial_pci_info);type_register_static (&virtio_net_pci_info); +type_register_static (&virtio_pmem_pci_info);#ifdef CONFIG_VHOST_SCSI type_register_static (&vhost_scsi_pci_info);#endif hw/virtio/virtio-pci.h +14
-0@@ -19,6 +19,7 @@#include "hw/virtio/virtio-blk.h" #include "hw/virtio/virtio-net.h" #include "hw/virtio/virtio-rng.h" +#include "hw/virtio/virtio-pmem.h" #include "hw/virtio/virtio-serial.h" #include "hw/virtio/virtio-scsi.h" #include "hw/virtio/virtio-balloon.h" @@ -57,6 +58,7 @@ typedef struct VirtIOInputHostPCI VirtIOInputHostPCI;typedef struct VirtIOGPUPCI VirtIOGPUPCI ;typedef struct VHostVSockPCI VHostVSockPCI ;typedef struct VirtIOCryptoPCI VirtIOCryptoPCI ; +typedef struct VirtIOPMEMPCI VirtIOPMEMPCI ;/* virtio-pci-bus */ @@ -274,6 +276,18 @@ struct VirtIOBlkPCI {VirtIOBlock vdev; }; +/* +* virtio-pmem-pci: This extends VirtioPCIProxy. +*/ +#define TYPE_VIRTIO_PMEM_PCI "virtio-pmem-pci" +#define VIRTIO_PMEM_PCI (obj) \ + OBJECT_CHECK(VirtIOPMEMPCI, (obj), TYPE_VIRTIO_PMEM_PCI) + +struct VirtIOPMEMPCI { +VirtIOPCIProxy parent_obj; +VirtIOPMEM vdev; +}; +/* * virtio-balloon-pci: This extends VirtioPCIProxy. */ hw/virtio/virtio-pmem.c new file +33
-0@@ -0,0 +1,241 @@ +/* +* Virtio pmem device +* +* Copyright (C) 2018 Red Hat, Inc. +* Copyright (C) 2018 Pankaj Gupta <[email protected]> +* +* This work is licensed under the terms of the GNU GPL, version 2. +* See the COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" +#include "qapi/error.h" +#include "qemu-common.h" +#include "qemu/error-report.h" +#include "hw/virtio/virtio-access.h" +#include "hw/virtio/virtio-pmem.h" +#include "hw/mem/memory-device.h" +#include "block/aio.h" +#include "block/thread-pool.h" + +typedef struct VirtIOPMEMresp { +int ret; +}VirtIOPMEMResp ; + +typedef struct VirtIODeviceRequest { +VirtQueueElement elem; +int fd; +VirtIOPMEM *pmem; +VirtIOPMEMResp resp; +}VirtIODeviceRequest ; + +static int worker_cb (void *opaque)
hw/virtio/virtio-pmem.c line 43
Quoted 10 lines
hw/virtio/virtio-pmem.c new file +10
-0+{ +VirtIODeviceRequest *req = opaque; +int err =0 ; + +/* flush raw backing image */ + err =fsync (req->fd); +if (err !=0 ) { + err = errno; + } + req->resp.ret = err;
Host question: are you returning the guest errno code to the host?
If yes, I don't think this is right. I think you probably want to define a constant for error and let the host decide on the errno code to return to the application.
Quoted 313 lines
hw/virtio/virtio-pmem.c new file +198
-0+ +return 0 ; +} + +static void done_cb (void *opaque,int ret) +{ +VirtIODeviceRequest *req = opaque; +int len =iov_from_buf (req->elem.in_sg, req->elem.in_num,0 , + &req->resp,sizeof (VirtIOPMEMResp)); + +/* Callbacks are serialized, so no need to use atomic ops. */ +virtqueue_push (req->pmem->rq_vq, &req->elem, len); +virtio_notify ((VirtIODevice *)req->pmem, req->pmem->rq_vq); +g_free (req); +} + +static void virtio_pmem_flush (VirtIODevice *vdev,VirtQueue *vq) +{ +VirtIODeviceRequest *req; +VirtIOPMEM *pmem =VIRTIO_PMEM (vdev); +HostMemoryBackend *backend =MEMORY_BACKEND (pmem->memdev); +ThreadPool *pool =aio_get_thread_pool (qemu_get_aio_context ()); + + req =virtqueue_pop (vq,sizeof (VirtIODeviceRequest)); +if (!req) { +virtio_error (vdev,"virtio-pmem missing request data" ); +return ; + } + +if (req->elem.out_num <1 || req->elem.in_num <1 ) { +virtio_error (vdev,"virtio-pmem request not proper" ); +g_free (req); +return ; + } + req->fd =memory_region_get_fd (&backend->mr); + req->pmem = pmem; +thread_pool_submit_aio (pool, worker_cb, req, done_cb, req); +} + +static void virtio_pmem_get_config (VirtIODevice *vdev,uint8_t *config) +{ +VirtIOPMEM *pmem =VIRTIO_PMEM (vdev); +struct virtio_pmem_config *pmemcfg = (struct virtio_pmem_config *) config; + +virtio_stq_p (vdev, &pmemcfg->start, pmem->start); +virtio_stq_p (vdev, &pmemcfg->size, pmem->size); +} + +static uint64_t virtio_pmem_get_features (VirtIODevice *vdev,uint64_t features, +Error **errp) +{ +return features; +} + +static void virtio_pmem_realize (DeviceState *dev,Error **errp) +{ +VirtIODevice *vdev =VIRTIO_DEVICE (dev); +VirtIOPMEM *pmem =VIRTIO_PMEM (dev); +MachineState *ms =MACHINE (qdev_get_machine ()); +uint64_t align; +Error *local_err =NULL ; +MemoryRegion *mr; + +if (!pmem->memdev) { +error_setg (errp,"virtio-pmem memdev not set" ); +return ; + } + + mr =host_memory_backend_get_memory (pmem->memdev); + align =memory_region_get_alignment (mr); + pmem->size =QEMU_ALIGN_DOWN (memory_region_size (mr), align); + pmem->start =memory_device_get_free_addr (ms,NULL , align, pmem->size, + &local_err); +if (local_err) { +error_setg (errp,"Can't get free address in mem device" ); +return ; + } +memory_region_init_alias (&pmem->mr,OBJECT (pmem), +"virtio_pmem-memory" , mr,0 , pmem->size); +memory_device_plug_region (ms, &pmem->mr, pmem->start); + +host_memory_backend_set_mapped (pmem->memdev, true); +virtio_init (vdev,TYPE_VIRTIO_PMEM ,VIRTIO_ID_PMEM , +sizeof (struct virtio_pmem_config )); + pmem->rq_vq =virtio_add_queue (vdev,128 , virtio_pmem_flush); +} + +static void virtio_mem_check_memdev (Object *obj,const char *name,Object *val, +Error **errp) +{ +if (host_memory_backend_is_mapped (MEMORY_BACKEND (val))) { +char *path =object_get_canonical_path_component (val); +error_setg (errp,"Can't use already busy memdev: %s" , path); +g_free (path); +return ; + } + +qdev_prop_allow_set_link_before_realize (obj, name, val, errp); +} + +static const char *virtio_pmem_get_device_id (VirtIOPMEM *vm) +{ +Object *obj =OBJECT (vm); +DeviceState *parent_dev; + +/* always use the ID of the proxy device */ +if (obj->parent &&object_dynamic_cast (obj->parent,TYPE_DEVICE )) { + parent_dev =DEVICE (obj->parent); +return parent_dev->id; + } +return NULL ; +} + +static void virtio_pmem_md_fill_device_info (const MemoryDeviceState *md, +MemoryDeviceInfo *info) +{ +VirtioPMemDeviceInfo *vi =g_new0 (VirtioPMemDeviceInfo,1 ); +VirtIOPMEM *vm =VIRTIO_PMEM (md); +const char *id =virtio_pmem_get_device_id (vm); + +if (id) { + vi->has_id = true; + vi->id =g_strdup (id); + } + + vi->start = vm->start; + vi->size = vm->size; + vi->memdev =object_get_canonical_path (OBJECT (vm->memdev)); + + info->u.virtio_pmem.data = vi; + info->type =MEMORY_DEVICE_INFO_KIND_VIRTIO_PMEM ; +} + +static uint64_t virtio_pmem_md_get_addr (const MemoryDeviceState *md) +{ +VirtIOPMEM *vm =VIRTIO_PMEM (md); + +return vm->start; +} + +static uint64_t virtio_pmem_md_get_plugged_size (const MemoryDeviceState *md) +{ +VirtIOPMEM *vm =VIRTIO_PMEM (md); + +return vm->size; +} + +static uint64_t virtio_pmem_md_get_region_size (const MemoryDeviceState *md) +{ +VirtIOPMEM *vm =VIRTIO_PMEM (md); + +return vm->size; +} + +static void virtio_pmem_instance_init (Object *obj) +{ +VirtIOPMEM *vm =VIRTIO_PMEM (obj); +object_property_add_link (obj,"memdev" ,TYPE_MEMORY_BACKEND , + (Object **)&vm->memdev, + (void *) virtio_mem_check_memdev, +OBJ_PROP_LINK_STRONG , + &error_abort); +} + + +static void virtio_pmem_class_init (ObjectClass *klass,void *data) +{ +VirtioDeviceClass *vdc =VIRTIO_DEVICE_CLASS (klass); +MemoryDeviceClass *mdc =MEMORY_DEVICE_CLASS (klass); + + vdc->realize = virtio_pmem_realize; + vdc->get_config = virtio_pmem_get_config; + vdc->get_features = virtio_pmem_get_features; + + mdc->get_addr = virtio_pmem_md_get_addr; + mdc->get_plugged_size = virtio_pmem_md_get_plugged_size; + mdc->get_region_size = virtio_pmem_md_get_region_size; + mdc->fill_device_info = virtio_pmem_md_fill_device_info; +} + +static TypeInfo virtio_pmem_info = { + .name =TYPE_VIRTIO_PMEM , + .parent =TYPE_VIRTIO_DEVICE , + .class_init = virtio_pmem_class_init, + .instance_size =sizeof (VirtIOPMEM), + .instance_init = virtio_pmem_instance_init, + .interfaces = (InterfaceInfo []) { + {TYPE_MEMORY_DEVICE }, + { } + }, +}; + +static void virtio_register_types (void ) +{ +type_register_static (&virtio_pmem_info); +} + +type_init (virtio_register_types)include/hw/pci/pci.h +1
-0@@ -85,6 +85,7 @@ extern bool pci_available;#define PCI_DEVICE_ID_VIRTIO_RNG 0x1005#define PCI_DEVICE_ID_VIRTIO_9P 0x1009#define PCI_DEVICE_ID_VIRTIO_VSOCK 0x1012 +#define PCI_DEVICE_ID_VIRTIO_PMEM 0x1013#define PCI_VENDOR_ID_REDHAT 0x1b36#define PCI_DEVICE_ID_REDHAT_BRIDGE 0x0001include/hw/virtio/virtio-pmem.h new file +42
-0@@ -0,0 +1,42 @@ +/* +* Virtio pmem Device +* +* Copyright Red Hat, Inc. 2018 +* Copyright Pankaj Gupta <[email protected]> +* +* This work is licensed under the terms of the GNU GPL, version 2 or +* (at your option) any later version. See the COPYING file in the +* top-level directory. +*/ + +#ifndef QEMU_VIRTIO_PMEM_H +#define QEMU_VIRTIO_PMEM_H + +#include "hw/virtio/virtio.h" +#include "exec/memory.h" +#include "sysemu/hostmem.h" +#include "standard-headers/linux/virtio_ids.h" +#include "hw/boards.h" +#include "hw/i386/pc.h" + +#define TYPE_VIRTIO_PMEM "virtio-pmem" + +#define VIRTIO_PMEM (obj) \ + OBJECT_CHECK(VirtIOPMEM, (obj), TYPE_VIRTIO_PMEM) + +/* VirtIOPMEM device structure */ +typedef struct VirtIOPMEM { +VirtIODevice parent_obj; + +VirtQueue *rq_vq; +uint64_t start; +uint64_t size; +MemoryRegion mr; +HostMemoryBackend *memdev; +}VirtIOPMEM ; + +struct virtio_pmem_config { +uint64_t start; +uint64_t size; +}; +#endif include/standard-headers/linux/virtio_ids.h +1
-0@@ -43,5 +43,6 @@#define VIRTIO_ID_INPUT 18/* virtio input */ #define VIRTIO_ID_VSOCK 19/* virtio vsock transport */ #define VIRTIO_ID_CRYPTO 20/* virtio crypto */ +#define VIRTIO_ID_PMEM 25/* virtio pmem */ #endif /* _LINUX_VIRTIO_IDS_H */ qapi/misc.json +25
-1@@ -2907,6 +2907,29 @@ } } +## +# @VirtioPMemDeviceInfo: +# +# VirtioPMem state information +# +# @id: device's ID +# +# @start: physical address, where device is mapped +# +# @size: size of memory that the device provides +# +# @memdev: memory backend linked with device +# +# Since: 2.13 +## +{ 'struct': 'VirtioPMemDeviceInfo', + 'data': { '*id': 'str', + 'start': 'size', + 'size': 'size', + 'memdev': 'str' + } +} + ## # @MemoryDeviceInfo: #@@ -2916,7 +2939,8 @@ ## { 'union': 'MemoryDeviceInfo', 'data': { 'dimm': 'PCDIMMDeviceInfo', - 'nvdimm': 'PCDIMMDeviceInfo' + 'nvdimm': 'PCDIMMDeviceInfo', + 'virtio-pmem': 'VirtioPMemDeviceInfo' } }
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
Quoted 196 lines
Quoted 196 lines
This patch adds virtio-pmem Qemu device.
This device presents memory address range information to guest which is backed by file backend type. It acts like persistent memory device for KVM guest. Guest can perform read and persistent write operations on this memory range with the help of DAX capable filesystem.
Persistent guest writes are assured with the help of virtio based flushing interface. When guest userspace space performs fsync on file fd on pmem device, a flush command is send to Qemu over VIRTIO and host side flush/sync is done on backing image file.
Changes from RFC v2:
- Useaio_worker()to avoid Qemu from hanging with blocking fsync call - Stefan
- Use virtio_st*_p() for endianess - Stefan
- Correct indentation inqapi/misc.json- EricSigned-off-by Pankaj Gupta <[email protected]>--- hw/virtio/Makefile.objs | 3 + hw/virtio/virtio-pci.c | 44 +++++ hw/virtio/virtio-pci.h | 14 ++ hw/virtio/virtio-pmem.c | 241 ++++++++++++++++++++++++++++ include/hw/pci/pci.h | 1 + include/hw/virtio/virtio-pmem.h | 42 +++++ include/standard-headers/linux/virtio_ids.h | 1 + qapi/misc.json | 26 ++- 8 files changed, 371 insertions(+), 1 deletion(-) create mode 100644 hw/virtio/virtio-pmem.c create mode 100644 include/hw/virtio/virtio-pmem.hhw/virtio/Makefile.objs +3
-0@@ -10,6 +10,9 @@ obj-$(CONFIG_VIRTIO_CRYPTO) += virtio-crypto.o obj-$(call land,$(CONFIG_VIRTIO_CRYPTO),$(CONFIG_VIRTIO_PCI)) += virtio-crypto-pci.o obj-$(CONFIG_LINUX) += vhost.o vhost-backend.o vhost-user.o +ifeq ($(CONFIG_MEM_HOTPLUG),y) +obj-$(CONFIG_LINUX) += virtio-pmem.o +endif obj-$(CONFIG_VHOST_VSOCK) += vhost-vsock.o endifhw/virtio/virtio-pci.c +43
-0@@ -2521,6 +2521,49 @@ static const TypeInfo virtio_rng_pci_info = { .class_init = virtio_rng_pci_class_init, }; +/* virtio-pmem-pci */ + +static void virtio_pmem_pci_realize (VirtIOPCIProxy *vpci_dev,Error **errp) +{ +VirtIOPMEMPCI *vpmem =VIRTIO_PMEM_PCI (vpci_dev); +DeviceState *vdev =DEVICE (&vpmem->vdev); + +qdev_set_parent_bus (vdev,BUS (&vpci_dev->bus)); +object_property_set_bool (OBJECT (vdev), true,"realized" , errp); +} + +static void virtio_pmem_pci_class_init (ObjectClass *klass,void *data) +{ +DeviceClass *dc =DEVICE_CLASS (klass); +VirtioPCIClass *k =VIRTIO_PCI_CLASS (klass); +PCIDeviceClass *pcidev_k =PCI_DEVICE_CLASS (klass); + k->realize = virtio_pmem_pci_realize; +set_bit (DEVICE_CATEGORY_MISC , dc->categories); + pcidev_k->vendor_id =PCI_VENDOR_ID_REDHAT_QUMRANET ; + pcidev_k->device_id =PCI_DEVICE_ID_VIRTIO_PMEM ; + pcidev_k->revision =VIRTIO_PCI_ABI_VERSION ; + pcidev_k->class_id =PCI_CLASS_OTHERS ; +} + +static void virtio_pmem_pci_instance_init (Object *obj) +{ +VirtIOPMEMPCI *dev =VIRTIO_PMEM_PCI (obj); + +virtio_instance_init_common (obj, &dev->vdev,sizeof (dev->vdev), +TYPE_VIRTIO_PMEM ); +object_property_add_alias (obj,"memdev" ,OBJECT (&dev->vdev),"memdev" , + &error_abort); +} + +static const TypeInfo virtio_pmem_pci_info = { + .name =TYPE_VIRTIO_PMEM_PCI , + .parent =TYPE_VIRTIO_PCI , + .instance_size =sizeof (VirtIOPMEMPCI), + .instance_init = virtio_pmem_pci_instance_init, + .class_init = virtio_pmem_pci_class_init, +}; + +/* virtio-input-pci */ static Property virtio_input_pci_properties[] = {
hw/virtio/virtio-pci.c +1
-0@@ -2714,6 +2757,7 @@ static void virtio_pci_register_types(void)type_register_static (&virtio_balloon_pci_info);type_register_static (&virtio_serial_pci_info);type_register_static (&virtio_net_pci_info); +type_register_static (&virtio_pmem_pci_info);#ifdef CONFIG_VHOST_SCSI type_register_static (&vhost_scsi_pci_info);#endif hw/virtio/virtio-pci.h +14
-0@@ -19,6 +19,7 @@#include "hw/virtio/virtio-blk.h" #include "hw/virtio/virtio-net.h" #include "hw/virtio/virtio-rng.h" +#include "hw/virtio/virtio-pmem.h" #include "hw/virtio/virtio-serial.h" #include "hw/virtio/virtio-scsi.h" #include "hw/virtio/virtio-balloon.h" @@ -57,6 +58,7 @@ typedef struct VirtIOInputHostPCI VirtIOInputHostPCI;typedef struct VirtIOGPUPCI VirtIOGPUPCI ;typedef struct VHostVSockPCI VHostVSockPCI ;typedef struct VirtIOCryptoPCI VirtIOCryptoPCI ; +typedef struct VirtIOPMEMPCI VirtIOPMEMPCI ;/* virtio-pci-bus */ @@ -274,6 +276,18 @@ struct VirtIOBlkPCI {VirtIOBlock vdev; }; +/* +* virtio-pmem-pci: This extends VirtioPCIProxy. +*/ +#define TYPE_VIRTIO_PMEM_PCI "virtio-pmem-pci" +#define VIRTIO_PMEM_PCI (obj) \ + OBJECT_CHECK(VirtIOPMEMPCI, (obj), TYPE_VIRTIO_PMEM_PCI) + +struct VirtIOPMEMPCI { +VirtIOPCIProxy parent_obj; +VirtIOPMEM vdev; +}; +/* * virtio-balloon-pci: This extends VirtioPCIProxy. */ hw/virtio/virtio-pmem.c new file +37
-0@@ -0,0 +1,241 @@ +/* +* Virtio pmem device +* +* Copyright (C) 2018 Red Hat, Inc. +* Copyright (C) 2018 Pankaj Gupta <[email protected]> +* +* This work is licensed under the terms of the GNU GPL, version 2. +* See the COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" +#include "qapi/error.h" +#include "qemu-common.h" +#include "qemu/error-report.h" +#include "hw/virtio/virtio-access.h" +#include "hw/virtio/virtio-pmem.h" +#include "hw/mem/memory-device.h" +#include "block/aio.h" +#include "block/thread-pool.h" + +typedef struct VirtIOPMEMresp { +int ret; +}VirtIOPMEMResp ; + +typedef struct VirtIODeviceRequest { +VirtQueueElement elem; +int fd; +VirtIOPMEM *pmem; +VirtIOPMEMResp resp; +}VirtIODeviceRequest ; + +static int worker_cb (void *opaque) +{ +VirtIODeviceRequest *req = opaque; +int err =0 ; +
Quoted 8 lines
hw/virtio/virtio-pmem.c line 43
Quoted 6 lines
hw/virtio/virtio-pmem.c new file +6
-0+/* flush raw backing image */ + err =fsync (req->fd); +if (err !=0 ) { + err = errno; + } + req->resp.ret = err;Host question: are you returning the guest errno code to the host?
No. I am returning error code from the host in-case of host fsync failure, otherwise returning zero.
Thanks,
Pankaj
Quoted 330 lines
If yes, I don't think this is right. I think you probably want to define a constant for error and let the host decide on the errno code to return to the application.
Quoted 322 lines
hw/virtio/virtio-pmem.c new file +43
-0+ +return 0 ; +} + +static void done_cb (void *opaque,int ret) +{ +VirtIODeviceRequest *req = opaque; +int len =iov_from_buf (req->elem.in_sg, req->elem.in_num,0 , + &req->resp,sizeof (VirtIOPMEMResp)); + +/* Callbacks are serialized, so no need to use atomic ops. */ +virtqueue_push (req->pmem->rq_vq, &req->elem, len); +virtio_notify ((VirtIODevice *)req->pmem, req->pmem->rq_vq); +g_free (req); +} + +static void virtio_pmem_flush (VirtIODevice *vdev,VirtQueue *vq) +{ +VirtIODeviceRequest *req; +VirtIOPMEM *pmem =VIRTIO_PMEM (vdev); +HostMemoryBackend *backend =MEMORY_BACKEND (pmem->memdev); +ThreadPool *pool =aio_get_thread_pool (qemu_get_aio_context ()); + + req =virtqueue_pop (vq,sizeof (VirtIODeviceRequest)); +if (!req) { +virtio_error (vdev,"virtio-pmem missing request data" ); +return ; + } + +if (req->elem.out_num <1 || req->elem.in_num <1 ) { +virtio_error (vdev,"virtio-pmem request not proper" ); +g_free (req); +return ; + } + req->fd =memory_region_get_fd (&backend->mr); + req->pmem = pmem; +thread_pool_submit_aio (pool, worker_cb, req, done_cb, req); +} + +static void virtio_pmem_get_config (VirtIODevice *vdev,uint8_t *config) +{ +VirtIOPMEM *pmem =VIRTIO_PMEM (vdev); + struct virtio_pmem_config *pmemcfg = (struct virtio_pmem_config *)config;
hw/virtio/virtio-pmem.c new file +6
-0+ +virtio_stq_p (vdev, &pmemcfg->start, pmem->start); +virtio_stq_p (vdev, &pmemcfg->size, pmem->size); +} + +static uint64_t virtio_pmem_get_features(VirtIODevice *vdev, uint64_tfeatures,
hw/virtio/virtio-pmem.c new file +24
-0+ Error **errp) +{ +return features; +} + +static void virtio_pmem_realize (DeviceState *dev,Error **errp) +{ +VirtIODevice *vdev =VIRTIO_DEVICE (dev); +VirtIOPMEM *pmem =VIRTIO_PMEM (dev); +MachineState *ms =MACHINE (qdev_get_machine ()); +uint64_t align; +Error *local_err =NULL ; +MemoryRegion *mr; + +if (!pmem->memdev) { +error_setg (errp,"virtio-pmem memdev not set" ); +return ; + } + + mr =host_memory_backend_get_memory (pmem->memdev); + align =memory_region_get_alignment (mr); + pmem->size =QEMU_ALIGN_DOWN (memory_region_size (mr), align); + pmem->start = memory_device_get_free_addr(ms, NULL, align, pmem->size, +
&local_err);hw/virtio/virtio-pmem.c new file +11
-0+if (local_err) { +error_setg (errp,"Can't get free address in mem device" ); +return ; + } +memory_region_init_alias (&pmem->mr,OBJECT (pmem), +"virtio_pmem-memory" , mr,0 , pmem->size); +memory_device_plug_region (ms, &pmem->mr, pmem->start); + +host_memory_backend_set_mapped (pmem->memdev, true); + virtio_init(vdev, TYPE_VIRTIO_PMEM, VIRTIO_ID_PMEM, + sizeof(struct
virtio_pmem_config));hw/virtio/virtio-pmem.c new file +4
-0+ pmem->rq_vq =virtio_add_queue (vdev,128 , virtio_pmem_flush); +} + +static void virtio_mem_check_memdev(Object *obj, const char *name, Object*val,
hw/virtio/virtio-pmem.c new file +53
-0+ Error **errp) +{ +if (host_memory_backend_is_mapped (MEMORY_BACKEND (val))) { +char *path =object_get_canonical_path_component (val); +error_setg (errp,"Can't use already busy memdev: %s" , path); +g_free (path); +return ; + } + +qdev_prop_allow_set_link_before_realize (obj, name, val, errp); +} + +static const char *virtio_pmem_get_device_id (VirtIOPMEM *vm) +{ +Object *obj =OBJECT (vm); +DeviceState *parent_dev; + +/* always use the ID of the proxy device */ +if (obj->parent &&object_dynamic_cast (obj->parent,TYPE_DEVICE )) { + parent_dev =DEVICE (obj->parent); +return parent_dev->id; + } +return NULL ; +} + +static void virtio_pmem_md_fill_device_info (const MemoryDeviceState *md, +MemoryDeviceInfo *info) +{ +VirtioPMemDeviceInfo *vi =g_new0 (VirtioPMemDeviceInfo,1 ); +VirtIOPMEM *vm =VIRTIO_PMEM (md); +const char *id =virtio_pmem_get_device_id (vm); + +if (id) { + vi->has_id = true; + vi->id =g_strdup (id); + } + + vi->start = vm->start; + vi->size = vm->size; + vi->memdev =object_get_canonical_path (OBJECT (vm->memdev)); + + info->u.virtio_pmem.data = vi; + info->type =MEMORY_DEVICE_INFO_KIND_VIRTIO_PMEM ; +} + +static uint64_t virtio_pmem_md_get_addr (const MemoryDeviceState *md) +{ +VirtIOPMEM *vm =VIRTIO_PMEM (md); + +return vm->start; +} + +static uint64_t virtio_pmem_md_get_plugged_size(const MemoryDeviceState*md)
hw/virtio/virtio-pmem.c new file +7
-0+{ +VirtIOPMEM *vm =VIRTIO_PMEM (md); + +return vm->size; +} + +static uint64_t virtio_pmem_md_get_region_size(const MemoryDeviceState*md)
hw/virtio/virtio-pmem.c new file +50
-0+{ +VirtIOPMEM *vm =VIRTIO_PMEM (md); + +return vm->size; +} + +static void virtio_pmem_instance_init (Object *obj) +{ +VirtIOPMEM *vm =VIRTIO_PMEM (obj); +object_property_add_link (obj,"memdev" ,TYPE_MEMORY_BACKEND , + (Object **)&vm->memdev, + (void *) virtio_mem_check_memdev, +OBJ_PROP_LINK_STRONG , + &error_abort); +} + + +static void virtio_pmem_class_init (ObjectClass *klass,void *data) +{ +VirtioDeviceClass *vdc =VIRTIO_DEVICE_CLASS (klass); +MemoryDeviceClass *mdc =MEMORY_DEVICE_CLASS (klass); + + vdc->realize = virtio_pmem_realize; + vdc->get_config = virtio_pmem_get_config; + vdc->get_features = virtio_pmem_get_features; + + mdc->get_addr = virtio_pmem_md_get_addr; + mdc->get_plugged_size = virtio_pmem_md_get_plugged_size; + mdc->get_region_size = virtio_pmem_md_get_region_size; + mdc->fill_device_info = virtio_pmem_md_fill_device_info; +} + +static TypeInfo virtio_pmem_info = { + .name =TYPE_VIRTIO_PMEM , + .parent =TYPE_VIRTIO_DEVICE , + .class_init = virtio_pmem_class_init, + .instance_size =sizeof (VirtIOPMEM), + .instance_init = virtio_pmem_instance_init, + .interfaces = (InterfaceInfo []) { + {TYPE_MEMORY_DEVICE }, + { } + }, +}; + +static void virtio_register_types (void ) +{ +type_register_static (&virtio_pmem_info); +} + +type_init (virtio_register_types)include/hw/pci/pci.h +1
-0@@ -85,6 +85,7 @@ extern bool pci_available;#define PCI_DEVICE_ID_VIRTIO_RNG 0x1005#define PCI_DEVICE_ID_VIRTIO_9P 0x1009#define PCI_DEVICE_ID_VIRTIO_VSOCK 0x1012 +#define PCI_DEVICE_ID_VIRTIO_PMEM 0x1013#define PCI_VENDOR_ID_REDHAT 0x1b36#define PCI_DEVICE_ID_REDHAT_BRIDGE 0x0001include/hw/virtio/virtio-pmem.h new file +42
-0@@ -0,0 +1,42 @@ +/* +* Virtio pmem Device +* +* Copyright Red Hat, Inc. 2018 +* Copyright Pankaj Gupta <[email protected]> +* +* This work is licensed under the terms of the GNU GPL, version 2 or +* (at your option) any later version. See the COPYING file in the +* top-level directory. +*/ + +#ifndef QEMU_VIRTIO_PMEM_H +#define QEMU_VIRTIO_PMEM_H + +#include "hw/virtio/virtio.h" +#include "exec/memory.h" +#include "sysemu/hostmem.h" +#include "standard-headers/linux/virtio_ids.h" +#include "hw/boards.h" +#include "hw/i386/pc.h" + +#define TYPE_VIRTIO_PMEM "virtio-pmem" + +#define VIRTIO_PMEM (obj) \ + OBJECT_CHECK(VirtIOPMEM, (obj), TYPE_VIRTIO_PMEM) + +/* VirtIOPMEM device structure */ +typedef struct VirtIOPMEM { +VirtIODevice parent_obj; + +VirtQueue *rq_vq; +uint64_t start; +uint64_t size; +MemoryRegion mr; +HostMemoryBackend *memdev; +}VirtIOPMEM ; + +struct virtio_pmem_config { +uint64_t start; +uint64_t size; +}; +#endif include/standard-headers/linux/virtio_ids.h +1
-0@@ -43,5 +43,6 @@#define VIRTIO_ID_INPUT 18/* virtio input */ #define VIRTIO_ID_VSOCK 19/* virtio vsock transport */ #define VIRTIO_ID_CRYPTO 20/* virtio crypto */ +#define VIRTIO_ID_PMEM 25/* virtio pmem */ #endif /* _LINUX_VIRTIO_IDS_H */ qapi/misc.json +25
-1@@ -2907,6 +2907,29 @@ } } +## +# @VirtioPMemDeviceInfo: +# +# VirtioPMem state information +# +# @id: device's ID +# +# @start: physical address, where device is mapped +# +# @size: size of memory that the device provides +# +# @memdev: memory backend linked with device +# +# Since: 2.13 +## +{ 'struct': 'VirtioPMemDeviceInfo', + 'data': { '*id': 'str', + 'start': 'size', + 'size': 'size', + 'memdev': 'str' + } +} + ## # @MemoryDeviceInfo: #@@ -2916,7 +2939,8 @@ ## { 'union': 'MemoryDeviceInfo', 'data': { 'dimm': 'PCDIMMDeviceInfo', - 'nvdimm': 'PCDIMMDeviceInfo' + 'nvdimm': 'PCDIMMDeviceInfo', + 'virtio-pmem': 'VirtioPMemDeviceInfo' } }
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
Quoted 205 lines · Pankaj Gupta
Quoted 196 lines
Quoted 196 lines
This patch adds virtio-pmem Qemu device.
This device presents memory address range information to guest which is backed by file backend type. It acts like persistent memory device for KVM guest. Guest can perform read and persistent write operations on this memory range with the help of DAX capable filesystem.
Persistent guest writes are assured with the help of virtio based flushing interface. When guest userspace space performs fsync on file fd on pmem device, a flush command is send to Qemu over VIRTIO and host side flush/sync is done on backing image file.
Changes from RFC v2:
- Useaio_worker()to avoid Qemu from hanging with blocking fsync call - Stefan
- Use virtio_st*_p() for endianess - Stefan
- Correct indentation inqapi/misc.json- EricSigned-off-by Pankaj Gupta <[email protected]>--- hw/virtio/Makefile.objs | 3 + hw/virtio/virtio-pci.c | 44 +++++ hw/virtio/virtio-pci.h | 14 ++ hw/virtio/virtio-pmem.c | 241 ++++++++++++++++++++++++++++ include/hw/pci/pci.h | 1 + include/hw/virtio/virtio-pmem.h | 42 +++++ include/standard-headers/linux/virtio_ids.h | 1 + qapi/misc.json | 26 ++- 8 files changed, 371 insertions(+), 1 deletion(-) create mode 100644 hw/virtio/virtio-pmem.c create mode 100644 include/hw/virtio/virtio-pmem.hhw/virtio/Makefile.objs +3
-0@@ -10,6 +10,9 @@ obj-$(CONFIG_VIRTIO_CRYPTO) += virtio-crypto.o obj-$(call land,$(CONFIG_VIRTIO_CRYPTO),$(CONFIG_VIRTIO_PCI)) += virtio-crypto-pci.o obj-$(CONFIG_LINUX) += vhost.o vhost-backend.o vhost-user.o +ifeq ($(CONFIG_MEM_HOTPLUG),y) +obj-$(CONFIG_LINUX) += virtio-pmem.o +endif obj-$(CONFIG_VHOST_VSOCK) += vhost-vsock.o endifhw/virtio/virtio-pci.c +43
-0@@ -2521,6 +2521,49 @@ static const TypeInfo virtio_rng_pci_info = { .class_init = virtio_rng_pci_class_init, }; +/* virtio-pmem-pci */ + +static void virtio_pmem_pci_realize (VirtIOPCIProxy *vpci_dev,Error **errp) +{ +VirtIOPMEMPCI *vpmem =VIRTIO_PMEM_PCI (vpci_dev); +DeviceState *vdev =DEVICE (&vpmem->vdev); + +qdev_set_parent_bus (vdev,BUS (&vpci_dev->bus)); +object_property_set_bool (OBJECT (vdev), true,"realized" , errp); +} + +static void virtio_pmem_pci_class_init (ObjectClass *klass,void *data) +{ +DeviceClass *dc =DEVICE_CLASS (klass); +VirtioPCIClass *k =VIRTIO_PCI_CLASS (klass); +PCIDeviceClass *pcidev_k =PCI_DEVICE_CLASS (klass); + k->realize = virtio_pmem_pci_realize; +set_bit (DEVICE_CATEGORY_MISC , dc->categories); + pcidev_k->vendor_id =PCI_VENDOR_ID_REDHAT_QUMRANET ; + pcidev_k->device_id =PCI_DEVICE_ID_VIRTIO_PMEM ; + pcidev_k->revision =VIRTIO_PCI_ABI_VERSION ; + pcidev_k->class_id =PCI_CLASS_OTHERS ; +} + +static void virtio_pmem_pci_instance_init (Object *obj) +{ +VirtIOPMEMPCI *dev =VIRTIO_PMEM_PCI (obj); + +virtio_instance_init_common (obj, &dev->vdev,sizeof (dev->vdev), +TYPE_VIRTIO_PMEM ); +object_property_add_alias (obj,"memdev" ,OBJECT (&dev->vdev),"memdev" , + &error_abort); +} + +static const TypeInfo virtio_pmem_pci_info = { + .name =TYPE_VIRTIO_PMEM_PCI , + .parent =TYPE_VIRTIO_PCI , + .instance_size =sizeof (VirtIOPMEMPCI), + .instance_init = virtio_pmem_pci_instance_init, + .class_init = virtio_pmem_pci_class_init, +}; + +/* virtio-input-pci */ static Property virtio_input_pci_properties[] = {
hw/virtio/virtio-pci.c +1
-0@@ -2714,6 +2757,7 @@ static void virtio_pci_register_types(void)type_register_static (&virtio_balloon_pci_info);type_register_static (&virtio_serial_pci_info);type_register_static (&virtio_net_pci_info); +type_register_static (&virtio_pmem_pci_info);#ifdef CONFIG_VHOST_SCSI type_register_static (&vhost_scsi_pci_info);#endif hw/virtio/virtio-pci.h +14
-0@@ -19,6 +19,7 @@#include "hw/virtio/virtio-blk.h" #include "hw/virtio/virtio-net.h" #include "hw/virtio/virtio-rng.h" +#include "hw/virtio/virtio-pmem.h" #include "hw/virtio/virtio-serial.h" #include "hw/virtio/virtio-scsi.h" #include "hw/virtio/virtio-balloon.h" @@ -57,6 +58,7 @@ typedef struct VirtIOInputHostPCI VirtIOInputHostPCI;typedef struct VirtIOGPUPCI VirtIOGPUPCI ;typedef struct VHostVSockPCI VHostVSockPCI ;typedef struct VirtIOCryptoPCI VirtIOCryptoPCI ; +typedef struct VirtIOPMEMPCI VirtIOPMEMPCI ;/* virtio-pci-bus */ @@ -274,6 +276,18 @@ struct VirtIOBlkPCI {VirtIOBlock vdev; }; +/* +* virtio-pmem-pci: This extends VirtioPCIProxy. +*/ +#define TYPE_VIRTIO_PMEM_PCI "virtio-pmem-pci" +#define VIRTIO_PMEM_PCI (obj) \ + OBJECT_CHECK(VirtIOPMEMPCI, (obj), TYPE_VIRTIO_PMEM_PCI) + +struct VirtIOPMEMPCI { +VirtIOPCIProxy parent_obj; +VirtIOPMEM vdev; +}; +/* * virtio-balloon-pci: This extends VirtioPCIProxy. */ hw/virtio/virtio-pmem.c new file +37
-0@@ -0,0 +1,241 @@ +/* +* Virtio pmem device +* +* Copyright (C) 2018 Red Hat, Inc. +* Copyright (C) 2018 Pankaj Gupta <[email protected]> +* +* This work is licensed under the terms of the GNU GPL, version 2. +* See the COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" +#include "qapi/error.h" +#include "qemu-common.h" +#include "qemu/error-report.h" +#include "hw/virtio/virtio-access.h" +#include "hw/virtio/virtio-pmem.h" +#include "hw/mem/memory-device.h" +#include "block/aio.h" +#include "block/thread-pool.h" + +typedef struct VirtIOPMEMresp { +int ret; +}VirtIOPMEMResp ; + +typedef struct VirtIODeviceRequest { +VirtQueueElement elem; +int fd; +VirtIOPMEM *pmem; +VirtIOPMEMResp resp; +}VirtIODeviceRequest ; + +static int worker_cb (void *opaque) +{ +VirtIODeviceRequest *req = opaque; +int err =0 ; +Quoted 8 lines
hw/virtio/virtio-pmem.c line 43
Quoted 6 lines
hw/virtio/virtio-pmem.c new file +6
-0+/* flush raw backing image */ + err =fsync (req->fd); +if (err !=0 ) { + err = errno; + } + req->resp.ret = err;Host question: are you returning the guest errno code to the host?
Quoted 2 lines
No. I am returning error code from the host in-case of host fsync failure, otherwise returning zero.
I think that's what Luiz meant. errno constants are not portable between operating systems and architectures. Therefore they cannot be used in external interfaces in software that expects to communicate with other systems.
It will be necessary to define specific constants for virtio-pmem instead of passing errno from the host to guest.
Stefan
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
Quoted 206 lines · On Thu, 19 Jul 2018 13:16:35 +0100 Stefan Hajnoczi…
Quoted 205 lines · Pankaj Gupta
Quoted 204 lines
Quoted 192 lines
This patch adds virtio-pmem Qemu device.
This device presents memory address range information to guest which is backed by file backend type. It acts like persistent memory device for KVM guest. Guest can perform read and persistent write operations on this memory range with the help of DAX capable filesystem.
Persistent guest writes are assured with the help of virtio based flushing interface. When guest userspace space performs fsync on file fd on pmem device, a flush command is send to Qemu over VIRTIO and host side flush/sync is done on backing image file.
Changes from RFC v2:
- Useaio_worker()to avoid Qemu from hanging with blocking fsync call - Stefan
- Use virtio_st*_p() for endianess - Stefan
- Correct indentation inqapi/misc.json- EricSigned-off-by Pankaj Gupta <[email protected]>--- hw/virtio/Makefile.objs | 3 + hw/virtio/virtio-pci.c | 44 +++++ hw/virtio/virtio-pci.h | 14 ++ hw/virtio/virtio-pmem.c | 241 ++++++++++++++++++++++++++++ include/hw/pci/pci.h | 1 + include/hw/virtio/virtio-pmem.h | 42 +++++ include/standard-headers/linux/virtio_ids.h | 1 + qapi/misc.json | 26 ++- 8 files changed, 371 insertions(+), 1 deletion(-) create mode 100644 hw/virtio/virtio-pmem.c create mode 100644 include/hw/virtio/virtio-pmem.hhw/virtio/Makefile.objs +3
-0@@ -10,6 +10,9 @@ obj-$(CONFIG_VIRTIO_CRYPTO) += virtio-crypto.o obj-$(call land,$(CONFIG_VIRTIO_CRYPTO),$(CONFIG_VIRTIO_PCI)) += virtio-crypto-pci.o obj-$(CONFIG_LINUX) += vhost.o vhost-backend.o vhost-user.o +ifeq ($(CONFIG_MEM_HOTPLUG),y) +obj-$(CONFIG_LINUX) += virtio-pmem.o +endif obj-$(CONFIG_VHOST_VSOCK) += vhost-vsock.o endifhw/virtio/virtio-pci.c +43
-0@@ -2521,6 +2521,49 @@ static const TypeInfo virtio_rng_pci_info = { .class_init = virtio_rng_pci_class_init, }; +/* virtio-pmem-pci */ + +static void virtio_pmem_pci_realize (VirtIOPCIProxy *vpci_dev,Error **errp) +{ +VirtIOPMEMPCI *vpmem =VIRTIO_PMEM_PCI (vpci_dev); +DeviceState *vdev =DEVICE (&vpmem->vdev); + +qdev_set_parent_bus (vdev,BUS (&vpci_dev->bus)); +object_property_set_bool (OBJECT (vdev), true,"realized" , errp); +} + +static void virtio_pmem_pci_class_init (ObjectClass *klass,void *data) +{ +DeviceClass *dc =DEVICE_CLASS (klass); +VirtioPCIClass *k =VIRTIO_PCI_CLASS (klass); +PCIDeviceClass *pcidev_k =PCI_DEVICE_CLASS (klass); + k->realize = virtio_pmem_pci_realize; +set_bit (DEVICE_CATEGORY_MISC , dc->categories); + pcidev_k->vendor_id =PCI_VENDOR_ID_REDHAT_QUMRANET ; + pcidev_k->device_id =PCI_DEVICE_ID_VIRTIO_PMEM ; + pcidev_k->revision =VIRTIO_PCI_ABI_VERSION ; + pcidev_k->class_id =PCI_CLASS_OTHERS ; +} + +static void virtio_pmem_pci_instance_init (Object *obj) +{ +VirtIOPMEMPCI *dev =VIRTIO_PMEM_PCI (obj); + +virtio_instance_init_common (obj, &dev->vdev,sizeof (dev->vdev), +TYPE_VIRTIO_PMEM ); +object_property_add_alias (obj,"memdev" ,OBJECT (&dev->vdev),"memdev" , + &error_abort); +} + +static const TypeInfo virtio_pmem_pci_info = { + .name =TYPE_VIRTIO_PMEM_PCI , + .parent =TYPE_VIRTIO_PCI , + .instance_size =sizeof (VirtIOPMEMPCI), + .instance_init = virtio_pmem_pci_instance_init, + .class_init = virtio_pmem_pci_class_init, +}; + +/* virtio-input-pci */ static Property virtio_input_pci_properties[] = {
hw/virtio/virtio-pci.c +1
-0@@ -2714,6 +2757,7 @@ static void virtio_pci_register_types(void)type_register_static (&virtio_balloon_pci_info);type_register_static (&virtio_serial_pci_info);type_register_static (&virtio_net_pci_info); +type_register_static (&virtio_pmem_pci_info);#ifdef CONFIG_VHOST_SCSI type_register_static (&vhost_scsi_pci_info);#endif hw/virtio/virtio-pci.h +14
-0@@ -19,6 +19,7 @@#include "hw/virtio/virtio-blk.h" #include "hw/virtio/virtio-net.h" #include "hw/virtio/virtio-rng.h" +#include "hw/virtio/virtio-pmem.h" #include "hw/virtio/virtio-serial.h" #include "hw/virtio/virtio-scsi.h" #include "hw/virtio/virtio-balloon.h" @@ -57,6 +58,7 @@ typedef struct VirtIOInputHostPCI VirtIOInputHostPCI;typedef struct VirtIOGPUPCI VirtIOGPUPCI ;typedef struct VHostVSockPCI VHostVSockPCI ;typedef struct VirtIOCryptoPCI VirtIOCryptoPCI ; +typedef struct VirtIOPMEMPCI VirtIOPMEMPCI ;/* virtio-pci-bus */ @@ -274,6 +276,18 @@ struct VirtIOBlkPCI {VirtIOBlock vdev; }; +/* +* virtio-pmem-pci: This extends VirtioPCIProxy. +*/ +#define TYPE_VIRTIO_PMEM_PCI "virtio-pmem-pci" +#define VIRTIO_PMEM_PCI (obj) \ + OBJECT_CHECK(VirtIOPMEMPCI, (obj), TYPE_VIRTIO_PMEM_PCI) + +struct VirtIOPMEMPCI { +VirtIOPCIProxy parent_obj; +VirtIOPMEM vdev; +}; +/* * virtio-balloon-pci: This extends VirtioPCIProxy. */ hw/virtio/virtio-pmem.c new file +33
-0@@ -0,0 +1,241 @@ +/* +* Virtio pmem device +* +* Copyright (C) 2018 Red Hat, Inc. +* Copyright (C) 2018 Pankaj Gupta <[email protected]> +* +* This work is licensed under the terms of the GNU GPL, version 2. +* See the COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" +#include "qapi/error.h" +#include "qemu-common.h" +#include "qemu/error-report.h" +#include "hw/virtio/virtio-access.h" +#include "hw/virtio/virtio-pmem.h" +#include "hw/mem/memory-device.h" +#include "block/aio.h" +#include "block/thread-pool.h" + +typedef struct VirtIOPMEMresp { +int ret; +}VirtIOPMEMResp ; + +typedef struct VirtIODeviceRequest { +VirtQueueElement elem; +int fd; +VirtIOPMEM *pmem; +VirtIOPMEMResp resp; +}VirtIODeviceRequest ; + +static int worker_cb (void *opaque)hw/virtio/virtio-pmem.c line 43
Quoted 10 lines
hw/virtio/virtio-pmem.c new file +10
-0+{ +VirtIODeviceRequest *req = opaque; +int err =0 ; + +/* flush raw backing image */ + err =fsync (req->fd); +if (err !=0 ) { + err = errno; + } + req->resp.ret = err;Host question: are you returning the guest errno code to the host?
Quoted 7 lines
Quoted 2 lines
No. I am returning error code from the host in-case of host fsync failure, otherwise returning zero.
I think that's what Luiz meant. errno constants are not portable between operating systems and architectures. Therefore they cannot be used in external interfaces in software that expects to communicate with other systems.
Oh, thanks. Only saw this email now.
Quoted 2 lines
It will be necessary to define specific constants for virtio-pmem instead of passing errno from the host to guest.
Yes, defining your own constants work. But I think the only fsync() error that will make sense for the guest is EIO. The other errors only make sense for the host.
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
Quoted 6 lines · On Thu, 19 Jul 2018 08:48:19 -0400 Luiz Capitulino <[email protected]>…
Quoted 2 lines
It will be necessary to define specific constants for virtio-pmem instead of passing errno from the host to guest.
Yes, defining your own constants work. But I think the only
fsync()error that will make sense for the guest is EIO. The other errors only make sense for the host.
Just to clarify: of course you'll return an error to guest on any fsync() error. But maybe you should always return EIO even if the error was EBADF for example. Or just signal the error with some constant, and let the guest implementation pick any errno it prefers (this was my first suggestion).
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
In reply to Luiz CapitulinoQuoted 35 lines
Quoted 27 lines
Quoted 27 lines
Quoted 26 lines
Quoted 14 lines
hw/virtio/virtio-pmem.c new file +13
-0+ +typedef struct VirtIOPMEMresp { +int ret; +}VirtIOPMEMResp ; + +typedef struct VirtIODeviceRequest { +VirtQueueElement elem; +int fd; +VirtIOPMEM *pmem; +VirtIOPMEMResp resp; +}VirtIODeviceRequest ; + +static int worker_cb (void *opaque)hw/virtio/virtio-pmem.c line 43
Quoted 10 lines
hw/virtio/virtio-pmem.c new file +10
-0+{ +VirtIODeviceRequest *req = opaque; +int err =0 ; + +/* flush raw backing image */ + err =fsync (req->fd); +if (err !=0 ) { + err = errno; + } + req->resp.ret = err;Host question: are you returning the guest errno code to the host?
Quoted 7 lines
Quoted 2 lines
No. I am returning error code from the host in-case of host fsync failure, otherwise returning zero.
I think that's what Luiz meant. errno constants are not portable between operating systems and architectures. Therefore they cannot be used in external interfaces in software that expects to communicate with other systems.
Quoted 8 lines
Oh, thanks. Only saw this email now.
Quoted 2 lines
It will be necessary to define specific constants for virtio-pmem instead of passing errno from the host to guest.
Yes, defining your own constants work. But I think the only
fsync()error that will make sense for the guest is EIO. The other errors only make sense for the host.
Agree.
Thanks,
Pankaj
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
In reply to Stefan HajnocziQuoted 209 lines · Stefan Hajnoczi
Quoted 205 lines · Pankaj Gupta
Quoted 196 lines
Quoted 196 lines
This patch adds virtio-pmem Qemu device.
This device presents memory address range information to guest which is backed by file backend type. It acts like persistent memory device for KVM guest. Guest can perform read and persistent write operations on this memory range with the help of DAX capable filesystem.
Persistent guest writes are assured with the help of virtio based flushing interface. When guest userspace space performs fsync on file fd on pmem device, a flush command is send to Qemu over VIRTIO and host side flush/sync is done on backing image file.
Changes from RFC v2:
- Useaio_worker()to avoid Qemu from hanging with blocking fsync call - Stefan
- Use virtio_st*_p() for endianess - Stefan
- Correct indentation inqapi/misc.json- EricSigned-off-by Pankaj Gupta <[email protected]>--- hw/virtio/Makefile.objs | 3 + hw/virtio/virtio-pci.c | 44 +++++ hw/virtio/virtio-pci.h | 14 ++ hw/virtio/virtio-pmem.c | 241 ++++++++++++++++++++++++++++ include/hw/pci/pci.h | 1 + include/hw/virtio/virtio-pmem.h | 42 +++++ include/standard-headers/linux/virtio_ids.h | 1 + qapi/misc.json | 26 ++- 8 files changed, 371 insertions(+), 1 deletion(-) create mode 100644 hw/virtio/virtio-pmem.c create mode 100644 include/hw/virtio/virtio-pmem.hhw/virtio/Makefile.objs +3
-0@@ -10,6 +10,9 @@ obj-$(CONFIG_VIRTIO_CRYPTO) += virtio-crypto.o obj-$(call land,$(CONFIG_VIRTIO_CRYPTO),$(CONFIG_VIRTIO_PCI)) += virtio-crypto-pci.o obj-$(CONFIG_LINUX) += vhost.o vhost-backend.o vhost-user.o +ifeq ($(CONFIG_MEM_HOTPLUG),y) +obj-$(CONFIG_LINUX) += virtio-pmem.o +endif obj-$(CONFIG_VHOST_VSOCK) += vhost-vsock.o endifhw/virtio/virtio-pci.c +43
-0@@ -2521,6 +2521,49 @@ static const TypeInfo virtio_rng_pci_info = { .class_init = virtio_rng_pci_class_init, }; +/* virtio-pmem-pci */ + +static void virtio_pmem_pci_realize (VirtIOPCIProxy *vpci_dev,Error **errp) +{ +VirtIOPMEMPCI *vpmem =VIRTIO_PMEM_PCI (vpci_dev); +DeviceState *vdev =DEVICE (&vpmem->vdev); + +qdev_set_parent_bus (vdev,BUS (&vpci_dev->bus)); +object_property_set_bool (OBJECT (vdev), true,"realized" , errp); +} + +static void virtio_pmem_pci_class_init (ObjectClass *klass,void *data) +{ +DeviceClass *dc =DEVICE_CLASS (klass); +VirtioPCIClass *k =VIRTIO_PCI_CLASS (klass); +PCIDeviceClass *pcidev_k =PCI_DEVICE_CLASS (klass); + k->realize = virtio_pmem_pci_realize; +set_bit (DEVICE_CATEGORY_MISC , dc->categories); + pcidev_k->vendor_id =PCI_VENDOR_ID_REDHAT_QUMRANET ; + pcidev_k->device_id =PCI_DEVICE_ID_VIRTIO_PMEM ; + pcidev_k->revision =VIRTIO_PCI_ABI_VERSION ; + pcidev_k->class_id =PCI_CLASS_OTHERS ; +} + +static void virtio_pmem_pci_instance_init (Object *obj) +{ +VirtIOPMEMPCI *dev =VIRTIO_PMEM_PCI (obj); + +virtio_instance_init_common (obj, &dev->vdev,sizeof (dev->vdev), +TYPE_VIRTIO_PMEM ); +object_property_add_alias (obj,"memdev" ,OBJECT (&dev->vdev),"memdev" , + &error_abort); +} + +static const TypeInfo virtio_pmem_pci_info = { + .name =TYPE_VIRTIO_PMEM_PCI , + .parent =TYPE_VIRTIO_PCI , + .instance_size =sizeof (VirtIOPMEMPCI), + .instance_init = virtio_pmem_pci_instance_init, + .class_init = virtio_pmem_pci_class_init, +}; + +/* virtio-input-pci */ static Property virtio_input_pci_properties[] = {
hw/virtio/virtio-pci.c +1
-0@@ -2714,6 +2757,7 @@ static void virtio_pci_register_types(void)type_register_static (&virtio_balloon_pci_info);type_register_static (&virtio_serial_pci_info);type_register_static (&virtio_net_pci_info); +type_register_static (&virtio_pmem_pci_info);#ifdef CONFIG_VHOST_SCSI type_register_static (&vhost_scsi_pci_info);#endif hw/virtio/virtio-pci.h +14
-0@@ -19,6 +19,7 @@#include "hw/virtio/virtio-blk.h" #include "hw/virtio/virtio-net.h" #include "hw/virtio/virtio-rng.h" +#include "hw/virtio/virtio-pmem.h" #include "hw/virtio/virtio-serial.h" #include "hw/virtio/virtio-scsi.h" #include "hw/virtio/virtio-balloon.h" @@ -57,6 +58,7 @@ typedef struct VirtIOInputHostPCI VirtIOInputHostPCI;typedef struct VirtIOGPUPCI VirtIOGPUPCI ;typedef struct VHostVSockPCI VHostVSockPCI ;typedef struct VirtIOCryptoPCI VirtIOCryptoPCI ; +typedef struct VirtIOPMEMPCI VirtIOPMEMPCI ;/* virtio-pci-bus */ @@ -274,6 +276,18 @@ struct VirtIOBlkPCI {VirtIOBlock vdev; }; +/* +* virtio-pmem-pci: This extends VirtioPCIProxy. +*/ +#define TYPE_VIRTIO_PMEM_PCI "virtio-pmem-pci" +#define VIRTIO_PMEM_PCI (obj) \ + OBJECT_CHECK(VirtIOPMEMPCI, (obj), TYPE_VIRTIO_PMEM_PCI) + +struct VirtIOPMEMPCI { +VirtIOPCIProxy parent_obj; +VirtIOPMEM vdev; +}; +/* * virtio-balloon-pci: This extends VirtioPCIProxy. */ hw/virtio/virtio-pmem.c new file +37
-0@@ -0,0 +1,241 @@ +/* +* Virtio pmem device +* +* Copyright (C) 2018 Red Hat, Inc. +* Copyright (C) 2018 Pankaj Gupta <[email protected]> +* +* This work is licensed under the terms of the GNU GPL, version 2. +* See the COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" +#include "qapi/error.h" +#include "qemu-common.h" +#include "qemu/error-report.h" +#include "hw/virtio/virtio-access.h" +#include "hw/virtio/virtio-pmem.h" +#include "hw/mem/memory-device.h" +#include "block/aio.h" +#include "block/thread-pool.h" + +typedef struct VirtIOPMEMresp { +int ret; +}VirtIOPMEMResp ; + +typedef struct VirtIODeviceRequest { +VirtQueueElement elem; +int fd; +VirtIOPMEM *pmem; +VirtIOPMEMResp resp; +}VirtIODeviceRequest ; + +static int worker_cb (void *opaque) +{ +VirtIODeviceRequest *req = opaque; +int err =0 ; +Quoted 8 lines
hw/virtio/virtio-pmem.c line 43
Quoted 6 lines
hw/virtio/virtio-pmem.c new file +6
-0+/* flush raw backing image */ + err =fsync (req->fd); +if (err !=0 ) { + err = errno; + } + req->resp.ret = err;Host question: are you returning the guest errno code to the host?
Quoted 2 lines
No. I am returning error code from the host in-case of host fsync failure, otherwise returning zero.
Quoted 8 lines
I think that's what Luiz meant. errno constants are not portable between operating systems and architectures. Therefore they cannot be used in external interfaces in software that expects to communicate with other systems.
It will be necessary to define specific constants for virtio-pmem instead of passing errno from the host to guest.
In general, I wonder if we should report errors at all or rather *kill* the guest. That might sound harsh, but think about the following scenario:
fsync() fails due to some block that cannot e.g. be written (e.g. network connection failed). What happens if our guest tries to read/write that mmaped block? (e.g. network connection failed).
I assume we'll get a signal an get killed? So we are trying to optimize one special case (fsync()) although every read/write is prone to kill the guest. And as soon as the guest will try to access the block that made fsync fail, we will crash the guest either way.
I assume the main problem is that we are trying to take a file (with all the errors that can happen during read/write/fsync) and make it look like memory (dax). On ordinary block access, we can forward errors, but not if it's memory (maybe using MCE, but it's complicated and architecture specific).
So I wonder if we should rather assume that our backend file is placed on some stable storage that cannot easily fail.
(we might have the same problem with NVDIMM right now, at least the memory reading/writing part)
It's complicated and I am not a block level expert :)
Quoted 2 lines
Stefan
Signature · 3 lines
Thanks, David / dhildenb
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
Quoted 215 lines · On Thu, 19 Jul 2018 15:58:20 +0200 David Hildenbrand…
Quoted 214 lines · Stefan Hajnoczi
Quoted 205 lines · Pankaj Gupta
Quoted 196 lines
Quoted 196 lines
This patch adds virtio-pmem Qemu device.
This device presents memory address range information to guest which is backed by file backend type. It acts like persistent memory device for KVM guest. Guest can perform read and persistent write operations on this memory range with the help of DAX capable filesystem.
Persistent guest writes are assured with the help of virtio based flushing interface. When guest userspace space performs fsync on file fd on pmem device, a flush command is send to Qemu over VIRTIO and host side flush/sync is done on backing image file.
Changes from RFC v2:
- Useaio_worker()to avoid Qemu from hanging with blocking fsync call - Stefan
- Use virtio_st*_p() for endianess - Stefan
- Correct indentation inqapi/misc.json- EricSigned-off-by Pankaj Gupta <[email protected]>--- hw/virtio/Makefile.objs | 3 + hw/virtio/virtio-pci.c | 44 +++++ hw/virtio/virtio-pci.h | 14 ++ hw/virtio/virtio-pmem.c | 241 ++++++++++++++++++++++++++++ include/hw/pci/pci.h | 1 + include/hw/virtio/virtio-pmem.h | 42 +++++ include/standard-headers/linux/virtio_ids.h | 1 + qapi/misc.json | 26 ++- 8 files changed, 371 insertions(+), 1 deletion(-) create mode 100644 hw/virtio/virtio-pmem.c create mode 100644 include/hw/virtio/virtio-pmem.hhw/virtio/Makefile.objs +3
-0@@ -10,6 +10,9 @@ obj-$(CONFIG_VIRTIO_CRYPTO) += virtio-crypto.o obj-$(call land,$(CONFIG_VIRTIO_CRYPTO),$(CONFIG_VIRTIO_PCI)) += virtio-crypto-pci.o obj-$(CONFIG_LINUX) += vhost.o vhost-backend.o vhost-user.o +ifeq ($(CONFIG_MEM_HOTPLUG),y) +obj-$(CONFIG_LINUX) += virtio-pmem.o +endif obj-$(CONFIG_VHOST_VSOCK) += vhost-vsock.o endifhw/virtio/virtio-pci.c +43
-0@@ -2521,6 +2521,49 @@ static const TypeInfo virtio_rng_pci_info = { .class_init = virtio_rng_pci_class_init, }; +/* virtio-pmem-pci */ + +static void virtio_pmem_pci_realize (VirtIOPCIProxy *vpci_dev,Error **errp) +{ +VirtIOPMEMPCI *vpmem =VIRTIO_PMEM_PCI (vpci_dev); +DeviceState *vdev =DEVICE (&vpmem->vdev); + +qdev_set_parent_bus (vdev,BUS (&vpci_dev->bus)); +object_property_set_bool (OBJECT (vdev), true,"realized" , errp); +} + +static void virtio_pmem_pci_class_init (ObjectClass *klass,void *data) +{ +DeviceClass *dc =DEVICE_CLASS (klass); +VirtioPCIClass *k =VIRTIO_PCI_CLASS (klass); +PCIDeviceClass *pcidev_k =PCI_DEVICE_CLASS (klass); + k->realize = virtio_pmem_pci_realize; +set_bit (DEVICE_CATEGORY_MISC , dc->categories); + pcidev_k->vendor_id =PCI_VENDOR_ID_REDHAT_QUMRANET ; + pcidev_k->device_id =PCI_DEVICE_ID_VIRTIO_PMEM ; + pcidev_k->revision =VIRTIO_PCI_ABI_VERSION ; + pcidev_k->class_id =PCI_CLASS_OTHERS ; +} + +static void virtio_pmem_pci_instance_init (Object *obj) +{ +VirtIOPMEMPCI *dev =VIRTIO_PMEM_PCI (obj); + +virtio_instance_init_common (obj, &dev->vdev,sizeof (dev->vdev), +TYPE_VIRTIO_PMEM ); +object_property_add_alias (obj,"memdev" ,OBJECT (&dev->vdev),"memdev" , + &error_abort); +} + +static const TypeInfo virtio_pmem_pci_info = { + .name =TYPE_VIRTIO_PMEM_PCI , + .parent =TYPE_VIRTIO_PCI , + .instance_size =sizeof (VirtIOPMEMPCI), + .instance_init = virtio_pmem_pci_instance_init, + .class_init = virtio_pmem_pci_class_init, +}; + +/* virtio-input-pci */ static Property virtio_input_pci_properties[] = {
hw/virtio/virtio-pci.c +1
-0@@ -2714,6 +2757,7 @@ static void virtio_pci_register_types(void)type_register_static (&virtio_balloon_pci_info);type_register_static (&virtio_serial_pci_info);type_register_static (&virtio_net_pci_info); +type_register_static (&virtio_pmem_pci_info);#ifdef CONFIG_VHOST_SCSI type_register_static (&vhost_scsi_pci_info);#endif hw/virtio/virtio-pci.h +14
-0@@ -19,6 +19,7 @@#include "hw/virtio/virtio-blk.h" #include "hw/virtio/virtio-net.h" #include "hw/virtio/virtio-rng.h" +#include "hw/virtio/virtio-pmem.h" #include "hw/virtio/virtio-serial.h" #include "hw/virtio/virtio-scsi.h" #include "hw/virtio/virtio-balloon.h" @@ -57,6 +58,7 @@ typedef struct VirtIOInputHostPCI VirtIOInputHostPCI;typedef struct VirtIOGPUPCI VirtIOGPUPCI ;typedef struct VHostVSockPCI VHostVSockPCI ;typedef struct VirtIOCryptoPCI VirtIOCryptoPCI ; +typedef struct VirtIOPMEMPCI VirtIOPMEMPCI ;/* virtio-pci-bus */ @@ -274,6 +276,18 @@ struct VirtIOBlkPCI {VirtIOBlock vdev; }; +/* +* virtio-pmem-pci: This extends VirtioPCIProxy. +*/ +#define TYPE_VIRTIO_PMEM_PCI "virtio-pmem-pci" +#define VIRTIO_PMEM_PCI (obj) \ + OBJECT_CHECK(VirtIOPMEMPCI, (obj), TYPE_VIRTIO_PMEM_PCI) + +struct VirtIOPMEMPCI { +VirtIOPCIProxy parent_obj; +VirtIOPMEM vdev; +}; +/* * virtio-balloon-pci: This extends VirtioPCIProxy. */ hw/virtio/virtio-pmem.c new file +37
-0@@ -0,0 +1,241 @@ +/* +* Virtio pmem device +* +* Copyright (C) 2018 Red Hat, Inc. +* Copyright (C) 2018 Pankaj Gupta <[email protected]> +* +* This work is licensed under the terms of the GNU GPL, version 2. +* See the COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" +#include "qapi/error.h" +#include "qemu-common.h" +#include "qemu/error-report.h" +#include "hw/virtio/virtio-access.h" +#include "hw/virtio/virtio-pmem.h" +#include "hw/mem/memory-device.h" +#include "block/aio.h" +#include "block/thread-pool.h" + +typedef struct VirtIOPMEMresp { +int ret; +}VirtIOPMEMResp ; + +typedef struct VirtIODeviceRequest { +VirtQueueElement elem; +int fd; +VirtIOPMEM *pmem; +VirtIOPMEMResp resp; +}VirtIODeviceRequest ; + +static int worker_cb (void *opaque) +{ +VirtIODeviceRequest *req = opaque; +int err =0 ; +Quoted 8 lines
hw/virtio/virtio-pmem.c line 43
Quoted 6 lines
hw/virtio/virtio-pmem.c new file +6
-0+/* flush raw backing image */ + err =fsync (req->fd); +if (err !=0 ) { + err = errno; + } + req->resp.ret = err;Host question: are you returning the guest errno code to the host?
Quoted 2 lines
No. I am returning error code from the host in-case of host fsync failure, otherwise returning zero.
I think that's what Luiz meant. errno constants are not portable between operating systems and architectures. Therefore they cannot be used in external interfaces in software that expects to communicate with other systems.
Quoted 6 lines
Quoted 3 lines
It will be necessary to define specific constants for virtio-pmem instead of passing errno from the host to guest.
In general, I wonder if we should report errors at all or rather *kill* the guest. That might sound harsh, but think about the following scenario:
I almost sure that I read in the nvdimm spec that real hardware will cause a memory error on sync or read/write error. If we truly want to emulate this, then I guess QEMU should be able to inject a memory error for the entire region instead of returning the fsync() error to the guest.
Quoted 3 lines
fsync()fails due to some block that cannot e.g. be written (e.g. network connection failed). What happens if our guest tries to read/write that mmaped block? (e.g. network connection failed).
I think it gets a SIGBUS? Btw, I think that QEMU already has the machinery to turn a SIGBUS into an memory error in the guest.
Quoted 4 lines
I assume we'll get a signal an get killed? So we are trying to optimize one special case (
fsync()) although every read/write is prone to kill the guest. And as soon as the guest will try to access the block that made fsync fail, we will crash the guest either way.
I think you have a point.
Quoted 19 lines
I assume the main problem is that we are trying to take a file (with all the errors that can happen during read/write/fsync) and make it look like memory (dax). On ordinary block access, we can forward errors, but not if it's memory (maybe using MCE, but it's complicated and architecture specific).
So I wonder if we should rather assume that our backend file is placed on some stable storage that cannot easily fail.
(we might have the same problem with NVDIMM right now, at least the memory reading/writing part)
It's complicated and I am not a block level expert :)
Quoted 2 lines
Stefan
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
In reply to David HildenbrandQuoted 80 lines
Quoted 59 lines
Quoted 56 lines
Quoted 47 lines
Quoted 47 lines
/*
* virtio-balloon-pci: This extends VirtioPCIProxy. */hw/virtio/virtio-pmem.c new file +37
-0@@ -0,0 +1,241 @@ +/* +* Virtio pmem device +* +* Copyright (C) 2018 Red Hat, Inc. +* Copyright (C) 2018 Pankaj Gupta <[email protected]> +* +* This work is licensed under the terms of the GNU GPL, version 2. +* See the COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" +#include "qapi/error.h" +#include "qemu-common.h" +#include "qemu/error-report.h" +#include "hw/virtio/virtio-access.h" +#include "hw/virtio/virtio-pmem.h" +#include "hw/mem/memory-device.h" +#include "block/aio.h" +#include "block/thread-pool.h" + +typedef struct VirtIOPMEMresp { +int ret; +}VirtIOPMEMResp ; + +typedef struct VirtIODeviceRequest { +VirtQueueElement elem; +int fd; +VirtIOPMEM *pmem; +VirtIOPMEMResp resp; +}VirtIODeviceRequest ; + +static int worker_cb (void *opaque) +{ +VirtIODeviceRequest *req = opaque; +int err =0 ; +Quoted 8 lines
hw/virtio/virtio-pmem.c line 43
Quoted 6 lines
hw/virtio/virtio-pmem.c new file +6
-0+/* flush raw backing image */ + err =fsync (req->fd); +if (err !=0 ) { + err = errno; + } + req->resp.ret = err;Host question: are you returning the guest errno code to the host?
Quoted 2 lines
No. I am returning error code from the host in-case of host fsync failure, otherwise returning zero.
Quoted 8 lines
I think that's what Luiz meant. errno constants are not portable between operating systems and architectures. Therefore they cannot be used in external interfaces in software that expects to communicate with other systems.
It will be necessary to define specific constants for virtio-pmem instead of passing errno from the host to guest.
In general, I wonder if we should report errors at all or rather *kill* the guest. That might sound harsh, but think about the following scenario:
fsync()fails due to some block that cannot e.g. be written (e.g. network connection failed). What happens if our guest tries to read/write that mmaped block? (e.g. network connection failed).I assume we'll get a signal an get killed? So we are trying to optimize one special case (
fsync()) although every read/write is prone to kill the guest. And as soon as the guest will try to access the block that made fsync fail, we will crash the guest either way.
Quoted 5 lines
I assume the main problem is that we are trying to take a file (with all the errors that can happen during read/write/fsync) and make it look like memory (dax). On ordinary block access, we can forward errors, but not if it's memory (maybe using MCE, but it's complicated and architecture specific).
There are two points which you highlighted:
1] Memory hardware errors:
These type of errors will be notified by MCA. If mce is non-recoverable, KVM gets SIG_BUS when hardware detects such error and injects mce in guest vCPU. If guest does not recoverable it can decide to kill the user-space process.
Default option for mce is '1':
1: panic or SIGBUS on uncorrected errors, log corrected errors
2] read/write/fsync failure because of (network connection failure):
I assume you are talking about something like NFS mount where read/write/fsync responsibility is taken care by NFS. This scenario can happen for any application accessing a network filesystem and return appropriate error or wait. Until 'fsync' is not performed there is no guarantee ram data is backed. I think its the responsibility of application to perform fsync after write operation or a transaction.
Quoted 6 lines
So I wonder if we should rather assume that our backend file is placed on some stable storage that cannot easily fail.
(we might have the same problem with NVDIMM right now, at least the memory reading/writing part)
NVDIMM NFIT handles this handler and checks if any SPA falls in the range of mce:address. It creates a list of bad blocks(corresponding to nd_region) and handle in function 'pmem_do_bvec' used by 'pmem_mem_request' & 'pmem_read_write'.
void nfit_mce_register(void)
{
mce_register_decode_chain(&nfit_mce_dec);
}In 'fake DAX', we bypass NFIT ACPI and using virtio & nvdimm_bus way of registering memory region. By default it should kill the userspace process or at worst cause guest reboot. I am thinking how we can integrate the NFIT bad block handling with mce handler approach for fake DAX. I think we can do this. But I want inputs from NVDIMM guys?
Thanks,
Pankaj
Quoted 2 lines
It's complicated and I am not a block level expert :)
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
In reply to Pankaj GuptaQuoted 204 lines · On Thu, 19 Jul 2018 01:48:13 -0400 (EDT) Pankaj Gupta…
Quoted 195 lines
Quoted 195 lines
This patch adds virtio-pmem Qemu device.
This device presents memory address range information to guest which is backed by file backend type. It acts like persistent memory device for KVM guest. Guest can perform read and persistent write operations on this memory range with the help of DAX capable filesystem.
Persistent guest writes are assured with the help of virtio based flushing interface. When guest userspace space performs fsync on file fd on pmem device, a flush command is send to Qemu over VIRTIO and host side flush/sync is done on backing image file.
Changes from RFC v2:
- Useaio_worker()to avoid Qemu from hanging with blocking fsync call - Stefan
- Use virtio_st*_p() for endianess - Stefan
- Correct indentation inqapi/misc.json- EricSigned-off-by Pankaj Gupta <[email protected]>--- hw/virtio/Makefile.objs | 3 + hw/virtio/virtio-pci.c | 44 +++++ hw/virtio/virtio-pci.h | 14 ++ hw/virtio/virtio-pmem.c | 241 ++++++++++++++++++++++++++++ include/hw/pci/pci.h | 1 + include/hw/virtio/virtio-pmem.h | 42 +++++ include/standard-headers/linux/virtio_ids.h | 1 + qapi/misc.json | 26 ++- 8 files changed, 371 insertions(+), 1 deletion(-) create mode 100644 hw/virtio/virtio-pmem.c create mode 100644 include/hw/virtio/virtio-pmem.hhw/virtio/Makefile.objs +3
-0@@ -10,6 +10,9 @@ obj-$(CONFIG_VIRTIO_CRYPTO) += virtio-crypto.o obj-$(call land,$(CONFIG_VIRTIO_CRYPTO),$(CONFIG_VIRTIO_PCI)) += virtio-crypto-pci.o obj-$(CONFIG_LINUX) += vhost.o vhost-backend.o vhost-user.o +ifeq ($(CONFIG_MEM_HOTPLUG),y) +obj-$(CONFIG_LINUX) += virtio-pmem.o +endif obj-$(CONFIG_VHOST_VSOCK) += vhost-vsock.o endifhw/virtio/virtio-pci.c +43
-0@@ -2521,6 +2521,49 @@ static const TypeInfo virtio_rng_pci_info = { .class_init = virtio_rng_pci_class_init, }; +/* virtio-pmem-pci */ + +static void virtio_pmem_pci_realize (VirtIOPCIProxy *vpci_dev,Error **errp) +{ +VirtIOPMEMPCI *vpmem =VIRTIO_PMEM_PCI (vpci_dev); +DeviceState *vdev =DEVICE (&vpmem->vdev); + +qdev_set_parent_bus (vdev,BUS (&vpci_dev->bus)); +object_property_set_bool (OBJECT (vdev), true,"realized" , errp); +} + +static void virtio_pmem_pci_class_init (ObjectClass *klass,void *data) +{ +DeviceClass *dc =DEVICE_CLASS (klass); +VirtioPCIClass *k =VIRTIO_PCI_CLASS (klass); +PCIDeviceClass *pcidev_k =PCI_DEVICE_CLASS (klass); + k->realize = virtio_pmem_pci_realize; +set_bit (DEVICE_CATEGORY_MISC , dc->categories); + pcidev_k->vendor_id =PCI_VENDOR_ID_REDHAT_QUMRANET ; + pcidev_k->device_id =PCI_DEVICE_ID_VIRTIO_PMEM ; + pcidev_k->revision =VIRTIO_PCI_ABI_VERSION ; + pcidev_k->class_id =PCI_CLASS_OTHERS ; +} + +static void virtio_pmem_pci_instance_init (Object *obj) +{ +VirtIOPMEMPCI *dev =VIRTIO_PMEM_PCI (obj); + +virtio_instance_init_common (obj, &dev->vdev,sizeof (dev->vdev), +TYPE_VIRTIO_PMEM ); +object_property_add_alias (obj,"memdev" ,OBJECT (&dev->vdev),"memdev" , + &error_abort); +} + +static const TypeInfo virtio_pmem_pci_info = { + .name =TYPE_VIRTIO_PMEM_PCI , + .parent =TYPE_VIRTIO_PCI , + .instance_size =sizeof (VirtIOPMEMPCI), + .instance_init = virtio_pmem_pci_instance_init, + .class_init = virtio_pmem_pci_class_init, +}; + +/* virtio-input-pci */ static Property virtio_input_pci_properties[] = {
hw/virtio/virtio-pci.c +1
-0@@ -2714,6 +2757,7 @@ static void virtio_pci_register_types(void)type_register_static (&virtio_balloon_pci_info);type_register_static (&virtio_serial_pci_info);type_register_static (&virtio_net_pci_info); +type_register_static (&virtio_pmem_pci_info);#ifdef CONFIG_VHOST_SCSI type_register_static (&vhost_scsi_pci_info);#endif hw/virtio/virtio-pci.h +14
-0@@ -19,6 +19,7 @@#include "hw/virtio/virtio-blk.h" #include "hw/virtio/virtio-net.h" #include "hw/virtio/virtio-rng.h" +#include "hw/virtio/virtio-pmem.h" #include "hw/virtio/virtio-serial.h" #include "hw/virtio/virtio-scsi.h" #include "hw/virtio/virtio-balloon.h" @@ -57,6 +58,7 @@ typedef struct VirtIOInputHostPCI VirtIOInputHostPCI;typedef struct VirtIOGPUPCI VirtIOGPUPCI ;typedef struct VHostVSockPCI VHostVSockPCI ;typedef struct VirtIOCryptoPCI VirtIOCryptoPCI ; +typedef struct VirtIOPMEMPCI VirtIOPMEMPCI ;/* virtio-pci-bus */ @@ -274,6 +276,18 @@ struct VirtIOBlkPCI {VirtIOBlock vdev; }; +/* +* virtio-pmem-pci: This extends VirtioPCIProxy. +*/ +#define TYPE_VIRTIO_PMEM_PCI "virtio-pmem-pci" +#define VIRTIO_PMEM_PCI (obj) \ + OBJECT_CHECK(VirtIOPMEMPCI, (obj), TYPE_VIRTIO_PMEM_PCI) + +struct VirtIOPMEMPCI { +VirtIOPCIProxy parent_obj; +VirtIOPMEM vdev; +}; +/* * virtio-balloon-pci: This extends VirtioPCIProxy. */ hw/virtio/virtio-pmem.c new file +37
-0@@ -0,0 +1,241 @@ +/* +* Virtio pmem device +* +* Copyright (C) 2018 Red Hat, Inc. +* Copyright (C) 2018 Pankaj Gupta <[email protected]> +* +* This work is licensed under the terms of the GNU GPL, version 2. +* See the COPYING file in the top-level directory. +* +*/ + +#include "qemu/osdep.h" +#include "qapi/error.h" +#include "qemu-common.h" +#include "qemu/error-report.h" +#include "hw/virtio/virtio-access.h" +#include "hw/virtio/virtio-pmem.h" +#include "hw/mem/memory-device.h" +#include "block/aio.h" +#include "block/thread-pool.h" + +typedef struct VirtIOPMEMresp { +int ret; +}VirtIOPMEMResp ; + +typedef struct VirtIODeviceRequest { +VirtQueueElement elem; +int fd; +VirtIOPMEM *pmem; +VirtIOPMEMResp resp; +}VirtIODeviceRequest ; + +static int worker_cb (void *opaque) +{ +VirtIODeviceRequest *req = opaque; +int err =0 ; +Quoted 8 lines
hw/virtio/virtio-pmem.c line 43
Quoted 6 lines
hw/virtio/virtio-pmem.c new file +6
-0+/* flush raw backing image */ + err =fsync (req->fd); +if (err !=0 ) { + err = errno; + } + req->resp.ret = err;Host question: are you returning the guest errno code to the host?
Quoted 2 lines
No. I am returning error code from the host in-case of host fsync failure, otherwise returning zero.
Sorry, that's what I meant. I exchanged host and guest but what I said still applies if you do s/host/guest
Quoted 334 lines
Thanks,
PankajQuoted 330 lines
If yes, I don't think this is right. I think you probably want to define a constant for error and let the host decide on the errno code to return to the application.
Quoted 322 lines
hw/virtio/virtio-pmem.c new file +43
-0+ +return 0 ; +} + +static void done_cb (void *opaque,int ret) +{ +VirtIODeviceRequest *req = opaque; +int len =iov_from_buf (req->elem.in_sg, req->elem.in_num,0 , + &req->resp,sizeof (VirtIOPMEMResp)); + +/* Callbacks are serialized, so no need to use atomic ops. */ +virtqueue_push (req->pmem->rq_vq, &req->elem, len); +virtio_notify ((VirtIODevice *)req->pmem, req->pmem->rq_vq); +g_free (req); +} + +static void virtio_pmem_flush (VirtIODevice *vdev,VirtQueue *vq) +{ +VirtIODeviceRequest *req; +VirtIOPMEM *pmem =VIRTIO_PMEM (vdev); +HostMemoryBackend *backend =MEMORY_BACKEND (pmem->memdev); +ThreadPool *pool =aio_get_thread_pool (qemu_get_aio_context ()); + + req =virtqueue_pop (vq,sizeof (VirtIODeviceRequest)); +if (!req) { +virtio_error (vdev,"virtio-pmem missing request data" ); +return ; + } + +if (req->elem.out_num <1 || req->elem.in_num <1 ) { +virtio_error (vdev,"virtio-pmem request not proper" ); +g_free (req); +return ; + } + req->fd =memory_region_get_fd (&backend->mr); + req->pmem = pmem; +thread_pool_submit_aio (pool, worker_cb, req, done_cb, req); +} + +static void virtio_pmem_get_config (VirtIODevice *vdev,uint8_t *config) +{ +VirtIOPMEM *pmem =VIRTIO_PMEM (vdev); + struct virtio_pmem_config *pmemcfg = (struct virtio_pmem_config *)config;
hw/virtio/virtio-pmem.c new file +6
-0+ +virtio_stq_p (vdev, &pmemcfg->start, pmem->start); +virtio_stq_p (vdev, &pmemcfg->size, pmem->size); +} + +static uint64_t virtio_pmem_get_features(VirtIODevice *vdev, uint64_tfeatures,
hw/virtio/virtio-pmem.c new file +24
-0+ Error **errp) +{ +return features; +} + +static void virtio_pmem_realize (DeviceState *dev,Error **errp) +{ +VirtIODevice *vdev =VIRTIO_DEVICE (dev); +VirtIOPMEM *pmem =VIRTIO_PMEM (dev); +MachineState *ms =MACHINE (qdev_get_machine ()); +uint64_t align; +Error *local_err =NULL ; +MemoryRegion *mr; + +if (!pmem->memdev) { +error_setg (errp,"virtio-pmem memdev not set" ); +return ; + } + + mr =host_memory_backend_get_memory (pmem->memdev); + align =memory_region_get_alignment (mr); + pmem->size =QEMU_ALIGN_DOWN (memory_region_size (mr), align); + pmem->start = memory_device_get_free_addr(ms, NULL, align, pmem->size, +
&local_err);hw/virtio/virtio-pmem.c new file +11
-0+if (local_err) { +error_setg (errp,"Can't get free address in mem device" ); +return ; + } +memory_region_init_alias (&pmem->mr,OBJECT (pmem), +"virtio_pmem-memory" , mr,0 , pmem->size); +memory_device_plug_region (ms, &pmem->mr, pmem->start); + +host_memory_backend_set_mapped (pmem->memdev, true); + virtio_init(vdev, TYPE_VIRTIO_PMEM, VIRTIO_ID_PMEM, + sizeof(struct
virtio_pmem_config));hw/virtio/virtio-pmem.c new file +4
-0+ pmem->rq_vq =virtio_add_queue (vdev,128 , virtio_pmem_flush); +} + +static void virtio_mem_check_memdev(Object *obj, const char *name, Object*val,
hw/virtio/virtio-pmem.c new file +53
-0+ Error **errp) +{ +if (host_memory_backend_is_mapped (MEMORY_BACKEND (val))) { +char *path =object_get_canonical_path_component (val); +error_setg (errp,"Can't use already busy memdev: %s" , path); +g_free (path); +return ; + } + +qdev_prop_allow_set_link_before_realize (obj, name, val, errp); +} + +static const char *virtio_pmem_get_device_id (VirtIOPMEM *vm) +{ +Object *obj =OBJECT (vm); +DeviceState *parent_dev; + +/* always use the ID of the proxy device */ +if (obj->parent &&object_dynamic_cast (obj->parent,TYPE_DEVICE )) { + parent_dev =DEVICE (obj->parent); +return parent_dev->id; + } +return NULL ; +} + +static void virtio_pmem_md_fill_device_info (const MemoryDeviceState *md, +MemoryDeviceInfo *info) +{ +VirtioPMemDeviceInfo *vi =g_new0 (VirtioPMemDeviceInfo,1 ); +VirtIOPMEM *vm =VIRTIO_PMEM (md); +const char *id =virtio_pmem_get_device_id (vm); + +if (id) { + vi->has_id = true; + vi->id =g_strdup (id); + } + + vi->start = vm->start; + vi->size = vm->size; + vi->memdev =object_get_canonical_path (OBJECT (vm->memdev)); + + info->u.virtio_pmem.data = vi; + info->type =MEMORY_DEVICE_INFO_KIND_VIRTIO_PMEM ; +} + +static uint64_t virtio_pmem_md_get_addr (const MemoryDeviceState *md) +{ +VirtIOPMEM *vm =VIRTIO_PMEM (md); + +return vm->start; +} + +static uint64_t virtio_pmem_md_get_plugged_size(const MemoryDeviceState*md)
hw/virtio/virtio-pmem.c new file +7
-0+{ +VirtIOPMEM *vm =VIRTIO_PMEM (md); + +return vm->size; +} + +static uint64_t virtio_pmem_md_get_region_size(const MemoryDeviceState*md)
hw/virtio/virtio-pmem.c new file +50
-0+{ +VirtIOPMEM *vm =VIRTIO_PMEM (md); + +return vm->size; +} + +static void virtio_pmem_instance_init (Object *obj) +{ +VirtIOPMEM *vm =VIRTIO_PMEM (obj); +object_property_add_link (obj,"memdev" ,TYPE_MEMORY_BACKEND , + (Object **)&vm->memdev, + (void *) virtio_mem_check_memdev, +OBJ_PROP_LINK_STRONG , + &error_abort); +} + + +static void virtio_pmem_class_init (ObjectClass *klass,void *data) +{ +VirtioDeviceClass *vdc =VIRTIO_DEVICE_CLASS (klass); +MemoryDeviceClass *mdc =MEMORY_DEVICE_CLASS (klass); + + vdc->realize = virtio_pmem_realize; + vdc->get_config = virtio_pmem_get_config; + vdc->get_features = virtio_pmem_get_features; + + mdc->get_addr = virtio_pmem_md_get_addr; + mdc->get_plugged_size = virtio_pmem_md_get_plugged_size; + mdc->get_region_size = virtio_pmem_md_get_region_size; + mdc->fill_device_info = virtio_pmem_md_fill_device_info; +} + +static TypeInfo virtio_pmem_info = { + .name =TYPE_VIRTIO_PMEM , + .parent =TYPE_VIRTIO_DEVICE , + .class_init = virtio_pmem_class_init, + .instance_size =sizeof (VirtIOPMEM), + .instance_init = virtio_pmem_instance_init, + .interfaces = (InterfaceInfo []) { + {TYPE_MEMORY_DEVICE }, + { } + }, +}; + +static void virtio_register_types (void ) +{ +type_register_static (&virtio_pmem_info); +} + +type_init (virtio_register_types)include/hw/pci/pci.h +1
-0@@ -85,6 +85,7 @@ extern bool pci_available;#define PCI_DEVICE_ID_VIRTIO_RNG 0x1005#define PCI_DEVICE_ID_VIRTIO_9P 0x1009#define PCI_DEVICE_ID_VIRTIO_VSOCK 0x1012 +#define PCI_DEVICE_ID_VIRTIO_PMEM 0x1013#define PCI_VENDOR_ID_REDHAT 0x1b36#define PCI_DEVICE_ID_REDHAT_BRIDGE 0x0001include/hw/virtio/virtio-pmem.h new file +42
-0@@ -0,0 +1,42 @@ +/* +* Virtio pmem Device +* +* Copyright Red Hat, Inc. 2018 +* Copyright Pankaj Gupta <[email protected]> +* +* This work is licensed under the terms of the GNU GPL, version 2 or +* (at your option) any later version. See the COPYING file in the +* top-level directory. +*/ + +#ifndef QEMU_VIRTIO_PMEM_H +#define QEMU_VIRTIO_PMEM_H + +#include "hw/virtio/virtio.h" +#include "exec/memory.h" +#include "sysemu/hostmem.h" +#include "standard-headers/linux/virtio_ids.h" +#include "hw/boards.h" +#include "hw/i386/pc.h" + +#define TYPE_VIRTIO_PMEM "virtio-pmem" + +#define VIRTIO_PMEM (obj) \ + OBJECT_CHECK(VirtIOPMEM, (obj), TYPE_VIRTIO_PMEM) + +/* VirtIOPMEM device structure */ +typedef struct VirtIOPMEM { +VirtIODevice parent_obj; + +VirtQueue *rq_vq; +uint64_t start; +uint64_t size; +MemoryRegion mr; +HostMemoryBackend *memdev; +}VirtIOPMEM ; + +struct virtio_pmem_config { +uint64_t start; +uint64_t size; +}; +#endif include/standard-headers/linux/virtio_ids.h +1
-0@@ -43,5 +43,6 @@#define VIRTIO_ID_INPUT 18/* virtio input */ #define VIRTIO_ID_VSOCK 19/* virtio vsock transport */ #define VIRTIO_ID_CRYPTO 20/* virtio crypto */ +#define VIRTIO_ID_PMEM 25/* virtio pmem */ #endif /* _LINUX_VIRTIO_IDS_H */ qapi/misc.json +25
-1@@ -2907,6 +2907,29 @@ } } +## +# @VirtioPMemDeviceInfo: +# +# VirtioPMem state information +# +# @id: device's ID +# +# @start: physical address, where device is mapped +# +# @size: size of memory that the device provides +# +# @memdev: memory backend linked with device +# +# Since: 2.13 +## +{ 'struct': 'VirtioPMemDeviceInfo', + 'data': { '*id': 'str', + 'start': 'size', + 'size': 'size', + 'memdev': 'str' + } +} + ## # @MemoryDeviceInfo: #@@ -2916,7 +2939,8 @@ ## { 'union': 'MemoryDeviceInfo', 'data': { 'dimm': 'PCDIMMDeviceInfo', - 'nvdimm': 'PCDIMMDeviceInfo' + 'nvdimm': 'PCDIMMDeviceInfo', + 'virtio-pmem': 'VirtioPMemDeviceInfo' } }
Re: [RFC v3] qemu: Add virtio pmem device
In reply to Pankaj GuptaQuoted 8 lines · Pankaj Gupta
This patch adds virtio-pmem Qemu device.
This device presents memory address range information to guest which is backed by file backend type. It acts like persistent memory device for KVM guest. Guest can perform read and persistent write operations on this memory range with the help of DAX capable filesystem.
Quoted 6 lines
Persistent guest writes are assured with the help of virtio based flushing interface. When guest userspace space performs fsync on file fd on pmem device, a flush command is send to Qemu over VIRTIO and host side flush/sync is done on backing image file.
Changes from RFC v2:
This patch has no n/M in the subject line; but is included in a thread that also has a 0/2 cover letter, as well as 1/2 and 2/2 patches in separate mails. Is that intentional?
When sending revision notes on a specific patch, it's best to place them...
Quoted 7 lines
- Use
aio_worker()to avoid Qemu from hanging with blocking fsync call - Stefan
- Use virtio_st*_p() for endianess - Stefan
- Correct indentation inqapi/misc.json- EricSigned-off-by Pankaj Gupta <[email protected]>---
...here, after the --- separator. They are useful to reviewers on the list, but are stripped by 'git am' as they don't need to be part of the git history (a year from now, we won't care how many iterations the patch went through during review, only what actually landed).
Quoted 9 lines
+++
b/qapi/misc.jsonqapi/misc.json +4
-0@@ -2907,6 +2907,29 @@ } } +## +# @VirtioPMemDeviceInfo: +# +# VirtioPMem state information
qapi/misc.json line 2923
Quoted 10 lines
qapi/misc.json +10
-0+# +# @id: device's ID +# +# @start: physical address, where device is mapped +# +# @size: size of memory that the device provides +# +# @memdev: memory backend linked with device +# +# Since: 2.13
There is no 2.13 release, and you've missed the 3.0 window. Please update this and any other version reference to 3.1.
Signature · 3 lines
Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
Hi Eric,
Quoted 15 lines · Pankaj Gupta
Quoted 13 lines
This patch adds virtio-pmem Qemu device.
This device presents memory address range information to guest which is backed by file backend type. It acts like persistent memory device for KVM guest. Guest can perform read and persistent write operations on this memory range with the help of DAX capable filesystem.
Persistent guest writes are assured with the help of virtio based flushing interface. When guest userspace space performs fsync on file fd on pmem device, a flush command is send to Qemu over VIRTIO and host side flush/sync is done on backing image file.
Quoted 5 lines
Quoted 1 line
Changes from RFC v2:
This patch has no n/M in the subject line; but is included in a thread that also has a 0/2 cover letter, as well as 1/2 and 2/2 patches in separate mails. Is that intentional?
Yes, kernel series has 0-2 patches and Qemu has this one. I thought its good to keep separate numbering for both the sets.
Quoted 2 lines
When sending revision notes on a specific patch, it's best to place them...
Sure.
Quoted 29 lines
Quoted 8 lines
- Use
aio_worker()to avoid Qemu from hanging with blocking fsync call - Stefan
- Use virtio_st*_p() for endianess - Stefan
- Correct indentation inqapi/misc.json- EricSigned-off-by Pankaj Gupta <[email protected]>---
...here, after the --- separator. They are useful to reviewers on the list, but are stripped by 'git am' as they don't need to be part of the git history (a year from now, we won't care how many iterations the patch went through during review, only what actually landed).
Quoted 14 lines
+++
b/qapi/misc.jsonqapi/misc.json +9
-0@@ -2907,6 +2907,29 @@ } } +## +# @VirtioPMemDeviceInfo: +# +# VirtioPMem state information +# +# @id: device's ID +# +# @start: physical address, where device is mapped +#
Quoted 8 lines
qapi/misc.json line 2923
Quoted 5 lines
qapi/misc.json +5
-0+# @size: size of memory that the device provides +# +# @memdev: memory backend linked with device +# +# Since: 2.13There is no 2.13 release, and you've missed the 3.0 window. Please update this and any other version reference to 3.1.
okay.
Thanks,
Pankaj
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
Quoted 7 lines · Pankaj Gupta
Quoted 4 lines
This patch has no n/M in the subject line; but is included in a thread that also has a 0/2 cover letter, as well as 1/2 and 2/2 patches in separate mails. Is that intentional?
Yes, kernel series has 0-2 patches and Qemu has this one. I thought its good to keep separate numbering for both the sets.
Ah, that makes sense. The cover letter didn't make it obvious to me that this was two separate series to two projects, but related enough that both series have to be incorporated for the feature to work and thus cross-posted under a single cover letter.
Signature · 3 lines
Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
Re: [Qemu-devel] [RFC v3] qemu: Add virtio pmem device
Quoted 9 lines
Quoted 9 lines
Quoted 8 lines
This patch has no n/M in the subject line; but is included in a thread that also has a 0/2 cover letter, as well as 1/2 and 2/2 patches in separate mails. Is that intentional?
Quoted 7 lines
Quoted 2 lines
Yes, kernel series has 0-2 patches and Qemu has this one. I thought its good to keep separate numbering for both the sets.
Ah, that makes sense. The cover letter didn't make it obvious to me that this was two separate series to two projects, but related enough that both series have to be incorporated for the feature to work and thus cross-posted under a single cover letter.
Will try to make it more clear in next posting.
Thanks,
Pankaj
Quoted 45 lines · Pankaj Gupta
This is RFC V3 for 'fake DAX' flushing interface sharing for review. This patchset has two parts:
- Guest virtio-pmem driver
Guest driver reads persistent memory range from paravirt device and registers with 'nvdimm_bus'. 'nvdimm/pmem' driver uses this information to allocate persistent memory range. Also, we have implemented guest side of VIRTIO flushing interface.- Qemu virtio-pmem device
It exposes a persistent memory range to KVM guest which at host side is file backed memory and works as persistent memory device. In addition to this it provides virtio device handling of flushing interface. KVM guest performs Qemu side asynchronous sync using this interface.Changes from RFC v2:
- Add flush function in thend_regionin place of switching on a flag - Dan & Stefan
- Add flush completion function with proper locking and wait for host side flush completion - Stefan & Dan
- Keep userspace API in uapi header file - Stefan, MST
- Use LE fields & New device id - MST
- Indentation & spacing suggestions - MST & Eric
- Remove extra header files & add licensing - StefanChanges from RFC v1:
- Reuse existing 'pmem' code for registering persistent memory and other operations instead of creating an entirely new block driver.
- Use VIRTIO driver to register memory information withnvdimm_busand createregion_typeaccordingly.
- Call VIRTIO flush from existing pmem driver.Details of project idea for 'fake DAX' flushing interface is shared [2] & [3].
Pankaj Gupta (2):
Add virtio-pmem guest driver
pmem: device flush over VIRTIO[1] https://marc.info/?l=linux-mm&m=150782346802290&w=2
[2] https://www.spinics.net/lists/kvm/msg149761.html
[3] https://www.spinics.net/lists/kvm/msg153095.html
Quoted 12 lines
drivers/nvdimm/nd.h | 1 drivers/nvdimm/pmem.c | 4 drivers/nvdimm/region_devs.c | 24 +++- drivers/virtio/Kconfig | 9 + drivers/virtio/Makefile | 1 drivers/virtio/virtio_pmem.c | 190 +++++++++++++++++++++++++++++++++++++++ include/linux/libnvdimm.h | 5 - include/linux/virtio_pmem.h | 44 +++++++++ include/uapi/linux/virtio_ids.h | 1 include/uapi/linux/virtio_pmem.h | 40 ++++++++ 10 files changed, 310 insertions(+), 9 deletions(-)
Hi Pankaj,
do you have a branch for the QEMU part somewhere available? I want to see how this works with MemoryDevice changes.
Signature · 3 lines
Thanks, David / dhildenb
Hi David,
Quoted 58 lines
Quoted 44 lines
for review. This patchset has two parts:
- Guest virtio-pmem driver
Guest driver reads persistent memory range from paravirt device and registers with 'nvdimm_bus'. 'nvdimm/pmem' driver uses this information to allocate persistent memory range. Also, we have implemented guest side of VIRTIO flushing interface.- Qemu virtio-pmem device
It exposes a persistent memory range to KVM guest which at host side is file backed memory and works as persistent memory device. In addition to this it provides virtio device handling of flushing interface. KVM guest performs Qemu side asynchronous sync using this interface.Changes from RFC v2:
- Add flush function in thend_regionin place of switching on a flag - Dan & Stefan
- Add flush completion function with proper locking and wait for host side flush completion - Stefan & Dan
- Keep userspace API in uapi header file - Stefan, MST
- Use LE fields & New device id - MST
- Indentation & spacing suggestions - MST & Eric
- Remove extra header files & add licensing - StefanChanges from RFC v1:
- Reuse existing 'pmem' code for registering persistent memory and other operations instead of creating an entirely new block driver.
- Use VIRTIO driver to register memory information withnvdimm_busand createregion_typeaccordingly.
- Call VIRTIO flush from existing pmem driver.Details of project idea for 'fake DAX' flushing interface is shared [2] & [3].
Pankaj Gupta (2):
Add virtio-pmem guest driver
pmem: device flush over VIRTIO[1] https://marc.info/?l=linux-mm&m=150782346802290&w=2
[2] https://www.spinics.net/lists/kvm/msg149761.html
[3] https://www.spinics.net/lists/kvm/msg153095.htmlQuoted 13 lines
drivers/nvdimm/nd.h | 1 drivers/nvdimm/pmem.c | 4 drivers/nvdimm/region_devs.c | 24 +++- drivers/virtio/Kconfig | 9 + drivers/virtio/Makefile | 1 drivers/virtio/virtio_pmem.c | 190 +++++++++++++++++++++++++++++++++++++++ include/linux/libnvdimm.h | 5 - include/linux/virtio_pmem.h | 44 +++++++++ include/uapi/linux/virtio_ids.h | 1 include/uapi/linux/virtio_pmem.h | 40 ++++++++ 10 files changed, 310 insertions(+), 9 deletions(-)
Quoted 4 lines
Hi Pankaj,
do you have a branch for the QEMU part somewhere available? I want to see how this works with MemoryDevice changes.
o.k I will update the guest virtio-pmem and Qemu current changes and share with you. BTW previous version is here:
https://marc.info/?l=kvm&m=153146839627143&w=2
Thanks,
Pankaj
Quoted 8 lines
--
Thanks,
David / dhildenb