* Re: [Qemu-devel] [PATCH v3 17/22] virtio-pmem: prototype
[not found] ` <1420151307.15516367.1537782494919.JavaMail.zimbra@redhat.com>
@ 2018-10-08 2:04 ` David Gibson
2018-10-08 3:50 ` Pankaj Gupta
0 siblings, 1 reply; 2+ messages in thread
From: David Gibson @ 2018-10-08 2:04 UTC (permalink / raw)
To: Pankaj Gupta
Cc: David Hildenbrand, Alexander Graf, Eduardo Habkost,
Michael S . Tsirkin, Markus Armbruster, Xiao Guangrong,
qemu-devel, Dr . David Alan Gilbert, qemu-ppc, Paolo Bonzini,
Igor Mammedov, Luiz Capitulino, Richard Henderson
[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]
On Mon, Sep 24, 2018 at 05:48:14AM -0400, Pankaj Gupta wrote:
>
> > On 24/09/2018 07:45, David Gibson wrote:
> > > On Thu, Sep 20, 2018 at 12:32:38PM +0200, David Hildenbrand wrote:
> > >> From: Pankaj Gupta <pagupta@redhat.com>
> > >>
> > >> 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.
> > >>
> > >> Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
> > >> [ MemoryDevice/MemoryRegion changes, cleanups, addr property "memaddr",
> > >> split up patches ]
> > >> Signed-off-by: David Hildenbrand <david@redhat.com>
> > >
> > > Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> > >
> > > Seems generally sane. Is there a (craft?) virtio-pmem spec around to
> > > see what this is actually trying to implement?
> >
> > I am not aware of any. The first goal is to get something implemented
> > that works and doesn't break important concepts. E.g. hotplugging memory
> > devices was one of these concepts that Igor saw as a potential problem
> > for getting virtio-pmem upstream.
> >
> > But maybe Pankaj already has some draft version of a spec lying around.
>
> I have created document but no official spec. Project idea is shared here [1]
> and kernel part of series [2]. I will create a spec and share.
>
> [1] https://www.spinics.net/lists/kvm/msg153095.html
> [2] https://marc.info/?l=kvm&m=153572224719212&w=2
Ok. Because this creates a new interface we could be working with for
a while, I think we do need at least a semi-formal spec - and to get
some review of that spec - before we merge.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] [PATCH v3 17/22] virtio-pmem: prototype
2018-10-08 2:04 ` [Qemu-devel] [PATCH v3 17/22] virtio-pmem: prototype David Gibson
@ 2018-10-08 3:50 ` Pankaj Gupta
0 siblings, 0 replies; 2+ messages in thread
From: Pankaj Gupta @ 2018-10-08 3:50 UTC (permalink / raw)
To: David Gibson
Cc: Xiao Guangrong, Michael S . Tsirkin, qemu-devel,
David Hildenbrand, Markus Armbruster, Alexander Graf, qemu-ppc,
Igor Mammedov, Paolo Bonzini, Luiz Capitulino, Richard Henderson,
Dr . David Alan Gilbert, Eduardo Habkost
Hello David,
Thanks for the review.
> >
> > > On 24/09/2018 07:45, David Gibson wrote:
> > > > On Thu, Sep 20, 2018 at 12:32:38PM +0200, David Hildenbrand wrote:
> > > >> From: Pankaj Gupta <pagupta@redhat.com>
> > > >>
> > > >> 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.
> > > >>
> > > >> Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
> > > >> [ MemoryDevice/MemoryRegion changes, cleanups, addr property
> > > >> "memaddr",
> > > >> split up patches ]
> > > >> Signed-off-by: David Hildenbrand <david@redhat.com>
> > > >
> > > > Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> > > >
> > > > Seems generally sane. Is there a (craft?) virtio-pmem spec around to
> > > > see what this is actually trying to implement?
> > >
> > > I am not aware of any. The first goal is to get something implemented
> > > that works and doesn't break important concepts. E.g. hotplugging memory
> > > devices was one of these concepts that Igor saw as a potential problem
> > > for getting virtio-pmem upstream.
> > >
> > > But maybe Pankaj already has some draft version of a spec lying around.
> >
> > I have created document but no official spec. Project idea is shared here
> > [1]
> > and kernel part of series [2]. I will create a spec and share.
> >
> > [1] https://www.spinics.net/lists/kvm/msg153095.html
> > [2] https://marc.info/?l=kvm&m=153572224719212&w=2
>
> Ok. Because this creates a new interface we could be working with for
> a while, I think we do need at least a semi-formal spec - and to get
> some review of that spec - before we merge.
Sure, Will create one and try to send for review this week.
Thanks,
Pankaj
>
> --
> David Gibson | I'll have my music baroque, and my code
> david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
> | _way_ _around_!
> http://www.ozlabs.org/~dgibson
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-10-08 3:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20180920103243.28474-1-david@redhat.com>
[not found] ` <20180920103243.28474-18-david@redhat.com>
[not found] ` <20180924054522.GY30868@umbus.fritz.box>
[not found] ` <bff1cdbc-8a7c-8d53-47ff-cf17120a4af5@redhat.com>
[not found] ` <1420151307.15516367.1537782494919.JavaMail.zimbra@redhat.com>
2018-10-08 2:04 ` [Qemu-devel] [PATCH v3 17/22] virtio-pmem: prototype David Gibson
2018-10-08 3:50 ` Pankaj Gupta
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).