From: Ciro Santilli <ciro.santilli@gmail.com>
To: Pavel Dovgalyuk <dovgaluk@ispras.ru>
Cc: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 00/19] reverse debugging
Date: Wed, 23 May 2018 16:57:40 +0100 [thread overview]
Message-ID: <CAFXrp_foEgBeKhZGFmRhXYaK4skDF4y4_M_4HEDR0ucAT20oaQ@mail.gmail.com> (raw)
In-Reply-To: <000301d3f299$e1e20340$a5a609c0$@ru>
On Wed, May 23, 2018 at 2:28 PM, Pavel Dovgalyuk <dovgaluk@ispras.ru> wrote:
>> From: Ciro Santilli [mailto:ciro.santilli@gmail.com]
>> On Wed, May 23, 2018 at 7:49 AM, Pavel Dovgalyuk
>> <Pavel.Dovgaluk@ispras.ru> wrote:
>> > GDB remote protocol supports reverse debugging of the targets.
>> > It includes 'reverse step' and 'reverse continue' operations.
>> > The first one finds the previous step of the execution,
>> > and the second one is intended to stop at the last breakpoint that
>> > would happen when the program is executed normally.
>> >
>> > Reverse debugging is possible in the replay mode, when at least
>> > one snapshot was created at the record or replay phase.
>> > QEMU can use these snapshots for travelling back in time with GDB.
>> >
>> > Running the execution in replay mode allows using GDB reverse debugging
>> > commands:
>> > - reverse-stepi (or rsi): Steps one instruction to the past.
>> > QEMU loads on of the prior snapshots and proceeds to the desired
>> > instruction forward. When that step is reaches, execution stops.
>> > - reverse-continue (or rc): Runs execution "backwards".
>> > QEMU tries to find breakpoint or watchpoint by loaded prior snapshot
>> > and replaying the execution. Then QEMU loads snapshots again and
>> > replays to the latest breakpoint. When there are no breakpoints in
>> > the examined section of the execution, QEMU finds one more snapshot
>> > and tries again. After the first snapshot is processed, execution
>> > stops at this snapshot.
>> >
>> > The set of patches include the following modifications:
>> > - gdbstub update for reverse debugging support
>> > - functions that automatically perform reverse step and reverse
>> > continue operations
>> > - hmp/qmp commands for manipulating the replay process
>> > - improvement of the snapshotting for saving the execution step
>> > in the snapshot parameters
>> > - other record/replay fixes
>> >
>> > The patches are available in the repository:
>> > https://github.com/ispras/qemu/tree/rr-180428
>> >
>>
>> This branch appears to contain one month old commits, is it the correct one?
>
> Right.
> There were no significant changes except the fix which was already queued by Paolo.
> As soon as it is upstreamed, I'll update the branch.
>
OK.
At the current branch 6b23df0d0ca0e5e999cd12af2b18b2a95faeb421 still
observe the same behaviour as mentioned at:
https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg04669.html
If I try to savevm during the debug replay to speedup up reverse
execution, QEMU hangs.
Have you managed to reproduce that? Or is this not an intended use
case, i.e. only savevm during record is supported?
Am I correct to understand that being able to do savevms in the middle
of a long execution is the critical feature that this adds? Otherwise
we are essentially replaying from the initial snapshot every time, so
we might as well just restart a new replay, is that true?
> Pavel Dovgalyuk
>
next prev parent reply other threads:[~2018-05-23 15:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 6:49 [Qemu-devel] [PATCH v3 00/19] reverse debugging Pavel Dovgalyuk
2018-05-23 6:49 ` [Qemu-devel] [PATCH v3 01/19] block: implement bdrv_snapshot_goto for blkreplay Pavel Dovgalyuk
2018-05-23 6:49 ` [Qemu-devel] [PATCH v3 02/19] replay: disable default snapshot for record/replay Pavel Dovgalyuk
2018-05-23 6:49 ` [Qemu-devel] [PATCH v3 03/19] replay: update docs for record/replay with block devices Pavel Dovgalyuk
2018-05-23 6:50 ` [Qemu-devel] [PATCH v3 04/19] replay: don't drain/flush bdrv queue while RR is working Pavel Dovgalyuk
2018-05-23 6:50 ` [Qemu-devel] [PATCH v3 05/19] replay: finish record/replay before closing the disks Pavel Dovgalyuk
2018-05-23 6:50 ` [Qemu-devel] [PATCH v3 06/19] qcow2: introduce icount field for snapshots Pavel Dovgalyuk
2018-05-23 6:50 ` [Qemu-devel] [PATCH v3 07/19] migration: " Pavel Dovgalyuk
2018-05-23 18:08 ` Eric Blake
2018-05-23 6:50 ` [Qemu-devel] [PATCH v3 08/19] replay: introduce info hmp/qmp command Pavel Dovgalyuk
2018-05-23 6:50 ` [Qemu-devel] [PATCH v3 09/19] replay: introduce breakpoint at the specified step Pavel Dovgalyuk
2018-05-23 6:50 ` [Qemu-devel] [PATCH v3 10/19] replay: implement replay-seek command to proceed to the desired step Pavel Dovgalyuk
2018-05-23 6:50 ` [Qemu-devel] [PATCH v3 11/19] replay: flush events when exiting Pavel Dovgalyuk
2018-05-23 6:50 ` [Qemu-devel] [PATCH v3 12/19] timer: remove replay clock probe in deadline calculation Pavel Dovgalyuk
2018-05-23 6:50 ` [Qemu-devel] [PATCH v3 13/19] replay: refine replay-time module Pavel Dovgalyuk
2018-05-23 6:51 ` [Qemu-devel] [PATCH v3 14/19] translator: fix breakpoint processing Pavel Dovgalyuk
2018-05-23 6:51 ` [Qemu-devel] [PATCH v3 15/19] replay: flush rr queue before loading the vmstate Pavel Dovgalyuk
2018-05-23 6:51 ` [Qemu-devel] [PATCH v3 16/19] gdbstub: add reverse step support in replay mode Pavel Dovgalyuk
2018-05-23 6:51 ` [Qemu-devel] [PATCH v3 17/19] gdbstub: add reverse continue " Pavel Dovgalyuk
2018-05-23 6:51 ` [Qemu-devel] [PATCH v3 18/19] replay: describe reverse debugging in docs/replay.txt Pavel Dovgalyuk
2018-05-23 6:51 ` [Qemu-devel] [PATCH v3 19/19] replay: allow loading any snapshots before recording Pavel Dovgalyuk
2018-05-23 13:23 ` [Qemu-devel] [PATCH v3 00/19] reverse debugging Ciro Santilli
2018-05-23 13:28 ` Pavel Dovgalyuk
2018-05-23 15:57 ` Ciro Santilli [this message]
2018-05-24 6:00 ` 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=CAFXrp_foEgBeKhZGFmRhXYaK4skDF4y4_M_4HEDR0ucAT20oaQ@mail.gmail.com \
--to=ciro.santilli@gmail.com \
--cc=Pavel.Dovgaluk@ispras.ru \
--cc=dovgaluk@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).