From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35049) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZpFUc-0002r2-EM for qemu-devel@nongnu.org; Thu, 22 Oct 2015 09:01:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZpFUP-0000hk-UF for qemu-devel@nongnu.org; Thu, 22 Oct 2015 09:01:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56168) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZpFUP-0000hg-Op for qemu-devel@nongnu.org; Thu, 22 Oct 2015 09:01:05 -0400 Message-ID: <1445518861.4059.869.camel@redhat.com> From: Alex Williamson Date: Thu, 22 Oct 2015 07:01:01 -0600 In-Reply-To: <20151022123252.GA19940@redhat.com> References: <1445445464-5056-1-git-send-email-tianyu.lan@intel.com> <1445455227.4059.867.camel@redhat.com> <20151022123252.GA19940@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: emil.s.tantilov@intel.com, kvm@vger.kernel.org, linux-pci@vger.kernel.org, qemu-devel@nongnu.org, Jesse Brandeburg , carolyn.wyborny@intel.com, "Skidmore, Donald C" , agraf@suse.de, matthew.vick@intel.com, intel-wired-lan@lists.osuosl.org, Jeff Kirsher , yang.z.zhang@intel.com, Or Gerlitz , Mitch Williams , nrupal.jani@intel.com, bhelgaas@google.com, Lan Tianyu , Linux Netdev List , Shannon Nelson , eddie.dong@intel.com, Linux Kernel , john.ronciak@intel.com, Paolo Bonzini On Thu, 2015-10-22 at 15:32 +0300, Michael S. Tsirkin wrote: > On Wed, Oct 21, 2015 at 01:20:27PM -0600, Alex Williamson wrote: > > The trouble here is that the VF needs to be unplugged prior to the start > > of migration because we can't do effective dirty page tracking while the > > device is connected and doing DMA. > > That's exactly what patch 12/12 is trying to accomplish. > > I do see some problems with it, but I also suggested some solutions. I was replying to: > So... what would you expect service down wise for the following > solution which is zero touch and I think should work for any VF > driver: And then later note: "Here it's done via an enlightened guest driver."