[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1327760552.22648230.1524667914875.JavaMail.zimbra@redhat.com>
Date: Wed, 25 Apr 2018 10:51:54 -0400 (EDT)
From: Pankaj Gupta <pagupta@...hat.com>
To: Eric Blake <eblake@...hat.com>
Cc: qemu-devel@...gnu.org, jack@...e.cz, kvm@...r.kernel.org,
david@...hat.com, linux-nvdimm@...1.01.org,
ross zwisler <ross.zwisler@...el.com>, lcapitulino@...hat.com,
linux-mm@...ck.org, niteshnarayanlal@...mail.com, mst@...hat.com,
hch@...radead.org, marcel@...hat.com, nilal@...hat.com,
haozhong zhang <haozhong.zhang@...el.com>, famz@...hat.com,
riel@...riel.com, stefanha@...hat.com, pbonzini@...hat.com,
dan j williams <dan.j.williams@...el.com>, kwolf@...hat.com,
xiaoguangrong eric <xiaoguangrong.eric@...il.com>,
linux-kernel@...r.kernel.org, imammedo@...hat.com
Subject: Re: [Qemu-devel] [RFC v2] qemu: Add virtio pmem device
> > Hi,
> >
> > Compile failures are because Qemu 'Memory-Device changes' are not yet
> > in qemu master. As mentioned in Qemu patch message patch is
> > dependent on 'Memeory-device' patches by 'David Hildenbrand'.
>
>
> On 04/25/2018 06:24 AM, Pankaj Gupta wrote:
> > This PV device code is dependent and tested
> > with 'David Hildenbrand's ' patchset[1] to
> > map non-PCDIMM devices to guest address space.
> > There is still upstream discussion on using
> > among PCI bar vs memory device, will update
> > as per concensus.
> >
> > [1] https://marc.info/?l=qemu-devel&m=152450249319168&w=2
>
> Then let's spell that in a way that patchew understands (since patchew
> does not know how to turn marc.info references into Message-IDs):
>
> Based-on: <20180423165126.15441-1-david@...hat.com>
o.k
Thank you!
>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc. +1-919-301-3266
> Virtualization: qemu.org | libvirt.org
>
>
Powered by blists - more mailing lists