qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, ehabkost@redhat.com, philmd@redhat.com,
	mtosatti@redhat.com, stefanha@redhat.com, armbru@redhat.com,
	mreitz@redhat.com, wrampazz@redhat.com, crosa@redhat.com,
	pbonzini@redhat.com, alex.bennee@linaro.org,
	zhiwei_liu@c-sky.com, rth@twiddle.net
Subject: Re: [PATCH 02/13] qcow2: introduce icount field for snapshots
Date: Mon, 6 Jul 2020 15:17:04 -0500	[thread overview]
Message-ID: <6882cb05-8533-d6ac-d41b-95c3d19ca496@redhat.com> (raw)
In-Reply-To: <159316679154.10508.16814264064541947914.stgit@pasha-ThinkPad-X280>

On 6/26/20 5:19 AM, Pavel Dovgalyuk wrote:
> From: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
> 
> This patch introduces the icount field for saving within the snapshot.
> It is required for navigation between the snapshots in record/replay mode.
> 
> Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgalyuk@ispras.ru>
> Acked-by: Kevin Wolf <kwolf@redhat.com>
> ---
>   0 files changed
> 

That's an odd diffstat; you may want to investigate why git isn't 
showing the usual diffstat that makes it easier to see which files are 
touched and the relative size of the changes.


> +++ b/docs/interop/qcow2.txt
> @@ -645,6 +645,11 @@ Snapshot table entry:
>   
>                       Byte 48 - 55:   Virtual disk size of the snapshot in bytes
>   
> +                    Byte 56 - 63:   icount value which corresponds to
> +                                    the record/replay instruction count
> +                                    when the snapshot was taken. Set to -1
> +                                    if icount was disabled
> +
>                       Version 3 images must include extra data at least up to
>                       byte 55.

Should we have additional text here, similar to what was added to the 
overall header in 3ae3fcfa, about how to properly add additional 
optional fields while maintaining back-compat considerations?  Maybe 
just a one sentence reference that the rules in that section apply here too?

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org



  reply	other threads:[~2020-07-06 20:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 10:19 [PATCH 00/13] Reverse debugging Pavel Dovgalyuk
2020-06-26 10:19 ` [PATCH 01/13] replay: provide an accessor for rr filename Pavel Dovgalyuk
2020-06-26 10:19 ` [PATCH 02/13] qcow2: introduce icount field for snapshots Pavel Dovgalyuk
2020-07-06 20:17   ` Eric Blake [this message]
2020-07-16  6:43     ` Pavel Dovgalyuk
2020-06-26 10:19 ` [PATCH 03/13] migration: " Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 04/13] iotests: update snapshot test for new output format Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 05/13] qapi: introduce replay.json for record/replay-related stuff Pavel Dovgalyuk
2020-07-15 11:20   ` Alex Bennée
2020-07-16  6:00     ` Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 06/13] replay: introduce info hmp/qmp command Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 07/13] replay: introduce breakpoint at the specified step Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 08/13] replay: implement replay-seek command Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 09/13] replay: flush rr queue before loading the vmstate Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 10/13] gdbstub: add reverse step support in replay mode Pavel Dovgalyuk
2020-07-15 11:27   ` Alex Bennée
2020-06-26 10:20 ` [PATCH 11/13] gdbstub: add reverse continue " Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 12/13] replay: describe reverse debugging in docs/replay.txt Pavel Dovgalyuk
2020-06-26 10:20 ` [PATCH 13/13] tests/acceptance: add reverse debugging test Pavel Dovgalyuk
2020-07-06  6:02 ` [PATCH 00/13] Reverse debugging Pavel Dovgalyuk
2020-07-06 19:55   ` Alex Bennée
2020-07-07  5: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=6882cb05-8533-d6ac-d41b-95c3d19ca496@redhat.com \
    --to=eblake@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pavel.dovgalyuk@ispras.ru \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=stefanha@redhat.com \
    --cc=wrampazz@redhat.com \
    --cc=zhiwei_liu@c-sky.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 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).