Re: [Qemu-devel] [PATCH v9 13/21] replay: implement replay-seek command to proceed to the desired step

["Pavel Dovgalyuk" <dovgaluk@ispras.ru>]

> From: Markus Armbruster [mailto:armbru@redhat.com]
> Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru> writes:
> 
> > This patch adds hmp/qmp commands replay_seek/replay-seek that proceed
> > the execution to the specified step.
> > The command automatically loads nearest snapshot and replay the execution
> > to find the desired step.
> 
> "step" again.
> 
> >
> > Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
> >
> > --
> >
> > v2:
> >  - renamed replay_seek qmp command into replay-seek
> >    (suggested by Eric Blake)
> > v7:
> >  - small fixes related to Markus Armbruster's review
> > v9:
> >  - changed 'step' parameter name to 'icount'
> >  - moved json stuff to replay.json and updated the description
> >    (suggested by Markus Armbruster)
> > ---
> >  hmp-commands.hx           |   19 +++++++++
> >  hmp.h                     |    1
> >  qapi/replay.json          |   20 ++++++++++
> >  replay/replay-debugging.c |   91 +++++++++++++++++++++++++++++++++++++++++++++
> >  4 files changed, 131 insertions(+)
> >
> > diff --git a/hmp-commands.hx b/hmp-commands.hx
> > index 6d04c02..2839acc 100644
> > --- a/hmp-commands.hx
> > +++ b/hmp-commands.hx
> > @@ -1924,6 +1924,25 @@ The command is ignored when there are no replay breakpoints.
> >  ETEXI
> >
> >      {
> > +        .name       = "replay_seek",
> > +        .args_type  = "icount:i",
> > +        .params     = "icount",
> > +        .help       = "rewinds replay to the step specified by icount",
> 
> We use imperative mood in .help: "rewind".
> 
> "Rewind" suggests going backward.  The command can do that.  But it can
> also go forward.  What about:
> 
> "replay execution to the specified intruction count"
> 
> > +        .cmd        = hmp_replay_seek,
> > +    },
> > +
> > +STEXI
> > +@item replay_seek @var{icount}
> > +@findex replay_seek
> > +Automatically proceeds to the step specified by @var{icount}, when
> > +replaying the execution. The command automatically loads nearest
> > +snapshot and replay the execution to find the desired step.
> > +When there is no preceding snapshot or the execution is not replayed,
> > +then the command is ignored.
> 
> Uh, why isn't that an error?

What about this one?

Automatically proceeds to the instruction count @var{icount}, when
replaying the execution. The command automatically loads nearest
snapshot and replays the execution to find the desired instruction.
When there is no preceding snapshot or the execution is not replayed,
then the command is ignored and error message is displayed.
icount for the reference may be observed with 'info replay' command.


Pavel Dovgalyuk