[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPcyv4iASygtEJrBL07ve3p4na_XvuoxV7yA0m4R1XfsyvNPJA@mail.gmail.com>
Date: Fri, 20 Oct 2017 09:11:13 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Kevin Wolf <kwolf@...hat.com>, Jan Kara <jack@...e.cz>,
xiaoguangrong eric <xiaoguangrong.eric@...il.com>,
KVM list <kvm@...r.kernel.org>,
Pankaj Gupta <pagupta@...hat.com>,
Stefan Hajnoczi <stefanha@...il.com>,
David Hildenbrand <david@...hat.com>,
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>,
linux-nvdimm <linux-nvdimm@...1.01.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Nitesh Narayan Lal <nilal@...hat.com>
Subject: Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver
On Fri, Oct 20, 2017 at 9:06 AM, Christoph Hellwig <hch@...radead.org> wrote:
> On Fri, Oct 20, 2017 at 08:05:09AM -0700, Dan Williams wrote:
>> Right, that's the same recommendation I gave.
>>
>> https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg08404.html
>>
>> ...so maybe I'm misunderstanding your concern? It sounds like we're on
>> the same page.
>
> Yes, the above is exactly what I think we should do it. And in many
> ways virtio seems overkill if we could just have a hypercall or doorbell
> page as the queueing infrastructure in virtio shouldn't really be
> needed.
Ah ok, yes, get rid of the virtio-pmem driver and just make
nvdimm_flush() do a hypercall based on region-type flag.
Powered by blists - more mailing lists