From: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, alex.bennee@linaro.org
Subject: Re: [PATCH v2] replay: notify CPU on event
Date: Wed, 24 Feb 2021 11:26:26 +0300 [thread overview]
Message-ID: <28b28cbe-5d08-bd60-0abd-fbba628b4d67@ispras.ru> (raw)
In-Reply-To: <161346807047.1296085.955420533772419632.stgit@pasha-ThinkPad-X280>
ping
On 16.02.2021 12:34, Pavel Dovgalyuk wrote:
> This patch enables vCPU notification to wake it up
> when new async event comes in replay mode.
>
> The motivation of this patch is the following.
> Consider recorded block async event. It is saved into the log
> with one of the checkpoints. This checkpoint may be passed in
> vCPU loop. In replay mode when this async event is read from
> the log, and block thread task is not finished yet, vCPU thread
> goes to sleep. That is why this patch adds waking up the vCPU
> to process this finished event.
>
> Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgalyuk@ispras.ru>
> ---
> replay/replay-events.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/replay/replay-events.c b/replay/replay-events.c
> index a1c6bb934e..92dc800219 100644
> --- a/replay/replay-events.c
> +++ b/replay/replay-events.c
> @@ -126,6 +126,7 @@ void replay_add_event(ReplayAsyncEventKind event_kind,
>
> g_assert(replay_mutex_locked());
> QTAILQ_INSERT_TAIL(&events_list, event, events);
> + qemu_clock_notify(QEMU_CLOCK_VIRTUAL);
> }
>
> void replay_bh_schedule_event(QEMUBH *bh)
>
next prev parent reply other threads:[~2021-02-24 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 9:34 [PATCH v2] replay: notify CPU on event Pavel Dovgalyuk
2021-02-24 8:26 ` Pavel Dovgalyuk [this message]
2021-03-15 6:01 ` Pavel Dovgalyuk
2021-03-29 7:43 Pavel Dovgalyuk
2021-03-29 10:29 ` Paolo Bonzini
2021-03-29 11:23 ` Pavel Dovgalyuk
2021-03-29 12:10 ` Paolo Bonzini
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=28b28cbe-5d08-bd60-0abd-fbba628b4d67@ispras.ru \
--to=pavel.dovgalyuk@ispras.ru \
--cc=alex.bennee@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.