qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Longpeng (Mike,
	Cloud Infrastructure Service Product Dept.)"
	<longpeng2@huawei.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"qemu-devel @ nongnu . org" <qemu-devel@nongnu.org>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	arei.gonglei@huawei.com, huangzhichao@huawei.com,
	rth@twiddle.net
Subject: Re: [RFC] cpus: avoid get stuck in pause_all_vcpus
Date: Fri, 13 Mar 2020 10:22:50 +0100	[thread overview]
Message-ID: <0b380490-dafc-39ef-1bf7-d3f4e54c14ad@redhat.com> (raw)
In-Reply-To: <e7a49ec8-6a71-78a9-05c6-f6967e1d55f2@huawei.com>

On 13/03/20 09:36, Longpeng (Mike, Cloud Infrastructure Service Product
Dept.) wrote:
>> You're right, do_vm_stop sets the runstate after pause_all_vcpus.  We
>> can move that before and it should fix your case too.
>>
> Uh, it seems to work. So can I send a patch based on your suggestion ? Or feel
> free to do if you want to fix it by yourself.
> 

Yes, please.

Paolo



  reply	other threads:[~2020-03-13  9:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10  9:14 [RFC] cpus: avoid get stuck in pause_all_vcpus Longpeng(Mike)
2020-03-10 10:20 ` no-reply
2020-03-10 12:09   ` Longpeng (Mike)
2020-03-12 15:28 ` Paolo Bonzini
2020-03-13  1:43   ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2020-03-13  7:09     ` Paolo Bonzini
2020-03-13  8:36       ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2020-03-13  9:22         ` Paolo Bonzini [this message]
2020-03-13  9:41           ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)

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=0b380490-dafc-39ef-1bf7-d3f4e54c14ad@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=dgilbert@redhat.com \
    --cc=huangzhichao@huawei.com \
    --cc=longpeng2@huawei.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).