From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39287) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZUH3o-0006xX-6T for qemu-devel@nongnu.org; Tue, 25 Aug 2015 12:27:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZUH3l-0005D0-Hm for qemu-devel@nongnu.org; Tue, 25 Aug 2015 12:26:56 -0400 Received: from mail-wi0-x234.google.com ([2a00:1450:400c:c05::234]:32861) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZUH3l-0005Ch-Ar for qemu-devel@nongnu.org; Tue, 25 Aug 2015 12:26:53 -0400 Received: by wicne3 with SMTP id ne3so655051wic.0 for ; Tue, 25 Aug 2015 09:26:52 -0700 (PDT) Date: Tue, 25 Aug 2015 17:26:49 +0100 From: Stefan Hajnoczi Message-ID: <20150825162649.GI8344@stefanha-thinkpad.redhat.com> References: <1439563931-12352-1-git-send-email-guangrong.xiao@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1439563931-12352-1-git-send-email-guangrong.xiao@linux.intel.com> Subject: Re: [Qemu-devel] [PATCH v2 00/18] implement vNVDIMM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Xiao Guangrong Cc: ehabkost@redhat.com, kvm@vger.kernel.org, mst@redhat.com, gleb@kernel.org, mtosatti@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com, imammedo@redhat.com, pbonzini@redhat.com, rth@twiddle.net On Fri, Aug 14, 2015 at 10:51:53PM +0800, Xiao Guangrong wrote: > Changlog: > - Use litten endian for DSM method, thanks for Stefan's suggestion > > - introduce a new parameter, @configdata, if it's false, Qemu will > build a static and readonly namespace in memory and use it serveing > for DSM GET_CONFIG_SIZE/GET_CONFIG_DATA requests. In this case, no > reserved region is needed at the end of the @file, it is good for > the user who want to pass whole nvdimm device and make its data > completely be visible to guest > > - divide the source code into separated files and add maintain info I have skipped ACPI patches because I'm not very familiar with that area. Have you thought about live migration? Are the contents of the NVDIMM migrated since they are registered as a RAM region? Stefan