From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38676) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a4Fpt-0000DB-5q for qemu-devel@nongnu.org; Wed, 02 Dec 2015 17:25:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a4Fps-0001na-Fo for qemu-devel@nongnu.org; Wed, 02 Dec 2015 17:25:17 -0500 Received: from mx1.redhat.com ([209.132.183.28]:42892) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a4Fps-0001nV-AD for qemu-devel@nongnu.org; Wed, 02 Dec 2015 17:25:16 -0500 Message-ID: <1449095113.15753.145.camel@redhat.com> From: Alex Williamson Date: Wed, 02 Dec 2015 15:25:13 -0700 In-Reply-To: <1448372127-28115-10-git-send-email-tianyu.lan@intel.com> References: <1448372127-28115-1-git-send-email-tianyu.lan@intel.com> <1448372127-28115-10-git-send-email-tianyu.lan@intel.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH V2 09/10] Qemu/VFIO: Add SRIOV VF migration support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Lan Tianyu Cc: emil.s.tantilov@intel.com, kvm@vger.kernel.org, ard.biesheuvel@linaro.org, aik@ozlabs.ru, donald.c.skidmore@intel.com, mst@redhat.com, eddie.dong@intel.com, agraf@suse.de, quintela@redhat.com, qemu-devel@nongnu.org, blauwirbel@gmail.com, cornelia.huck@de.ibm.com, nrupal.jani@intel.com, kraxel@redhat.com, anthony@codemonkey.ws, amit.shah@redhat.com, pbonzini@redhat.com, mark.d.rustad@intel.com, lcapitulino@redhat.com, gerlitz.or@gmail.com On Tue, 2015-11-24 at 21:35 +0800, Lan Tianyu wrote: > This patch is to add SRIOV VF migration support. > Create new device type "vfio-sriov" and add faked PCI migration capability > to the type device. > > The purpose of the new capability > 1) sync migration status with VF driver in the VM > 2) Get mailbox irq vector to notify VF driver during migration. > 3) Provide a way to control injecting irq or not. > > Qemu will migrate PCI configure space regs and MSIX config for VF. > Inject mailbox irq at last stage of migration to notify VF about > migration event and wait VF driver ready for migration. VF driver > writeS PCI config reg PCI_VF_MIGRATION_VF_STATUS in the new cap table > to tell Qemu. What makes this sr-iov specific? Why wouldn't we simply extend vfio-pci with a migration=on feature? Thanks, Alex