qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] replay: fix recursive checkpoints
Date: Mon, 29 Mar 2021 12:25:12 +0100	[thread overview]
Message-ID: <87o8f2xk04.fsf@linaro.org> (raw)
In-Reply-To: <161700476500.1140362.10108444973730452257.stgit@pasha-ThinkPad-X280>


Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru> writes:

> Record/replay uses checkpoints to synchronize the execution
> of the threads and timers. Hardware events such as BH are
> processed at the checkpoints too.
> Event processing can cause refreshing the virtual timers
> and calling the icount-related functions, that also use checkpoints.
> This patch prevents recursive processing of such checkpoints,
> because they have their own records in the log and should be
> processed later.
>
> Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgalyuk@ispras.ru>
> ---
>  replay/replay.c |   11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/replay/replay.c b/replay/replay.c
> index c806fec69a..6df2abc18c 100644
> --- a/replay/replay.c
> +++ b/replay/replay.c
> @@ -180,12 +180,13 @@ bool replay_checkpoint(ReplayCheckpoint checkpoint)
>      }
>  
>      if (in_checkpoint) {
> -        /* If we are already in checkpoint, then there is no need
> -           for additional synchronization.
> +        /*
>             Recursion occurs when HW event modifies timers.
> -           Timer modification may invoke the checkpoint and
> -           proceed to recursion. */
> -        return true;
> +           Prevent performing icount warp in this case and
> +           wait for another invocation of the checkpoint.
> +        */

nit: as you are updating the comment you might as well fix the style. It
would probably help with the diff as well.

> +        g_assert(replay_mode == REPLAY_MODE_PLAY);
> +        return false;
>      }
>      in_checkpoint = true;

The accompanying comments in replay.h are also confusing 

    Returns 0 in PLAY mode if checkpoint was not found.
    Returns 1 in all other cases.

Which translated to actual bool results:

    Returns false in PLAY mode if checkpoint was not found
    Returns true in all other cases

Which implies the checkpoint is always found (or created?) which I'm not
even sure of while following the rest of the replay_checkpoint code
which has exit cases of:

    bool res = false; (default)
    replay_state.data_kind != EVENT_ASYNC;
    res = true; (when recording)

So is the following more correct?

/**
 * replay_checkpoint(checkpoint): save (in RECORD) or consume (in PLAY) checkpoint
 * @checkpoint: the checkpoint event
 *
 * In SAVE mode stores the checkpoint in the record and potentially
 * saves a number of events.
 *
 * In PLAY mode consumes checkpoint and any following EVENT_ASYNC events.
 *
 * Results: in SAVE mode always True
 *          in PLAY mode True unless checkpoint not found or recursively called.
 */

-- 
Alex Bennée


  parent reply	other threads:[~2021-03-29 11:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  7:59 [PATCH] replay: fix recursive checkpoints Pavel Dovgalyuk
2021-03-29  9:42 ` Paolo Bonzini
2021-03-29 11:25 ` Alex Bennée [this message]
2021-03-30  8:24   ` 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=87o8f2xk04.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=pavel.dovgalyuk@ispras.ru \
    --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 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).