[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [qemu-s390x] [PATCH RFC 04/10] virtio-pmem: Prototype
|
From: |
Dr. David Alan Gilbert |
|
Subject: |
Re: [qemu-s390x] [PATCH RFC 04/10] virtio-pmem: Prototype |
|
Date: |
Mon, 21 Jan 2019 12:02:53 +0000 |
|
User-agent: |
Mutt/1.10.1 (2018-07-13) |
* David Hildenbrand (address@hidden) wrote:
> On 16.01.19 15:46, Eric Blake wrote:
> > On 1/16/19 5:35 AM, David Hildenbrand wrote:
> >> From: Pankaj Gupta <address@hidden>
> >>
> >> This is the current protoype of virtio-pmem. Support will require
> >> machine changes for the architectures that will support it, so it will
> >> not yet be compiled.
> >>
> >> TODO:
> >> - Use separate struct for tracking requests internally
> >> - Move request/response structs to linux headers
> >> - Factor out linux header sync
> >> - Drop debug printfs
> >>
> >> Signed-off-by: Pankaj Gupta <address@hidden>
> >> [ MemoryDevice/MemoryRegion changes, cleanups, addr property "memaddr",
> >> split up patches, unplug handler ]
> >> Signed-off-by: David Hildenbrand <address@hidden>
> >> ---
> >
> >> +++ b/qapi/misc.json
> >> @@ -2949,6 +2949,29 @@
> >> }
> >> }
> >>
> >> +##
> >> +# @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: 3.1
> >
> > Now 4.0
> >
> >> +##
> >> +{ 'struct': 'VirtioPMEMDeviceInfo',
> >> + 'data': { '*id': 'str',
> >> + 'memaddr': 'size',
> >> + 'size': 'size',
> >> + 'memdev': 'str'
> >> + }
> >> +}
> >> +
> >> ##
> >> # @MemoryDeviceInfo:
> >> #
> >> @@ -2958,7 +2981,8 @@
> >> ##
> >> { 'union': 'MemoryDeviceInfo',
> >
> > Does this union need a documentation update that virtio-pmem was added
> > in 4.0?
>
> Seems like:
>
> ##
> # @MemoryDeviceInfo:
> #
> # Union containing information about a memory device
> #
> # @dimm: Information about a pc-dimm device.
> #
> # @nvdimm: Information about a nvdimm device. (since 2.12)
> #
> # @virtio-pmem: Information about a virtio-pmem device. (since 4.0)
> #
> # Since: 2.1
> ##
>
> Does not work.
>
> In file included from /home/dhildenb/git/qemu/qapi/qapi-schema.json:97:
> /home/dhildenb/git/qemu/qapi/misc.json:2975: The following documented
> members are not in the declaration: dimm, nvdimm, virtio-pmem
>
> Any idea how to document this correctly?
No I don't, but looking at other Union's they only ever seem to document
the base members, not the data members, for example see CpuInfo.
Dave
> --
>
> Thanks,
>
> David / dhildenb
--
Dr. David Alan Gilbert / address@hidden / Manchester, UK
- Re: [qemu-s390x] [PATCH RFC 01/10] qdev: Let the hotplug_handler_unplug() caller delete the device, (continued)
- [qemu-s390x] [PATCH RFC 05/10] virtio-pci: Allow to specify additional interfaces for the base type, David Hildenbrand, 2019/01/16
- [qemu-s390x] [PATCH RFC 02/10] qdev: Let machine hotplug handler to override bus hotplug handler, David Hildenbrand, 2019/01/16
- [qemu-s390x] [PATCH RFC 10/10] pc: Enable support for virtio-pmem, David Hildenbrand, 2019/01/16
- [qemu-s390x] [PATCH RFC 07/10] hmp: Handle virtio-pmem when printing memory device infos, David Hildenbrand, 2019/01/16
- [qemu-s390x] [PATCH RFC 08/10] numa: Handle virtio-pmem in NUMA stats, David Hildenbrand, 2019/01/16
- [qemu-s390x] [PATCH RFC 04/10] virtio-pmem: Prototype, David Hildenbrand, 2019/01/16
Re: [qemu-s390x] [Qemu-ppc] [PATCH RFC 04/10] virtio-pmem: Prototype, Murilo Opsfelder Araujo, 2019/01/16
[qemu-s390x] [PATCH RFC 09/10] pc: Support for PCI based memory devices, David Hildenbrand, 2019/01/16
[qemu-s390x] [PATCH RFC 03/10] qdev: Provide qdev_get_bus_hotplug_handler(), David Hildenbrand, 2019/01/16