From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, quintela@redhat.com
Subject: [Qemu-devel] Re: [PATCH] rtl8139: IO memory is not part of vmstate
Date: Wed, 15 Dec 2010 21:04:36 +0200 [thread overview]
Message-ID: <20101215190436.GA8605@redhat.com> (raw)
In-Reply-To: <4D08F6F9.5050104@redhat.com>
On Wed, Dec 15, 2010 at 06:12:25PM +0100, Paolo Bonzini wrote:
> On 12/15/2010 11:00 AM, Michael S. Tsirkin wrote:
> >>Indeed, subsections are for data that is rarely needed so that
> >>there's some chance (sometimes ~100%) of migration working
> >>seemlessly.
> >
> >If a subsection arrives that qemu does
> >not know about, won't migratin fail?
>
> Yes, that's why rarely needed => some high chance of migration
> working (though no certainty).
>
> >>In this case it's either
> >>no-bump-and-live-with-the-consequences, or changing the version id.
> >
> >This was discussed to death already. version ids have the problem
> >that they don't play nicely with downstreams.
>
> Downstream version bumps don't play nicely with upstream, so
> downstream does have a reason for always-necessary subsections. But
> upstream can bump the version id as much as they care.
>
> Paolo
This assuming upstream developers do not care about downstreams.
To give a chance for downstream to cherry-pick changes, upstream
should use subsections instead of version ids too.
--
MST
next prev parent reply other threads:[~2010-12-15 19:05 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
2010-12-15 10:00 ` Michael S. Tsirkin
2010-12-15 17:12 ` Paolo Bonzini
2010-12-15 19:04 ` Michael S. Tsirkin [this message]
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=20101215190436.GA8605@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.