From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33562) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDeQW-0005xl-Tq for qemu-devel@nongnu.org; Tue, 11 Oct 2011 11:39:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RDeQW-0006kb-21 for qemu-devel@nongnu.org; Tue, 11 Oct 2011 11:39:32 -0400 Received: from e6.ny.us.ibm.com ([32.97.182.146]:34018) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDeQV-0006kD-V9 for qemu-devel@nongnu.org; Tue, 11 Oct 2011 11:39:32 -0400 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e6.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p9BFFFpT007795 for ; Tue, 11 Oct 2011 11:15:15 -0400 Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p9BFdNuP207616 for ; Tue, 11 Oct 2011 11:39:24 -0400 Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p9BFdLr4018697 for ; Tue, 11 Oct 2011 09:39:22 -0600 Message-ID: <4E94631B.8000209@linux.vnet.ibm.com> Date: Tue, 11 Oct 2011 11:39:07 -0400 From: Stefan Berger MIME-Version: 1.0 References: <4E942CFA.5040403@redhat.com> <4E944AB0.2030903@codemonkey.ws> In-Reply-To: <4E944AB0.2030903@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] KVM call agenda for October 11th List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org, Avi Kivity , KVM devel mailing list , quintela@redhat.com On 10/11/2011 09:54 AM, Anthony Liguori wrote: > On 10/11/2011 08:27 AM, Juan Quintela wrote: > > I've been thinking about it this morning. I think it's solvable. We > need to be able to save off the qdev construction properties right > before init. This is just a matter of storing a list of strings. > Then we need a qdev_torture function that will save the device state > (will require a dummy QEMUFile that saves to memory). We then need to > invoke destruction w/o actually freeing the memory of the device. We > should then zero out the device memory. > > We then need to run through qdev creation, setting properties based on > the saved construction properties. Then we should init and invoke the > device's reset function. Finally we can pass the dummy QEMUFile to > the device's load function (or vmstate). If you want, I have a 'dummy QEMUFile' implementation... Stefan