qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RfC PATCH] usb/vmstate: add parent dev path
Date: Fri, 26 Aug 2011 11:25:05 +0100	[thread overview]
Message-ID: <20110826102505.GI3944@redhat.com> (raw)
In-Reply-To: <1314353480-14169-1-git-send-email-kraxel@redhat.com>

On Fri, Aug 26, 2011 at 12:11:20PM +0200, Gerd Hoffmann wrote:
> ... to make vmstate id string truely unique with multiple host
> controllers, i.e. move from "1/usb-ptr" to "0000:00:01.3/1/usb-ptr"
> (usb tabled connected to piix3 uhci).
> 
> Obvious problem with that is that it breaks migration from and to older
> versions, thats why it is RfC.  I don't see any way to fix the issue
> without breaking though.  So the question is how to deal with that best?

How about keeping the original naming *only* for devices on the first
USB controller. Since it was impossible to start a QEMU process with
2 USB controllers, migration compatibility does not matter for the
naming of devices on the 2nd, 3rd, 4th.... controller.

Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2011-08-26 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26 10:11 [Qemu-devel] [RfC PATCH] usb/vmstate: add parent dev path Gerd Hoffmann
2011-08-26 10:25 ` Daniel P. Berrange [this message]
2011-08-26 10:46   ` Gerd Hoffmann
  -- strict thread matches above, loose matches on Subject: below --
2012-03-13 12:34 Gerd Hoffmann
2012-03-13 12:42 ` Paolo Bonzini

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=20110826102505.GI3944@redhat.com \
    --to=berrange@redhat.com \
    --cc=kraxel@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).