From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33011) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZpFPG-0005xT-UC for qemu-devel@nongnu.org; Thu, 22 Oct 2015 08:55:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZpFPD-00068G-OA for qemu-devel@nongnu.org; Thu, 22 Oct 2015 08:55:46 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54926) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZpFPD-00068A-Ez for qemu-devel@nongnu.org; Thu, 22 Oct 2015 08:55:43 -0400 Date: Thu, 22 Oct 2015 15:55:34 +0300 From: "Michael S. Tsirkin" Message-ID: <20151022155234-mutt-send-email-mst@redhat.com> References: <1445445464-5056-1-git-send-email-tianyu.lan@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1445445464-5056-1-git-send-email-tianyu.lan@intel.com> 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: Lan Tianyu Cc: shannon.nelson@intel.com, emil.s.tantilov@intel.com, kvm@vger.kernel.org, linux-pci@vger.kernel.org, donald.c.skidmore@intel.com, mitch.a.williams@intel.com, eddie.dong@intel.com, agraf@suse.de, qemu-devel@nongnu.org, yang.z.zhang@intel.com, nrupal.jani@intel.com, john.ronciak@intel.com, intel-wired-lan@lists.osuosl.org, jeffrey.t.kirsher@intel.com, jesse.brandeburg@intel.com, bhelgaas@google.com, pbonzini@redhat.com, carolyn.wyborny@intel.com, matthew.vick@intel.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org On Thu, Oct 22, 2015 at 12:37:32AM +0800, Lan Tianyu wrote: > This patchset is to propose a new solution to add live migration support for 82599 > SRIOV network card. > > Im our solution, we prefer to put all device specific operation into VF and > PF driver and make code in the Qemu more general. Adding code to VF driver makes sense. However, adding code to PF driver is problematic: PF and VF run within different environments, you can't assume PF and VF drivers are the same version. I guess that would be acceptable if these messages make it into the official intel spec, along with hardware registers. -- MST