From: Paolo Bonzini <pbonzini@redhat.com>
To: Pavel Dovgalyuk <dovgaluk@ispras.ru>,
Pavel Dovgalyuk <Pavel.Dovgaluk@gmail.com>,
qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org, pavel.dovgaluk@ispras.ru
Subject: Re: [PATCH] replay: notify the main loop when there are no instructions
Date: Mon, 15 Jun 2020 15:40:42 +0200 [thread overview]
Message-ID: <a5f10cf3-e4e9-69e3-c7a6-96ddea9c68b0@redhat.com> (raw)
In-Reply-To: <44b8f06f-aa8f-33ac-175a-f3af5f9e87e5@ispras.ru>
On 15/06/20 07:39, Pavel Dovgalyuk wrote:
>>
>
> Thanks, but this patch and "replay: synchronize on every virtual timer
> callback" were not included.
>
> Replay tests are succeeded only with these patches.
Added back both. I'll be faster this time, promised.
Paolo
prev parent reply other threads:[~2020-06-15 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 6:47 [PATCH] replay: notify the main loop when there are no instructions Pavel Dovgalyuk
2020-05-22 13:00 ` no-reply
2020-06-01 10:35 ` Pavel Dovgalyuk
2020-06-01 14:01 ` Paolo Bonzini
2020-06-15 5:39 ` Pavel Dovgalyuk
2020-06-15 13:40 ` Paolo Bonzini [this message]
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=a5f10cf3-e4e9-69e3-c7a6-96ddea9c68b0@redhat.com \
--to=pbonzini@redhat.com \
--cc=Pavel.Dovgaluk@gmail.com \
--cc=alex.bennee@linaro.org \
--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).