qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	 Eric Farman <farman@linux.ibm.com>
Cc: qemu-s390x@nongnu.org, Halil Pasic <pasic@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH 3/3] hw/s390x/s390-stattrib: Don't call register_savevm_live() during instance_init()
Date: Fri, 20 Oct 2023 15:27:47 +0200	[thread overview]
Message-ID: <ce07caaa-f6c0-42db-af76-f89f80db83a5@redhat.com> (raw)
In-Reply-To: <20231020125728.579747-4-thuth@redhat.com>

On 20/10/2023 14.57, Thomas Huth wrote:
> We must not call register_savevm_live() from an instance_init() function
> (since this could be called multiple times during device introspection).
> Move this to the realize() function instead.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>   hw/s390x/s390-stattrib.c | 28 ++++++++++++++--------------
>   1 file changed, 14 insertions(+), 14 deletions(-)
> 
> diff --git a/hw/s390x/s390-stattrib.c b/hw/s390x/s390-stattrib.c
> index 52f9fc036e..3217263418 100644
> --- a/hw/s390x/s390-stattrib.c
> +++ b/hw/s390x/s390-stattrib.c
> @@ -331,6 +331,17 @@ static const TypeInfo qemu_s390_stattrib_info = {
>   
>   /* Generic abstract object: */
>   
> +static SaveVMHandlers savevm_s390_stattrib_handlers = {
> +    .save_setup = cmma_save_setup,
> +    .save_live_iterate = cmma_save_iterate,
> +    .save_live_complete_precopy = cmma_save_complete,
> +    .state_pending_exact = cmma_state_pending,
> +    .state_pending_estimate = cmma_state_pending,
> +    .save_cleanup = cmma_save_cleanup,
> +    .load_state = cmma_load,
> +    .is_active = cmma_active,
> +};
> +
>   static void s390_stattrib_realize(DeviceState *dev, Error **errp)
>   {
>       bool ambiguous = false;
> @@ -339,6 +350,9 @@ static void s390_stattrib_realize(DeviceState *dev, Error **errp)
>       if (ambiguous) {
>           error_setg(errp, "storage_attributes device already exists");
>       }
> +
> +    register_savevm_live(TYPE_S390_STATTRIB, 0, 0,
> +                         &savevm_s390_stattrib_handlers, sas);
>   }

Oh, drat, I forgot to "git commit --amend" one remaining change: it should 
be "dev" instead of "sas" in above line, sorry for the confusion!

  Thomas



  reply	other threads:[~2023-10-20 13:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 12:57 [PATCH 0/3] hw/s390x: Don't call register_savevm_live() during instance_init() Thomas Huth
2023-10-20 12:57 ` [PATCH 1/3] hw/s390x/s390-skeys: " Thomas Huth
2023-10-20 12:57 ` [PATCH 2/3] hw/s390x/s390-stattrib: Simplify handling of the "migration-enabled" property Thomas Huth
2023-10-20 12:57 ` [PATCH 3/3] hw/s390x/s390-stattrib: Don't call register_savevm_live() during instance_init() Thomas Huth
2023-10-20 13:27   ` Thomas Huth [this message]
2023-10-20 13:16 ` [PATCH 0/3] hw/s390x: " David Hildenbrand
2023-10-20 14:05 ` Eric Farman

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=ce07caaa-f6c0-42db-af76-f89f80db83a5@redhat.com \
    --to=thuth@redhat.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@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).