All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: tianren@smartx.com
Cc: qemu-devel@nongnu.org, richard.henderson@linaro.org, pbonzini@redhat.com
Subject: Re: [PATCH v2] qemu: send stop event after bdrv_flush_all
Date: Tue, 5 Dec 2023 08:14:09 +0000	[thread overview]
Message-ID: <ZW7b0SwY6SKMC6zo@redhat.com> (raw)
In-Reply-To: <20231205064826.5000-1-tianren@smartx.com>

On Tue, Dec 05, 2023 at 01:48:26AM -0500, tianren@smartx.com wrote:
> From: Tianren Zhang <tianren@smartx.com>
> 
> The stop process is not finished until bdrv_flush_all
> is done. Some users (e.g., libvirt) detect the STOP
> event and invokes some lock release logic to revoke
> the disk lock held by current qemu when such event is
> emitted. In such case, if the bdrv_flush_all is after
> the stop event, it's possible that the disk lock is
> released while the qemu is still waiting for I/O.
> Therefore, it's better to have the stop event generated
> after the whole stop process is done, so we can
> guarantee to users that the stop process is finished
> when they get the STOP event.
>
> Change-Id: Ia2f95cd55edfdeb71ee2e04005ac216cfabffa22

Please don't include this in commit messages for patches posted.
QEMU does not use Gerrit and so this is irrelevant to upstream.

> Signed-off-by: Tianren Zhang <tianren@smartx.com>
> ---
> v2: do not call runstate_is_running twice
> ---
>  system/cpus.c | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>

> 
> diff --git a/system/cpus.c b/system/cpus.c
> index a444a747f0..49af0f92b5 100644
> --- a/system/cpus.c
> +++ b/system/cpus.c
> @@ -262,21 +262,24 @@ void cpu_interrupt(CPUState *cpu, int mask)
>  static int do_vm_stop(RunState state, bool send_stop)
>  {
>      int ret = 0;
> +    bool do_send_stop = false;
>  
>      if (runstate_is_running()) {
>          runstate_set(state);
>          cpu_disable_ticks();
>          pause_all_vcpus();
>          vm_state_notify(0, state);
> -        if (send_stop) {
> -            qapi_event_send_stop();
> -        }
> +        do_send_stop = send_stop;
>      }
>  
>      bdrv_drain_all();
>      ret = bdrv_flush_all();
>      trace_vm_stop_flush_all(ret);
>  
> +    if (do_send_stop) {
> +        qapi_event_send_stop();
> +    }
> +
>      return ret;
>  }

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2023-12-05  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05  6:48 [PATCH v2] qemu: send stop event after bdrv_flush_all tianren
2023-12-05  8:14 ` Daniel P. Berrangé [this message]
2023-12-05  9:24   ` Tianren Zhang

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=ZW7b0SwY6SKMC6zo@redhat.com \
    --to=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=tianren@smartx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.