From: Laurent Vivier <lvivier@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] runstate: ignore finishmigrate -> prelaunch transition
Date: Wed, 18 Dec 2019 17:21:17 +0100 [thread overview]
Message-ID: <e0557fa4-e5b3-3f83-e002-b22d81e7561f@redhat.com> (raw)
In-Reply-To: <b782071a-c522-0e50-ed49-152964fe6bd4@redhat.com>
Ping?
Thanks,
Laurent
On 12/12/2019 20:40, Laurent Vivier wrote:
> On 06/12/2019 20:52, Dr. David Alan Gilbert wrote:
>> * Laurent Vivier (lvivier@redhat.com) wrote:
>>> Commit 1bd71dce4bf2 tries to prevent a finishmigrate -> prelaunch
>>> transition by exiting at the beginning of the main_loop_should_exit()
>>> function if the state is already finishmigrate.
>>>
>>> As the finishmigrate state is set in the migration thread it can
>>> happen concurrently to the function. The migration thread and the
>>> function are normally protected by the iothread mutex and thus the
>>> state should no evolve between the start of the function and its end.
>>>
>>> Unfortunately during the function life the lock is released by
>>> pause_all_vcpus() just before the point we need to be sure we are
>>> not in finishmigrate state and if the migration thread is waiting
>>> for the lock it will take the opportunity to change the state
>>> to finishmigrate.
>>
>> Ewww.
>> I hate those short wakeups for pause_all_vcpus; I'm sure there are loads
>> more corners that break.
>>
>> Still, I _think_ this is an improvement, so:
>>
>> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>>
>
> Who volunteers to take this in his queue?
>
> Thanks,
> Laurent
>
>
next prev parent reply other threads:[~2019-12-18 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 11:51 [PATCH] runstate: ignore finishmigrate -> prelaunch transition Laurent Vivier
2019-12-06 19:52 ` Dr. David Alan Gilbert
2019-12-12 19:40 ` Laurent Vivier
2019-12-18 16:21 ` Laurent Vivier [this message]
2019-12-18 16:52 ` Dr. David Alan Gilbert
2020-01-08 12:39 ` Juan Quintela
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=e0557fa4-e5b3-3f83-e002-b22d81e7561f@redhat.com \
--to=lvivier@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@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).