From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>,
KVM devel mailing list <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for October 11th
Date: Tue, 11 Oct 2011 11:39:07 -0400 [thread overview]
Message-ID: <4E94631B.8000209@linux.vnet.ibm.com> (raw)
In-Reply-To: <4E944AB0.2030903@codemonkey.ws>
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
prev parent reply other threads:[~2011-10-11 15:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 11:35 [Qemu-devel] KVM call agenda for October 11th Juan Quintela
2011-10-11 11:36 ` Paolo Bonzini
2011-10-11 12:54 ` Anthony Liguori
2011-10-11 11:48 ` Avi Kivity
2011-10-11 13:01 ` Anthony Liguori
2011-10-11 13:21 ` Avi Kivity
2011-10-11 13:27 ` Anthony Liguori
2011-10-11 13:47 ` Avi Kivity
2011-10-11 13:57 ` Anthony Liguori
2011-10-11 14:01 ` Avi Kivity
2011-10-11 14:34 ` Anthony Liguori
2011-10-11 14:43 ` Avi Kivity
2011-10-11 13:27 ` Juan Quintela
2011-10-11 13:54 ` Anthony Liguori
2011-10-11 15:39 ` Stefan Berger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E94631B.8000209@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).