[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5655DB99.3040007@intel.com>
Date: Thu, 26 Nov 2015 00:02:33 +0800
From: "Lan, Tianyu" <tianyu.lan@...el.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: a.motakis@...tualopensystems.com, alex.williamson@...hat.com,
b.reynal@...tualopensystems.com, bhelgaas@...gle.com,
carolyn.wyborny@...el.com, donald.c.skidmore@...el.com,
eddie.dong@...el.com, nrupal.jani@...el.com, agraf@...e.de,
kvm@...r.kernel.org, pbonzini@...hat.com, qemu-devel@...gnu.org,
emil.s.tantilov@...el.com, gerlitz.or@...il.com,
mark.d.rustad@...el.com, eric.auger@...aro.org,
intel-wired-lan@...ts.osuosl.org, jeffrey.t.kirsher@...el.com,
jesse.brandeburg@...el.com, john.ronciak@...el.com,
linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
matthew.vick@...el.com, mitch.a.williams@...el.com,
netdev@...r.kernel.org, shannon.nelson@...el.com,
weiyang@...ux.vnet.ibm.com, zajec5@...il.com
Subject: Re: [RFC PATCH V2 3/3] Ixgbevf: Add migration support for ixgbevf
driver
On 11/25/2015 8:28 PM, Michael S. Tsirkin wrote:
> Frankly, I don't really see what this short term hack buys us,
> and if it goes in, we'll have to maintain it forever.
>
The framework of how to notify VF about migration status won't be
changed regardless of stopping VF or not before doing migration.
We hope to reach agreement on this first. Tracking dirty memory still
need to more discussions and we will continue working on it. Stop VF may
help to work around the issue and make tracking easier.
> Also, assuming you just want to do ifdown/ifup for some reason, it's
> easy enough to do using a guest agent, in a completely generic way.
>
Just ifdown/ifup is not enough for migration. It needs to restore some
PCI settings before doing ifup on the target machine
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists