All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-devel@nongnu.org
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
	"Pavel Dovgalyuk" <Pavel.Dovgalyuk@ispras.ru>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"John Snow" <jsnow@redhat.com>, "Cleber Rosa" <crosa@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>
Subject: [PATCH v2 0/4] replay: minor fixes and tests
Date: Fri, 26 Jan 2024 02:08:31 +1000	[thread overview]
Message-ID: <20240125160835.480488-1-npiggin@gmail.com> (raw)

replay-dump.py script still chokes quite easily on a trace of
Linux boot, so I revived some  patches from last year that fix
the script and add some test cases for it.

The runstate patch doesn't have a test case (yet), but you can
hit the problem by replaying to the machine shutdown and then
reverse-stepping.

Thanks,
Nick

Since v1:
- Rebase onto script that now has initial v12 support.
- avocado tests now also cover replay_kernel.py because
  replay_linux.py is very heavyweight and flaky. replay_kernel is
  feasible to run in CI and general hacking.
- Rearrange replay-dump.py decoders.

Nicholas Piggin (4):
  replay: allow runstate shutdown->running when replaying trace
  scripts/replay-dump.py: Update to current rr record format
  scripts/replay-dump.py: rejig decoders in event number order
  tests/avocado: excercise scripts/replay-dump.py in replay tests

 include/sysemu/runstate.h      |   1 +
 replay/replay.c                |   2 +
 system/runstate.c              |  19 ++++
 scripts/replay-dump.py         | 172 +++++++++++++++++++++++----------
 tests/avocado/replay_kernel.py |  16 +++
 tests/avocado/replay_linux.py  |  16 +++
 6 files changed, 173 insertions(+), 53 deletions(-)

-- 
2.42.0



             reply	other threads:[~2024-01-25 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 16:08 Nicholas Piggin [this message]
2024-01-25 16:08 ` [PATCH v2 1/4] replay: allow runstate shutdown->running when replaying trace Nicholas Piggin
2024-01-29  5:06   ` Pavel Dovgalyuk
2024-01-25 16:08 ` [PATCH v2 2/4] scripts/replay-dump.py: Update to current rr record format Nicholas Piggin
2024-01-30 21:36   ` John Snow
2024-02-26  6:39     ` Nicholas Piggin
2024-01-25 16:08 ` [PATCH v2 3/4] scripts/replay-dump.py: rejig decoders in event number order Nicholas Piggin
2024-01-25 16:08 ` [PATCH v2 4/4] tests/avocado: excercise scripts/replay-dump.py in replay tests Nicholas Piggin
2024-01-29  5:08   ` 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=20240125160835.480488-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=Pavel.Dovgalyuk@ispras.ru \
    --cc=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=crosa@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=wainersm@redhat.com \
    /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.