qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: quintela@redhat.com, qemu-devel@nongnu.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] rtl8139: IO memory is not part of vmstate
Date: Tue, 14 Dec 2010 16:59:55 +0100	[thread overview]
Message-ID: <4D07947B.80702@redhat.com> (raw)
In-Reply-To: <1292341315.2857.175.camel@x201>

On 12/14/2010 04:41 PM, Alex Williamson wrote:
> >  Maybe in this particular case the advantage is minimal.
> >  But it seems easier to stick to a rule of no more version
> >  bumps than argue about each case.
>
> Do we have such a rule?  If we have a subsection who's needed function
> is return 1, I think that's a good indication that it's not appropriate
> for a subsection and the end result is equivalent to bumping the main
> driver vmstate version.  It's convoluted to try to hide a one-way
> upgrade in a subsection.  Thanks,

Indeed, subsections are for data that is rarely needed so that there's 
some chance (sometimes ~100%) of migration working seemlessly.  In this 
case it's either no-bump-and-live-with-the-consequences, or changing the 
version id.

Paolo

  reply	other threads:[~2010-12-14 15:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 19:16 [Qemu-devel] [PATCH] rtl8139: IO memory is not part of vmstate Alex Williamson
2010-12-09 21:49 ` [Qemu-devel] " Juan Quintela
2010-12-09 22:14   ` Alex Williamson
2010-12-12 10:28     ` Michael S. Tsirkin
2010-12-12 11:53       ` Juan Quintela
2010-12-12 12:01         ` Michael S. Tsirkin
2010-12-12 14:37           ` Juan Quintela
2010-12-12 16:29             ` Alex Williamson
2010-12-12 16:41               ` Michael S. Tsirkin
2010-12-12 21:25               ` Juan Quintela
2010-12-13 17:43                 ` Alex Williamson
2010-12-13 17:50                   ` Michael S. Tsirkin
2010-12-13 18:00                     ` Alex Williamson
2010-12-13 18:54                       ` Michael S. Tsirkin
2010-12-13 18:59                         ` Alex Williamson
2010-12-13 19:06                           ` Michael S. Tsirkin
2010-12-13 19:15                             ` Alex Williamson
2010-12-14  4:43                               ` Michael S. Tsirkin
2010-12-14  5:00                                 ` Alex Williamson
2010-12-14 12:32                                   ` Michael S. Tsirkin
2010-12-14 15:41                                     ` Alex Williamson
2010-12-14 15:59                                       ` Paolo Bonzini [this message]
2010-12-15 10:00                                         ` Michael S. Tsirkin
2010-12-15 17:12                                           ` Paolo Bonzini
2010-12-15 19:04                                             ` Michael S. Tsirkin
2010-12-16 12:45                                               ` Paolo Bonzini
2010-12-15 10:07                                       ` Michael S. Tsirkin
2010-12-15 16:05                                         ` Alex Williamson

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=4D07947B.80702@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).