[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver
From: |
Christoph Hellwig |
Subject: |
Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver |
Date: |
Thu, 19 Oct 2017 01:01:49 -0700 |
User-agent: |
Mutt/1.8.3 (2017-05-23) |
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.
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, (continued)
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Christoph Hellwig, 2017/10/17
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Pankaj Gupta, 2017/10/17
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Christoph Hellwig, 2017/10/17
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Pankaj Gupta, 2017/10/17
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Stefan Hajnoczi, 2017/10/18
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Dan Williams, 2017/10/18
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Stefan Hajnoczi, 2017/10/19
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver,
Christoph Hellwig <=
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Dan Williams, 2017/10/19
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Christoph Hellwig, 2017/10/20
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Dan Williams, 2017/10/20
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Christoph Hellwig, 2017/10/20
- Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver, Dan Williams, 2017/10/20
[Qemu-devel] [RFC] QEMU: Add virtio pmem device, Pankaj Gupta, 2017/10/12