From: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/4] hw/ppc: migrating the DRC state of hotplugged devices
Date: Wed, 3 May 2017 15:05:24 -0300 [thread overview]
Message-ID: <fc06bf7f-050b-2bd1-5184-802f36cd8ca3@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170503160916.GD2077@work-vm>
On 05/03/2017 01:09 PM, Dr. David Alan Gilbert wrote:
> * Daniel Henrique Barboza (danielhb@linux.vnet.ibm.com) wrote:
>
> <snip>
>
>> static void realize(DeviceState *d, Error **errp)
>> {
>> sPAPRDRConnector *drc = SPAPR_DR_CONNECTOR(d);
>> @@ -540,6 +598,8 @@ static void realize(DeviceState *d, Error **errp)
>> object_unref(OBJECT(drc));
>> }
>> g_free(child_name);
>> + vmstate_register(DEVICE(drc), drck->get_index(drc), &vmstate_spapr_drc,
>> + drc);
>> trace_spapr_drc_realize_complete(drck->get_index(drc));
>> }
>>
>> @@ -658,6 +718,7 @@ static void spapr_dr_connector_class_init(ObjectClass *k, void *data)
>> dk->reset = reset;
>> dk->realize = realize;
>> dk->unrealize = unrealize;
>> + dk->vmsd = &vmstate_spapr_drc;
> Are you sure this is right - isn't it unusual to have both
> a ->vmsd entry AND a vmstate_register?
I've changed the code to use vmstate_register but forgot to remove the
->vmsd entry that was being used in v6.
Thanks for pointing it out Dave. I'll fix it in v9.
Daniel
>
> a ->vmsd = is the preferable way I think, but I see you're
> doing something with the 2nd parameter of vmstate_register;
> if you *need* to do that then I think it's the only way.
>
> Dave
>
>> drck->set_isolation_state = set_isolation_state;
>> drck->set_indicator_state = set_indicator_state;
>> drck->set_allocation_state = set_allocation_state;
>> --
>> 2.9.3
>>
>>
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
next prev parent reply other threads:[~2017-05-03 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 21:22 [Qemu-devel] [PATCH 0/4 v7] migration/ppc: migrating DRC, ccs_list and pending_events Daniel Henrique Barboza
2017-04-26 21:23 ` [Qemu-devel] [PATCH 1/4] hw/ppc: setting spapr_drc_detach_cb in spapr_dr_connector_new Daniel Henrique Barboza
2017-04-26 21:23 ` [Qemu-devel] [PATCH 2/4] hw/ppc: migrating the DRC state of hotplugged devices Daniel Henrique Barboza
2017-05-03 16:09 ` Dr. David Alan Gilbert
2017-05-03 18:05 ` Daniel Henrique Barboza [this message]
2017-04-26 21:23 ` [Qemu-devel] [PATCH 3/4] migration: spapr: migrate ccs_list in spapr state Daniel Henrique Barboza
2017-04-26 21:23 ` [Qemu-devel] [PATCH 4/4] migration: spapr: migrate pending_events of " Daniel Henrique Barboza
-- strict thread matches above, loose matches on Subject: below --
2017-04-26 21:31 [Qemu-devel] [PATCH 0/4 v7] migration/ppc: migrating DRC, ccs_list and pending_events Daniel Henrique Barboza
2017-04-26 21:31 ` [Qemu-devel] [PATCH 2/4] hw/ppc: migrating the DRC state of hotplugged devices Daniel Henrique Barboza
2017-04-24 22:08 [Qemu-devel] [PATCH 0/4 v6] migration/ppc: migrating DRC, ccs_list and pending_events Daniel Henrique Barboza
2017-04-24 22:08 ` [Qemu-devel] [PATCH 2/4] hw/ppc: migrating the DRC state of hotplugged devices Daniel Henrique Barboza
2017-04-25 22:45 ` Michael Roth
2017-04-26 5:55 ` David Gibson
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=fc06bf7f-050b-2bd1-5184-802f36cd8ca3@linux.vnet.ibm.com \
--to=danielhb@linux.vnet.ibm.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.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).