From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EE77FC5B57D for ; Wed, 3 Jul 2019 02:43:39 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id BC0B821721 for ; Wed, 3 Jul 2019 02:43:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BC0B821721 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:58852 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hiVFC-00021E-VF for qemu-devel@archiver.kernel.org; Tue, 02 Jul 2019 22:43:38 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:58584) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hiVEP-0001cS-8V for qemu-devel@nongnu.org; Tue, 02 Jul 2019 22:42:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hiVEO-0003WW-Cm for qemu-devel@nongnu.org; Tue, 02 Jul 2019 22:42:49 -0400 Received: from mga05.intel.com ([192.55.52.43]:64616) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hiVEO-0003Tj-4H for qemu-devel@nongnu.org; Tue, 02 Jul 2019 22:42:48 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jul 2019 19:42:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.63,445,1557212400"; d="scan'208";a="247480765" Received: from richard.sh.intel.com (HELO localhost) ([10.239.159.54]) by orsmga001.jf.intel.com with ESMTP; 02 Jul 2019 19:42:40 -0700 Date: Wed, 3 Jul 2019 10:42:19 +0800 From: Wei Yang To: Pankaj Gupta Message-ID: <20190703024219.GA4444@richard> References: <20190619094907.10131-1-pagupta@redhat.com> <20190702084934.GA25987@richard> <1872807933.38582516.1562062064161.JavaMail.zimbra@redhat.com> <20190703005836.GA18621@richard> <1866293380.38744564.1562117503276.JavaMail.zimbra@redhat.com> <20190703015718.GA3752@richard> <1195441475.38747365.1562121061024.JavaMail.zimbra@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1195441475.38747365.1562121061024.JavaMail.zimbra@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 192.55.52.43 Subject: Re: [Qemu-devel] [PATCH v2 0/7] Qemu virtio pmem device X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Wei Yang Cc: kwolf@redhat.com, aarcange@redhat.com, xiaoguangrong eric , mst@redhat.com, cohuck@redhat.com, david@redhat.com, qemu-devel@nongnu.org, ehabkost@redhat.com, armbru@redhat.com, Wei Yang , stefanha@redhat.com, pbonzini@redhat.com, lcapitulino@redhat.com, imammedo@redhat.com, riel@surriel.com, nilal@redhat.com, dan j williams , dgilbert@redhat.com, rth@twiddle.net Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Tue, Jul 02, 2019 at 10:31:01PM -0400, Pankaj Gupta wrote: > > >> >> Ok, if it works, we could list those regions? and change pmem0 mode to dax >> mode, right? > >You mean fs dax? >I don't think currently we support this because raw image wont have any metadata. >Will have to think if this is at all possible or how we can achieve such behavior. > Ok, I got it. >Also, there is requirement to support host backing file on real NVDIMM and >virtio. Once we have have first version of virtio pmem series merged upstream >we will continue to work on advance features depending upon feasibility. > One curiosity, what difference make NVDIMM backend doesn't work now? The /dev/dax0.0 is a char file. The nvdimm device use mmap to map HVA to HPA. It looks a normal file to me. Would appreciated it if you would share some light on it. >Thanks, >Pankaj > > -- Wei Yang Help you, Help me