From: Paolo Bonzini <pbonzini@redhat.com>
To: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>, qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org
Subject: Re: [PATCH] replay: don't wait in run_on_cpu
Date: Mon, 29 Mar 2021 14:11:36 +0200 [thread overview]
Message-ID: <d43889b5-ebf6-12e5-af95-94e25bc7d383@redhat.com> (raw)
In-Reply-To: <2f94f9b5-0a90-dbc1-e35e-d6c43580c127@ispras.ru>
On 29/03/21 12:55, Pavel Dovgalyuk wrote:
>>>
>>
>> Is the "or" saying that the execution is using the lockstep mode? If
>> so, can you put it in a separate function so that it's more
>> self-explanatory and check if it should be used elsewhere?
>
> It was replay (is that lockstep that you mentioned?).
Lockstep in the sense that (as is the case in record/replay mode) the
I/O thread and vCPU thread execute in turns.
Paolo
> I check that the mutex is already locked, which means, that vCPU
> does nothing at this moment.
next prev parent reply other threads:[~2021-03-29 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 8:05 [PATCH] replay: don't wait in run_on_cpu Pavel Dovgalyuk
2021-03-29 9:42 ` Paolo Bonzini
2021-03-29 10:55 ` Pavel Dovgalyuk
2021-03-29 12:11 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-11 7:14 Pavel Dovgalyuk
2021-03-15 5:59 ` 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=d43889b5-ebf6-12e5-af95-94e25bc7d383@redhat.com \
--to=pbonzini@redhat.com \
--cc=pavel.dovgalyuk@ispras.ru \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).