[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171019080149.GB10089@infradead.org>
Date: Thu, 19 Oct 2017 01:01:49 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Stefan Hajnoczi <stefanha@...il.com>,
Pankaj Gupta <pagupta@...hat.com>,
Christoph Hellwig <hch@...radead.org>,
Kevin Wolf <kwolf@...hat.com>,
haozhong zhang <haozhong.zhang@...el.com>,
Jan Kara <jack@...e.cz>,
xiaoguangrong eric <xiaoguangrong.eric@...il.com>,
KVM list <kvm@...r.kernel.org>,
David Hildenbrand <david@...hat.com>,
linux-nvdimm <linux-nvdimm@...1.01.org>,
ross zwisler <ross.zwisler@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Qemu Developers <qemu-devel@...gnu.org>,
Linux MM <linux-mm@...ck.org>,
Stefan Hajnoczi <stefanha@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Nitesh Narayan Lal <nilal@...hat.com>
Subject: Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver
On Wed, Oct 18, 2017 at 08:51:37AM -0700, Dan Williams wrote:
> This use case is not "Persistent Memory". Persistent Memory is
> something you can map and make persistent with CPU instructions.
> Anything that requires a driver call is device driver managed "Shared
> Memory".
How is this any different than the existing nvdimm_flush()? If you
really care about the not driver thing it could easily be a write
to a doorbell page or a hypercall, but in the end that's just semantics.
Powered by blists - more mailing lists