From: Isaku Yamahata <yamahata@valinux.co.jp>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] pci: disable migration of p2p bridge
Date: Wed, 22 Dec 2010 17:00:45 +0900 [thread overview]
Message-ID: <20101222080045.GA7603@valinux.co.jp> (raw)
In-Reply-To: <20101222062716.GC7814@redhat.com>
On Wed, Dec 22, 2010 at 08:27:17AM +0200, Michael S. Tsirkin wrote:
> On Wed, Dec 22, 2010 at 12:13:43PM +0900, Isaku Yamahata wrote:
> > Right now pcibus_get_dev_path() isn't migration save because
> > bus number/secondary bus number are set by guest OS.
> > So it can't be used reliably for qemu internal id.
> >
> > For 0.14 release, disable p2p bridge migration at the moment.
> > Once pcibus_get_dev_path() is fixed, this patch should be reverted.
> > It will be addressed for 0.15 release.
> >
> > Cc: "Michael S. Tsirkin" <mst@redhat.com>
> > Cc: Alex Williamson <alex.williamson@redhat.com>
> > Cc: Blue Swirl <blauwirbel@gmail.com>
> > Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
>
>
> Hmm, haven't looked into this deeply - can we do this in one place
> when the bridge is created?
Unfortunately it's not easy. It requires revising
register_device_unmigratable(). I have to admit this patch is ugly.
This patch is temporal work around and should be reverted eventually.
So I think it is better to address the original issue (allowing migration
of p2p bridge) instead of addressing register_device_unmigratable().
thanks
--
yamahata
next prev parent reply other threads:[~2010-12-22 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 3:13 [Qemu-devel] [PATCH] pci: disable migration of p2p bridge Isaku Yamahata
2010-12-22 6:27 ` [Qemu-devel] " Michael S. Tsirkin
2010-12-22 8:00 ` Isaku Yamahata [this message]
2010-12-22 10:54 ` 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=20101222080045.GA7603@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=alex.williamson@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=mst@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).