From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48288) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1cWv-0005hn-AS for qemu-devel@nongnu.org; Wed, 25 Nov 2015 11:02:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a1cWs-0001g7-3D for qemu-devel@nongnu.org; Wed, 25 Nov 2015 11:02:49 -0500 Received: from mga11.intel.com ([192.55.52.93]:57099) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1cWr-0001fb-TG for qemu-devel@nongnu.org; Wed, 25 Nov 2015 11:02:46 -0500 References: <1448372298-28386-1-git-send-email-tianyu.lan@intel.com> <1448372298-28386-4-git-send-email-tianyu.lan@intel.com> <20151124230551-mutt-send-email-mst@redhat.com> <56554994.1090305@intel.com> <20151125142437-mutt-send-email-mst@redhat.com> From: "Lan, Tianyu" Message-ID: <5655DB99.3040007@intel.com> Date: Thu, 26 Nov 2015 00:02:33 +0800 MIME-Version: 1.0 In-Reply-To: <20151125142437-mutt-send-email-mst@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH V2 3/3] Ixgbevf: Add migration support for ixgbevf driver List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: weiyang@linux.vnet.ibm.com, emil.s.tantilov@intel.com, kvm@vger.kernel.org, qemu-devel@nongnu.org, jesse.brandeburg@intel.com, mark.d.rustad@intel.com, carolyn.wyborny@intel.com, eric.auger@linaro.org, donald.c.skidmore@intel.com, zajec5@gmail.com, agraf@suse.de, matthew.vick@intel.com, intel-wired-lan@lists.osuosl.org, jeffrey.t.kirsher@intel.com, gerlitz.or@gmail.com, mitch.a.williams@intel.com, nrupal.jani@intel.com, bhelgaas@google.com, a.motakis@virtualopensystems.com, b.reynal@virtualopensystems.com, linux-api@vger.kernel.org, shannon.nelson@intel.com, eddie.dong@intel.com, alex.williamson@redhat.com, linux-kernel@vger.kernel.org, john.ronciak@intel.com, netdev@vger.kernel.org, pbonzini@redhat.com 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