From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 00/18] Record/replay core for QEMU 2.4-rc1
Date: Wed, 04 Nov 2015 18:11:06 +0000 [thread overview]
Message-ID: <87bnb91vph.fsf@linaro.org> (raw)
In-Reply-To: <1446653876-116008-1-git-send-email-pbonzini@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> The following changes since commit 7bc8e0c967a4ef77657174d28af775691e18b4ce:
>
> Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (2015-10-29 09:49:52 +0000)
>
> are available in the git repository at:
>
>
> git://github.com/bonzini/qemu.git tags/for-upstream-replay
>
> for you to fetch changes up to e02cf7f4de91174dc322e235da6e1a1198601920:
>
> replay: recording of the user input (2015-11-04 15:09:54 +0100)
>
> ----------------------------------------------------------------
> So here it is, let's see what happens.
>
> ----------------------------------------------------------------
> Pavel Dovgalyuk (18):
> replay: global variables and function stubs
> replay: internal functions for replay log
> replay: introduce mutex to protect the replay log
> replay: introduce icount event
> cpu-exec: allow temporary disabling icount
> cpu: replay instructions sequence
> replay: interrupts and exceptions
> replay: asynchronous events infrastructure
> replay: recording and replaying clock ticks
> replay: shutdown event
> icount: improve counting for record/replay
> replay: checkpoints
> bottom halves: introduce bh call function
> replay: ptimer
> replay: initialization and deinitialization
> replay: replay blockers for devices
> replay: command line options
> replay: recording of the user input
>
> Makefile.objs | 2 +
> async.c | 7 +-
> cpu-exec.c | 55 ++++++--
> cpus.c | 64 ++++++---
> docs/replay.txt | 168 +++++++++++++++++++++++
> exec.c | 2 +
> hw/bt/hci.c | 7 +
> hw/core/ptimer.c | 3 +-
> include/block/aio.h | 5 +
> include/exec/exec-all.h | 1 +
> include/qapi/qmp/qerror.h | 3 +
> include/sysemu/replay.h | 120 ++++++++++++++++
> include/ui/input.h | 2 +
> main-loop.c | 3 +
> qapi-schema.json | 18 +++
> qemu-options.hx | 8 +-
> qemu-timer.c | 43 +++++-
> replay/Makefile.objs | 5 +
> replay/replay-events.c | 279 +++++++++++++++++++++++++++++++++++++
> replay/replay-input.c | 160 ++++++++++++++++++++++
> replay/replay-internal.c | 206 ++++++++++++++++++++++++++++
> replay/replay-internal.h | 140 +++++++++++++++++++
> replay/replay-time.c | 64 +++++++++
> replay/replay.c | 342 ++++++++++++++++++++++++++++++++++++++++++++++
> stubs/Makefile.objs | 2 +
> stubs/replay-user.c | 32 +++++
> stubs/replay.c | 31 +++++
> translate-all.c | 2 +-
> ui/input.c | 27 ++--
> vl.c | 60 ++++++--
> 30 files changed, 1803 insertions(+), 58 deletions(-)
> create mode 100644 docs/replay.txt
> create mode 100644 include/sysemu/replay.h
> create mode 100644 replay/Makefile.objs
> create mode 100644 replay/replay-events.c
> create mode 100644 replay/replay-input.c
> create mode 100644 replay/replay-internal.c
> create mode 100644 replay/replay-internal.h
> create mode 100644 replay/replay-time.c
> create mode 100644 replay/replay.c
> create mode 100644 stubs/replay-user.c
> create mode 100644 stubs/replay.c
Are there any tests to protect basic functionality?
I'm just worried about stuff getting broken when MTTCG comes along.
--
Alex Bennée
next prev parent reply other threads:[~2015-11-04 18:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 16:17 [Qemu-devel] [PULL 00/18] Record/replay core for QEMU 2.4-rc1 Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 01/18] replay: global variables and function stubs Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 02/18] replay: internal functions for replay log Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 03/18] replay: introduce mutex to protect the " Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 04/18] replay: introduce icount event Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 05/18] cpu-exec: allow temporary disabling icount Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 06/18] cpu: replay instructions sequence Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 07/18] replay: interrupts and exceptions Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 08/18] replay: asynchronous events infrastructure Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 09/18] replay: recording and replaying clock ticks Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 10/18] replay: shutdown event Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 11/18] icount: improve counting for record/replay Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 12/18] replay: checkpoints Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 13/18] bottom halves: introduce bh call function Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 14/18] replay: ptimer Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 15/18] replay: initialization and deinitialization Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 16/18] replay: replay blockers for devices Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 17/18] replay: command line options Paolo Bonzini
2015-11-04 16:17 ` [Qemu-devel] [PULL 18/18] replay: recording of the user input Paolo Bonzini
2015-11-04 18:11 ` Alex Bennée [this message]
2015-11-05 10:52 ` [Qemu-devel] [PULL 00/18] Record/replay core for QEMU 2.4-rc1 Peter Maydell
2015-11-05 11:18 ` 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=87bnb91vph.fsf@linaro.org \
--to=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 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).