From: "Alex Bennée" <alex.bennee@linaro.org>
To: Eric Blake <eblake@redhat.com>
Cc: pavel.dovgaluk@ispras.ru, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH-for-2.9] replay/replay.c: bump REPLAY_VERSION
Date: Fri, 24 Mar 2017 17:25:10 +0000 [thread overview]
Message-ID: <871stmy4cp.fsf@linaro.org> (raw)
In-Reply-To: <fa4d3712-859a-ced3-3883-8951ee9b6aa7@redhat.com>
Eric Blake <eblake@redhat.com> writes:
> On 03/24/2017 10:26 AM, Alex Bennée wrote:
>> A previous commit (3d4d16f4) added support for audio record/playback.
>> However this breaks the logfile ABI due to the re-ordering of the
>> ReplayEvents enum. The REPLAY_VERSION check is meant to prevent you
>> from using old log files in newer QEMUs but this is currently broken.
>
> As we don't have a formal release with the reordered enum yet, would an
> alternative approach be partially reverting 3d4d16f4 to instead stick
> the new enum values at the end, so that all existing enums are in the
> same order?
That would certainly be an option.
> Or do you still need the version bump even then, because
> you don't want a new stream (with the new enums) being played to an
> older system that isn't expecting them?
I'm not personally bothered either way. Currently the check is a simple
match so there is not really the concept of a super/subsets of log file.
I only ran into this as I was trying to debug the record/replay
regression while writing a dumper script to debug the current
regression:
https://github.com/stsquad/qemu/blob/mttcg/more-fixes-for-rc1-v2/scripts/replay-dump.py
--
Alex Bennée
next prev parent reply other threads:[~2017-03-24 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 15:26 [Qemu-devel] [PATCH-for-2.9] replay/replay.c: bump REPLAY_VERSION Alex Bennée
2017-03-24 17:11 ` Eric Blake
2017-03-24 17:25 ` Alex Bennée [this message]
2017-03-27 5:42 ` 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=871stmy4cp.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=eblake@redhat.com \
--cc=pavel.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).