From: Jason Wang <jasowang@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
David Vrabel <david.vrabel@citrix.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv2] rtl8139: save/load RxMulOk counter (again)
Date: Wed, 22 Jun 2016 13:51:58 +0800 [thread overview]
Message-ID: <576A277E.6010209@redhat.com> (raw)
In-Reply-To: <c819eba9-9620-984f-96d9-fbcb3600d9d4@redhat.com>
On 2016年06月21日 18:11, Paolo Bonzini wrote:
> On 21/06/2016 11:36, David Vrabel wrote:
>> >On 21/06/16 08:35, Paolo Bonzini wrote:
>>> >>
>>> >>
>>> >>On 21/06/2016 03:44, Jason Wang wrote:
>>>> >>>
>>>> >>>
>>>> >>>On 2016年06月21日 01:53, David Vrabel wrote:
>>>>> >>>>Commit 9d29cdeaaca3a0383af764000b71492c4fc67c6e (rtl8139: port
>>>>> >>>>TallyCounters to vmstate) introduced in incompatibility in the v4
>>>>> >>>>format as it omitted the RxOkMul counter.
>>>>> >>>>
>>>>> >>>>There are presumably no users that were impacted by the v4 to v4'
>>>>> >>>>breakage, so increase the save version to 5 and re-add the field,
>>>>> >>>>keeping backward compatibility with v4'.
>>>>> >>>>
>>>>> >>>>We can't have a field conditional on the section version in
>>>>> >>>>vmstate_tally_counters since this version checked would not be the
>>>>> >>>>section version (but the version defined in this structure). So, move
>>>>> >>>>all the fields into the main state structure.
>>>>> >>>>
>>>>> >>>>Signed-off-by: David Vrabel<david.vrabel@citrix.com>
>>>> >>>
>>>> >>>Migration to old version is important for the user and this patch seems
>>>> >>>to break this. How about something like:
>>>> >>>
>>>> >>>- introduce a subsection for RXOKMul
>>>> >>>- only migrate it for new version (e.g >= 2.7)
>> >
>> >I don't see how this can work with snapshots where the QEMU version that
>> >is going to restore the snapshot is not known in advance.
> By "new version" he meant the versioned machine types, e.g.
> pc-i440fx-2.6 and older wouldn't migrate it.
>
>>> >>Introducing a subsection is not really necessary if the value is going
>>> >>to be migrated always, and upstream generally does not have "migrate it
>>> >>only in some version" checks. This is left for downstreams to implement
>>> >>if they care. We just don't have the manpower to ensure that migration
>>> >>to older versions works between all releases of QEMU.
>> >
>> >So is this patch acceptable as is?
> I think it is.
>
> Paolo
Applied to -net.
Thanks
prev parent reply other threads:[~2016-06-22 5:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 17:53 [Qemu-devel] [PATCHv2] rtl8139: save/load RxMulOk counter (again) David Vrabel
2016-06-21 1:44 ` Jason Wang
2016-06-21 7:35 ` Paolo Bonzini
2016-06-21 9:36 ` David Vrabel
2016-06-21 10:11 ` Paolo Bonzini
2016-06-22 5:51 ` Jason Wang [this message]
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=576A277E.6010209@redhat.com \
--to=jasowang@redhat.com \
--cc=david.vrabel@citrix.com \
--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).