From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: [Qemu-devel] Re: [PATCH] rtl8139: IO memory is not part of vmstate
Date: Sun, 12 Dec 2010 18:41:33 +0200 [thread overview]
Message-ID: <20101212164133.GB4148@redhat.com> (raw)
In-Reply-To: <1292171345.2857.43.camel@x201>
On Sun, Dec 12, 2010 at 09:29:05AM -0700, Alex Williamson wrote:
> On Sun, 2010-12-12 at 20:07 +0530, Juan Quintela wrote:
> > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > > On Sun, Dec 12, 2010 at 05:23:39PM +0530, Juan Quintela wrote:
> > >> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > >> > On Thu, Dec 09, 2010 at 03:14:17PM -0700, Alex Williamson wrote:
> >
> > >> > How about we keep migrating the index for the benefit of
> > >> > old versions, but ignore the value on load?
> > >> > Something like the following:
> > >>
> > >> This was my 1st suggestion to Alex O:-)
> > >
> > > The difference here is that instead of sending garbage to the
> > > old version we send an actual index value.
> > >
> > >> So, I am in. he think this is bad for upstream, I don't think so (but
> > >> I understand that it is oppinable).
> > >>
> > >> Later, Juan.
> > >
> > > I think it makes sense to fix this for the stable branch,
> > > and I think we should try as hard as we can to avoid bumping up the
> > > version number there.
> > >
> > > For master we can bump the version number but it might be easier to
> > > just keep the code the same there.
> >
> > I think that your solution is better. For older versions, it works as
> > expected. For new versions, problem is fixed. Solution is not the
> > "purest", but you can say the same about uping the version for a state
> > that is exactly the same length & fields O:-)
>
> I disagree, without bumping the version number, we can never guarantee
> the problem is behind us. We can always migrate to the bad version,
> which puts our users at risk.
Well, they can also migrate between old versions, right?
> The responsible behavior is to allow
> forward migrations and prevent migrations to a version with an issue
> known to compromise VM integrity. Perhaps I feel more strongly about
> this because I actually had to debug this problem. Obvious in
> retrospect, but a huge pain in the butt to get there.
>
> I had sent Juan a similar patch to the one Michael proposed, but with
> the following change:
>
> + if (s->dev.qdev.hotplugged) {
> + s->rtl8139_mmio_io_addr_dummy = IO_MEM_UNASSIGNED;
> + } else {
> + s->rtl8139_mmio_io_addr_dummy = s->rtl8139_mmio_io_addr;
> + }
>
> With this, we at least limit the damage that the hotplugged NIC can do,
> but all it takes is a reboot of the VM to touch the BARs before the
> device becomes unusable (which is better than taking out the whole VM).
Looks good to me.
> If we need something like this for stable, I will begrudgingly agree,
> but for master I think we have to bump the version. Thanks,
>
> Alex
next prev parent reply other threads:[~2010-12-12 16:42 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 [this message]
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
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=20101212164133.GB4148@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@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).