From: Cornelia Huck <cohuck@redhat.com>
To: Pankaj Gupta <pagupta@redhat.com>
Cc: kwolf@redhat.com, aarcange@redhat.com,
xiaoguangrong.eric@gmail.com, mst@redhat.com, armbru@redhat.com,
riel@surriel.com, david@redhat.com, qemu-devel@nongnu.org,
ehabkost@redhat.com, lcapitulino@redhat.com, stefanha@redhat.com,
pbonzini@redhat.com, imammedo@redhat.com,
dan.j.williams@intel.com, nilal@redhat.com, dgilbert@redhat.com,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v2 1/7] virtio-pmem: add virtio device
Date: Tue, 2 Jul 2019 13:46:53 +0200 [thread overview]
Message-ID: <20190702134653.1a529826.cohuck@redhat.com> (raw)
In-Reply-To: <20190619094907.10131-2-pagupta@redhat.com>
On Wed, 19 Jun 2019 15:19:01 +0530
Pankaj Gupta <pagupta@redhat.com> wrote:
> This is the implementation of virtio-pmem device. Support will require
> machine changes for the architectures that will support it, so it will
> not yet be compiled. It can be unlocked with VIRTIO_PMEM_SUPPORTED per
> machine and disabled globally via VIRTIO_PMEM.
>
> We cannot use the "addr" property as that is already used e.g. for
> virtio-pci/pci devices. And we will have e.g. virtio-pmem-pci as a proxy.
> So we have to choose a different one (unfortunately). "memaddr" it is.
> That name should ideally be used by all other virtio-* based memory
> devices in the future.
> -device virtio-pmem-pci,id=p0,bus=bux0,addr=0x01,memaddr=0x1000000...
>
> Acked-by: Markus Armbruster <armbru@redhat.com>
> [ QAPI bits ]
> Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
> [ MemoryDevice/MemoryRegion changes, cleanups, addr property "memaddr",
> split up patches, unplug handler ]
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> hw/virtio/Kconfig | 10 +++
> hw/virtio/Makefile.objs | 1 +
> hw/virtio/virtio-pmem.c | 189 ++++++++++++++++++++++++++++++++++++++++
> include/hw/virtio/virtio-pmem.h | 49 +++++++++++
> qapi/misc.json | 28 +++++-
> 5 files changed, 276 insertions(+), 1 deletion(-)
> create mode 100644 hw/virtio/virtio-pmem.c
> create mode 100644 include/hw/virtio/virtio-pmem.h
>
> diff --git a/qapi/misc.json b/qapi/misc.json
> index dc4cf9da20..6f1bff10e4 100644
> --- a/qapi/misc.json
> +++ b/qapi/misc.json
> @@ -2738,16 +2738,42 @@
> }
> }
>
> +##
> +# @VirtioPMEMDeviceInfo:
> +#
> +# VirtioPMEM state information
> +#
> +# @id: device's ID
> +#
> +# @memaddr: physical address in memory, where device is mapped
> +#
> +# @size: size of memory that the device provides
> +#
> +# @memdev: memory backend linked with device
> +#
> +# Since: 4.1
Not sure if this can still make it...
> +##
> +{ 'struct': 'VirtioPMEMDeviceInfo',
> + 'data': { '*id': 'str',
> + 'memaddr': 'size',
> + 'size': 'size',
> + 'memdev': 'str'
> + }
> +}
> +
> ##
> # @MemoryDeviceInfo:
> #
> # Union containing information about a memory device
> #
> +# nvdimm is included since 2.12. virtio-pmem is included since 4.1.
> +#
> # Since: 2.1
> ##
> { 'union': 'MemoryDeviceInfo',
> 'data': { 'dimm': 'PCDIMMDeviceInfo',
> - 'nvdimm': 'PCDIMMDeviceInfo'
> + 'nvdimm': 'PCDIMMDeviceInfo',
> + 'virtio-pmem': 'VirtioPMEMDeviceInfo'
> }
> }
>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2019-07-02 11:52 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 9:49 [Qemu-devel] [PATCH v2 0/7] Qemu virtio pmem device Pankaj Gupta
2019-06-19 9:49 ` [Qemu-devel] [PATCH v2 1/7] virtio-pmem: add virtio device Pankaj Gupta
2019-07-02 11:46 ` Cornelia Huck [this message]
2019-07-02 15:07 ` [Qemu-devel] [PULL 05/22] " Michael S. Tsirkin
2019-07-11 12:57 ` Peter Maydell
2019-07-11 14:05 ` Pankaj Gupta
2019-06-19 9:49 ` [Qemu-devel] [PATCH v2 2/7] virtio-pci: Allow to specify additional interfaces for the base type Pankaj Gupta
2019-07-02 15:07 ` [Qemu-devel] [PULL 06/22] " Michael S. Tsirkin
2019-06-19 9:49 ` [Qemu-devel] [PATCH v2 3/7] virtio-pmem: sync linux headers Pankaj Gupta
2019-07-02 11:50 ` Cornelia Huck
2019-07-02 11:59 ` Pankaj Gupta
2019-07-02 16:58 ` Michael S. Tsirkin
2019-07-02 17:09 ` Pankaj Gupta
2019-07-02 17:11 ` Michael S. Tsirkin
2019-07-02 17:21 ` Pankaj Gupta
2019-07-02 15:10 ` Michael S. Tsirkin
2019-07-02 15:07 ` [Qemu-devel] [PULL 07/22] " Michael S. Tsirkin
2019-06-19 9:49 ` [Qemu-devel] [PATCH v2 4/7] virtio-pci: Proxy for virtio-pmem Pankaj Gupta
2019-07-02 11:55 ` Cornelia Huck
2019-07-02 12:00 ` Pankaj Gupta
2019-07-02 17:09 ` Michael S. Tsirkin
2019-07-02 17:14 ` Pankaj Gupta
2019-07-02 15:07 ` [Qemu-devel] [PULL 08/22] " Michael S. Tsirkin
2019-07-11 12:59 ` Peter Maydell
2019-07-11 13:27 ` Pankaj Gupta
2019-06-19 9:49 ` [Qemu-devel] [PATCH v2 5/7] hmp: Handle virtio-pmem when printing memory device infos Pankaj Gupta
2019-07-02 8:50 ` Wei Yang
2019-07-02 10:17 ` Pankaj Gupta
2019-07-02 15:07 ` [Qemu-devel] [PULL 09/22] " Michael S. Tsirkin
2019-06-19 9:49 ` [Qemu-devel] [PATCH v2 6/7] numa: Handle virtio-pmem in NUMA stats Pankaj Gupta
2019-07-02 15:07 ` [Qemu-devel] [PULL 10/22] " Michael S. Tsirkin
2019-06-19 9:49 ` [Qemu-devel] [PATCH v2 7/7] pc: Support for virtio-pmem-pci Pankaj Gupta
2019-07-02 15:07 ` [Qemu-devel] [PULL 11/22] " Michael S. Tsirkin
2019-07-01 3:53 ` [Qemu-devel] [PATCH v2 0/7] Qemu virtio pmem device Pankaj Gupta
2019-07-02 8:49 ` Wei Yang
2019-07-02 10:07 ` Pankaj Gupta
2019-07-03 0:58 ` Wei Yang
2019-07-03 1:31 ` Pankaj Gupta
2019-07-03 1:57 ` Wei Yang
2019-07-03 2:31 ` Pankaj Gupta
2019-07-03 2:42 ` Wei Yang
2019-07-03 3:21 ` Pankaj Gupta
2019-06-26 2:31 [Qemu-devel] [PATCH v4 0/5] virtio: fix some issues of "started" and "start_on_kick" flag elohimes
2019-06-26 2:31 ` [Qemu-devel] [PATCH v4 1/5] virtio: add "use-started" property elohimes
2019-06-26 10:17 ` Greg Kurz
2019-06-27 2:20 ` Yongji Xie
2019-07-02 15:07 ` [Qemu-devel] [PULL 13/22] " Michael S. Tsirkin
2019-06-26 2:31 ` [Qemu-devel] [PATCH v4 2/5] virtio: Set "start_on_kick" for legacy devices elohimes
2019-07-02 15:07 ` [Qemu-devel] [PULL 14/22] " Michael S. Tsirkin
2019-06-26 2:31 ` [Qemu-devel] [PATCH v4 3/5] virtio: Set "start_on_kick" on virtio_set_features() elohimes
2019-07-02 15:08 ` [Qemu-devel] [PULL 15/22] " Michael S. Tsirkin
2019-06-26 2:31 ` [Qemu-devel] [PATCH v4 4/5] virtio: Make sure we get correct state of device on handle_aio_output() elohimes
2019-07-02 15:08 ` [Qemu-devel] [PULL 16/22] " Michael S. Tsirkin
2019-06-26 2:31 ` [Qemu-devel] [PATCH v4 5/5] virtio: Don't change "started" flag on virtio_vmstate_change() elohimes
2019-07-02 15:08 ` [Qemu-devel] [PULL 17/22] " Michael S. Tsirkin
2019-06-26 10:43 ` [Qemu-devel] [PATCH v4 0/5] virtio: fix some issues of "started" and "start_on_kick" flag Laurent Vivier
2019-06-27 2:19 ` Yongji Xie
2019-06-26 7:48 [Qemu-devel] [PATCH v2 0/4] libvhost-user: VHOST_USER_PROTOCOL_F_MQ support Stefan Hajnoczi
2019-06-26 7:48 ` [Qemu-devel] [PATCH v2 1/4] libvhost-user: add vmsg_set_reply_u64() helper Stefan Hajnoczi
2019-07-02 15:08 ` [Qemu-devel] [PULL 19/22] " Michael S. Tsirkin
2019-06-26 7:48 ` [Qemu-devel] [PATCH v2 2/4] libvhost-user: support many virtqueues Stefan Hajnoczi
2019-07-02 15:08 ` [Qemu-devel] [PULL 20/22] " Michael S. Tsirkin
2019-06-26 7:48 ` [Qemu-devel] [PATCH v2 3/4] libvhost-user: implement VHOST_USER_PROTOCOL_F_MQ Stefan Hajnoczi
2019-07-02 15:08 ` [Qemu-devel] [PULL 21/22] " Michael S. Tsirkin
2019-06-26 7:48 ` [Qemu-devel] [PATCH v2 4/4] docs: avoid vhost-user-net specifics in multiqueue section Stefan Hajnoczi
2019-07-02 15:08 ` [Qemu-devel] [PULL 22/22] " Michael S. Tsirkin
2019-07-02 15:06 [Qemu-devel] [PULL 00/22] virtio, pc, pci: features, fixes, cleanups Michael S. Tsirkin
2019-06-25 23:23 ` [Qemu-devel] [PATCH] virtio-pci: fix missing device properties Marc-André Lureau
2019-06-26 1:55 ` Eduardo Habkost
2019-06-26 9:48 ` Marc-André Lureau
2019-06-26 12:39 ` Eduardo Habkost
2019-07-02 15:07 ` [Qemu-devel] [PULL 12/22] " Michael S. Tsirkin
2019-06-28 20:02 ` [Qemu-devel] [PATCH] pc: Move compat_apic_id_mode variable to PCMachineClass Eduardo Habkost
2019-06-29 10:46 ` Philippe Mathieu-Daudé
2019-06-30 21:30 ` Michael S. Tsirkin
2019-07-02 15:08 ` [Qemu-devel] [PULL 18/22] " Michael S. Tsirkin
2019-07-02 15:06 ` [Qemu-devel] [PULL 01/22] pcie: don't skip multi-mask events Michael S. Tsirkin
2019-07-02 15:06 ` [Qemu-devel] [PULL 02/22] pcie: check that slt ctrl changed before deleting Michael S. Tsirkin
2019-07-11 12:31 ` Peter Maydell
2019-07-02 15:06 ` [Qemu-devel] [PULL 03/22] pcie: work around for racy guest init Michael S. Tsirkin
2019-07-02 15:06 ` [Qemu-devel] [PULL 04/22] pcie: minor cleanups for slot control/status Michael S. Tsirkin
2019-07-02 15:56 ` [Qemu-devel] [PULL 00/22] virtio, pc, pci: features, fixes, cleanups Peter Maydell
2019-07-02 17:00 ` Michael S. Tsirkin
2019-07-02 17:20 ` Peter Maydell
2019-07-02 18:22 ` Michael S. Tsirkin
2019-07-02 18:27 ` Peter Maydell
2019-07-02 19:00 ` Michael S. Tsirkin
2019-07-26 12:39 ` Peter Maydell
2019-07-26 13:43 ` Michael S. Tsirkin
2019-07-04 9:25 ` Peter Maydell
2019-07-04 11:03 ` Pankaj Gupta
2019-07-04 21:24 ` Michael S. Tsirkin
2019-07-05 9:37 ` Pankaj Gupta
2019-07-04 21:29 ` Michael S. Tsirkin
2019-07-05 9:47 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190702134653.1a529826.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=aarcange@redhat.com \
--cc=armbru@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=nilal@redhat.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riel@surriel.com \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.com \
--cc=xiaoguangrong.eric@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).