All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, quintela@redhat.com
Subject: [Qemu-devel] Re: [PATCH 0/2] Fix rtl8139 migration with hotplug
Date: Fri, 17 Dec 2010 01:41:47 +0200	[thread overview]
Message-ID: <20101216234147.GF3878@redhat.com> (raw)
In-Reply-To: <20101216175516.6420.66081.stgit@s20.home>

On Thu, Dec 16, 2010 at 11:01:49AM -0700, Alex Williamson wrote:
> Ok, I think this might actually make everyone happy, but I've been
> known to be wrong about that many times before.  Juan challenged me
> to find an rtl8139 migration scenario that fails when hotplug is
> not involved (and not switch device creation order since that's a
> usage bug).  I couldn't come up with one.  We had been arguing that
> a subsection didn't make sense for the change to rtl8139 vmstate
> because the needed function would be {return 1}. but what if we
> could detect if the VM had done any other hotplugs and only include
> the subsection in those cases.  That's what this short series does.
> 
> So, I hope Juan is happy because this preserves the migration ABI
> for the majority of the use cases, and I hope Michael is happy
> because it does so using a subsection.  Thanks,
> 
> Alex

I think it's a clever hack.

Acked-by: Michael S. Tsirkin <mst@redhat.com>

> ---
> 
> Alex Williamson (2):
>       rtl8139: Use subsection to restrict migration after hotplug
>       qdev: Track runtime machine modifications
> 
> 
>  hw/qdev.c    |   10 ++++++++++
>  hw/qdev.h    |    1 +
>  hw/rtl8139.c |   28 +++++++++++++++++++++++++++-
>  3 files changed, 38 insertions(+), 1 deletions(-)

  parent reply	other threads:[~2010-12-16 23:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16 18:01 [Qemu-devel] [PATCH 0/2] Fix rtl8139 migration with hotplug Alex Williamson
2010-12-16 18:02 ` [Qemu-devel] [PATCH 1/2] qdev: Track runtime machine modifications Alex Williamson
2010-12-16 18:02 ` [Qemu-devel] [PATCH 2/2] rtl8139: Use subsection to restrict migration after hotplug Alex Williamson
2010-12-16 23:41 ` Michael S. Tsirkin [this message]
2010-12-17  1:35 ` [Qemu-devel] Re: [PATCH 0/2] Fix rtl8139 migration with hotplug Juan Quintela
2011-01-04 19:37 ` [Qemu-devel] [RESEND PATCH " Alex Williamson
2011-01-04 19:37   ` [Qemu-devel] [RESEND PATCH 1/2] qdev: Track runtime machine modifications Alex Williamson
2011-01-12 12:09     ` Markus Armbruster
2011-01-12 13:51       ` Alex Williamson
2011-01-04 19:38   ` [Qemu-devel] [RESEND PATCH 2/2] rtl8139: Use subsection to restrict migration after hotplug Alex Williamson
2011-01-05 10:13   ` [Qemu-devel] Re: [RESEND PATCH 0/2] Fix rtl8139 migration with hotplug Michael S. Tsirkin

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=20101216234147.GF3878@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.