From: Paolo Bonzini <pbonzini@redhat.com>
To: Pavel Dovgalyuk <Pavel.Dovgaluk@gmail.com>, qemu-devel@nongnu.org
Cc: dovgaluk@ispras.ru, pavel.dovgaluk@ispras.ru
Subject: Re: [PATCH] replay: implement fair mutex
Date: Thu, 30 Apr 2020 11:30:22 +0200 [thread overview]
Message-ID: <564674ea-77a8-2ca9-2874-3210c3ea87b2@redhat.com> (raw)
In-Reply-To: <158823802979.28101.9340462887738957616.stgit@pasha-ThinkPad-X280>
On 30/04/20 11:13, Pavel Dovgalyuk wrote:
> In record/replay icount mode main loop thread and vCPU thread
> do not perform simultaneously. They take replay mutex to synchronize
> the actions. Sometimes vCPU thread waits for locking the mutex for
> very long time, because main loop releases the mutex and takes it
> back again. Standard qemu mutex do not provide the ordering
> capabilities.
>
> This patch adds a "queue" for replay mutex. Therefore thread ordering
> becomes more "fair". Threads are executed in the same order as
> they are trying to take the mutex.
>
> Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
> ---
> replay/replay-internal.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/replay/replay-internal.c b/replay/replay-internal.c
> index eba8246aae..2e8a3e947a 100644
> --- a/replay/replay-internal.c
> +++ b/replay/replay-internal.c
> @@ -22,6 +22,9 @@
> It also protects replay events queue which stores events to be
> written or read to the log. */
> static QemuMutex lock;
> +/* Condition and queue for fair ordering of mutex lock requests. */
> +static QemuCond mutex_cond;
> +static unsigned long mutex_head, mutex_tail;
>
> /* File for replay writing */
> static bool write_error;
> @@ -197,9 +200,10 @@ static __thread bool replay_locked;
> void replay_mutex_init(void)
> {
> qemu_mutex_init(&lock);
> + qemu_cond_init(&mutex_cond);
> /* Hold the mutex while we start-up */
> - qemu_mutex_lock(&lock);
> replay_locked = true;
> + ++mutex_tail;
> }
>
> bool replay_mutex_locked(void)
> @@ -211,10 +215,16 @@ bool replay_mutex_locked(void)
> void replay_mutex_lock(void)
> {
> if (replay_mode != REPLAY_MODE_NONE) {
> + unsigned long id;
> g_assert(!qemu_mutex_iothread_locked());
> g_assert(!replay_mutex_locked());
> qemu_mutex_lock(&lock);
> + id = mutex_tail++;
> + while (id != mutex_head) {
> + qemu_cond_wait(&mutex_cond, &lock);
> + }
> replay_locked = true;
> + qemu_mutex_unlock(&lock);
> }
> }
>
> @@ -222,7 +232,10 @@ void replay_mutex_unlock(void)
> {
> if (replay_mode != REPLAY_MODE_NONE) {
> g_assert(replay_mutex_locked());
> + qemu_mutex_lock(&lock);
> + ++mutex_head;
> replay_locked = false;
> + qemu_cond_broadcast(&mutex_cond);
> qemu_mutex_unlock(&lock);
> }
> }
>
Queued, thanks.
Paolo
next prev parent reply other threads:[~2020-04-30 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 9:13 [PATCH] replay: implement fair mutex Pavel Dovgalyuk
2020-04-30 9:30 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-30 9:46 Pavel Dovgalyuk
2020-05-18 16:07 ` Alex Bennée
2020-05-19 5:46 ` Pavel Dovgalyuk
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=564674ea-77a8-2ca9-2874-3210c3ea87b2@redhat.com \
--to=pbonzini@redhat.com \
--cc=Pavel.Dovgaluk@gmail.com \
--cc=dovgaluk@ispras.ru \
--cc=pavel.dovgaluk@ispras.ru \
--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).