Re: [Qemu-devel] [PATCH v2 00/18] implement vNVDIMM
On Wed, Oct 07, 2015 at 10:43:40PM +0800, Xiao Guangrong wrote: > > > On 10/07/2015 10:02 PM, Stefan Hajnoczi wrote: > >On Wed, Aug 26, 2015 at 06:49:35PM +0800, Xiao Guangrong wrote: > >>On 08/26/2015 12:26 AM, Stefan Hajnoczi wrote: > >>>On Fri, Aug 14, 2015 at 10:51:53PM +0800, Xiao Guangrong wrote: > >>>Have you thought about live migration? > >>> > >>>Are the contents of the NVDIMM migrated since they are registered as a > >>>RAM region? > >> > >>Will fully test live migration and VM save before sending the V3 out. :) > > > >Hi, > >What is the status of this patch series? > > This is huge change in v3, the patchset is ready now and it's being tested. > Will post it out (hopefully this week) after the long holiday in China. :) Great, thanks! Stefan -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Qemu-devel] [PATCH v2 00/18] implement vNVDIMM
On Wed, Aug 26, 2015 at 06:49:35PM +0800, Xiao Guangrong wrote: > On 08/26/2015 12:26 AM, Stefan Hajnoczi wrote: > >On Fri, Aug 14, 2015 at 10:51:53PM +0800, Xiao Guangrong wrote: > >Have you thought about live migration? > > > >Are the contents of the NVDIMM migrated since they are registered as a > >RAM region? > > Will fully test live migration and VM save before sending the V3 out. :) Hi, What is the status of this patch series? Stefan -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Qemu-devel] [PATCH v2 00/18] implement vNVDIMM
On 10/07/2015 10:02 PM, Stefan Hajnoczi wrote: On Wed, Aug 26, 2015 at 06:49:35PM +0800, Xiao Guangrong wrote: On 08/26/2015 12:26 AM, Stefan Hajnoczi wrote: On Fri, Aug 14, 2015 at 10:51:53PM +0800, Xiao Guangrong wrote: Have you thought about live migration? Are the contents of the NVDIMM migrated since they are registered as a RAM region? Will fully test live migration and VM save before sending the V3 out. :) Hi, What is the status of this patch series? This is huge change in v3, the patchset is ready now and it's being tested. Will post it out (hopefully this week) after the long holiday in China. :) -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Qemu-devel] [PATCH v2 00/18] implement vNVDIMM
On 08/26/2015 12:26 AM, Stefan Hajnoczi wrote: 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. Thank you very much for your review, your comment is great helpful to me, Stefan! Have you thought about live migration? Are the contents of the NVDIMM migrated since they are registered as a RAM region? Will fully test live migration and VM save before sending the V3 out. :) -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Qemu-devel] [PATCH v2 00/18] implement vNVDIMM
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 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
