qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>, qemu-devel@nongnu.org
Subject: Re: [PATCH 3/9] replay: rewrite async event handling
Date: Tue, 26 Apr 2022 11:54:56 -0700	[thread overview]
Message-ID: <f5443f62-bdc7-dfd0-ea3a-e13cdcc3da52@linaro.org> (raw)
In-Reply-To: <165062840564.526882.15249141058569885051.stgit@pasha-ThinkPad-X280>

On 4/22/22 04:53, Pavel Dovgalyuk wrote:
> This patch decouples checkpoints and async events.
> It was a tricky part of replay implementation. Now it becomes
> much simpler and easier to maintain.
> 
> Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgalyuk@ispras.ru>

Looks ok, as far as I can follow.  With a couple of nits,

Acked-by: Richard Henderson <richard.henderson@linaro.org>

> --- a/replay/replay-snapshot.c
> +++ b/replay/replay-snapshot.c
> @@ -61,7 +61,6 @@ static const VMStateDescription vmstate_replay = {
>           VMSTATE_UINT64(block_request_id, ReplayState),
>           VMSTATE_INT32(read_event_kind, ReplayState),
>           VMSTATE_UINT64(read_event_id, ReplayState),
> -        VMSTATE_INT32(read_event_checkpoint, ReplayState),
>           VMSTATE_END_OF_LIST()
>       },
>   };

Bump version_id and minimum_version_id.

> +void replay_async_events(void)
> +{
> +    static bool processing = false;
> +    /* If we are already processing the events, recursion may occur
> +        in case of incorrect implementation when HW event modifies timers.
> +        Timer modification may invoke the icount warp, event processing,
> +        and cause the recursion. */

Format multi-line comments per coding style:

   /*
    * block
    */


r~


  reply	other threads:[~2022-04-26 19:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 11:53 [PATCH 0/9] Record/replay refactoring and stuff Pavel Dovgalyuk
2022-04-22 11:53 ` [PATCH 1/9] replay: fix event queue flush for qemu shutdown Pavel Dovgalyuk
2022-04-26 18:25   ` Richard Henderson
2022-04-22 11:53 ` [PATCH 2/9] replay: notify vCPU when BH is scheduled Pavel Dovgalyuk
2022-04-26 18:45   ` Richard Henderson
2022-05-04  6:54     ` Pavel Dovgalyuk
2022-04-22 11:53 ` [PATCH 3/9] replay: rewrite async event handling Pavel Dovgalyuk
2022-04-26 18:54   ` Richard Henderson [this message]
2022-05-04  6:58     ` Pavel Dovgalyuk
2022-04-22 11:53 ` [PATCH 4/9] replay: simplify async event processing Pavel Dovgalyuk
2022-04-26 20:26   ` Richard Henderson
2022-05-04  7:10     ` Pavel Dovgalyuk
2022-04-22 11:53 ` [PATCH 5/9] docs: convert docs/devel/replay page to rst Pavel Dovgalyuk
2022-04-26 20:27   ` Richard Henderson
2022-04-22 11:53 ` [PATCH 6/9] docs: move replay docs to docs/system/replay.rst Pavel Dovgalyuk
2022-04-26 20:33   ` Richard Henderson
2022-04-22 11:53 ` [PATCH 7/9] tests/avocado: update replay_linux test Pavel Dovgalyuk
2022-04-22 11:53 ` [PATCH 8/9] tests/avocado: add replay Linux tests for virtio machine Pavel Dovgalyuk
2022-04-22 11:53 ` [PATCH 9/9] tests/avocado: add replay Linux test for Aarch64 machines 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=f5443f62-bdc7-dfd0-ea3a-e13cdcc3da52@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=pavel.dovgalyuk@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).