From: Blue Swirl <blauwirbel@gmail.com>
To: Juan Quintela <quintela@trasno.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 1/4] qdev: integrate reset
Date: Tue, 1 Sep 2009 19:45:53 +0300 [thread overview]
Message-ID: <f43fc5580909010945s233eb655pbc24ad695306da31@mail.gmail.com> (raw)
In-Reply-To: <m33a76mxkc.fsf@neno.mitica>
On Tue, Sep 1, 2009 at 7:36 PM, Juan Quintela<quintela@trasno.org> wrote:
> Blue Swirl <blauwirbel@gmail.com> wrote:
>> On Tue, Sep 1, 2009 at 10:56 AM, Gerd Hoffmann<kraxel@redhat.com> wrote:
>>
>>> @@ -110,6 +110,9 @@ struct DeviceInfo {
>>> Property *props;
>>> int no_user;
>>>
>>> + /* callbacks */
>>> + QEMUResetHandler *reset;
>>> +
>>
>> This would remove the need for registration but I had in my mind a bit
>> more complex solution like VMState structures. Even better, VMState
>> could be enhanced so that the reset value of the fields could be
>> specified (when not zero).
>
> That soonds nice, but ... not every field in the structures are used
> during migration. Do we want to merge both things?
New flags that tell whether a VMState field is used for savevm or reset?
next prev parent reply other threads:[~2009-09-01 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 7:56 [Qemu-devel] [PATCH 0/4] integrate more device handling bits with qdev Gerd Hoffmann
2009-09-01 7:56 ` [Qemu-devel] [PATCH 1/4] qdev: integrate reset Gerd Hoffmann
2009-09-01 16:30 ` Blue Swirl
[not found] ` <m33a76mxkc.fsf@neno.mitica>
2009-09-01 16:45 ` Blue Swirl [this message]
2009-09-02 6:43 ` Gerd Hoffmann
2009-09-01 7:56 ` [Qemu-devel] [PATCH 2/4] qdev: convert rtl8139 to reset Gerd Hoffmann
2009-09-01 7:56 ` [Qemu-devel] [PATCH 3/4] qdev: integrate vmstate Gerd Hoffmann
2009-09-01 7:56 ` [Qemu-devel] [PATCH 4/4] qdev: convert tcx to reset + vmsd Gerd Hoffmann
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=f43fc5580909010945s233eb655pbc24ad695306da31@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.org \
/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).