From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755211AbdJLKjz (ORCPT ); Thu, 12 Oct 2017 06:39:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39726 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752430AbdJLKjw (ORCPT ); Thu, 12 Oct 2017 06:39:52 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 98C1F3D0A Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=pagupta@redhat.com Date: Thu, 12 Oct 2017 06:39:48 -0400 (EDT) From: Pankaj Gupta To: Stefan Hajnoczi Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, qemu-devel@nongnu.org, linux-nvdimm@ml01.01.org, linux-mm@kvack.org, jack@suse.cz, dan j williams , riel@redhat.com, haozhong zhang , nilal@redhat.com, kwolf@redhat.com, pbonzini@redhat.com, ross zwisler , david@redhat.com, xiaoguangrong eric Message-ID: <1776453018.19707347.1507804788144.JavaMail.zimbra@redhat.com> In-Reply-To: <20171012085031.GA1959@stefanha-x1.localdomain> References: <20171011185146.20295-1-pagupta@redhat.com> <20171012085031.GA1959@stefanha-x1.localdomain> Subject: Re: [RFC] KVM "fake DAX" device flushing MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.65.193.47, 10.4.195.19] Thread-Topic: KVM "fake DAX" device flushing Thread-Index: Ag5TM3lg0SsWnC0lnDMSpFmKt7hJsw== X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Thu, 12 Oct 2017 10:39:52 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Thu, Oct 12, 2017 at 12:21:46AM +0530, Pankaj Gupta wrote: > > We are sharing the prototype version of 'fake DAX' flushing > > interface for the initial feedback. This is still work in progress > > and not yet ready for merging. > > > > Protoype right now just implements basic functionality without advanced > > features with two major parts: > > > > - Qemu virtio-pmem device > > It exposes a persistent memory range to KVM guest which at host side is > > file > > backed memory and works as persistent memory device. In addition to this > > it > > provides a virtio flushing interface for KVM guest to do a Qemu side sync > > for > > guest DAX persistent memory range. > > Please post a draft VIRTIO device specification. Sure! will prepare and share. Thanks, Pankaj > > The VIRTIO Technical Committee resources and mailing lists are here: > > https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=virtio#feedback > > Stefan >