From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53313) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZqEOd-0000cI-PQ for qemu-devel@nongnu.org; Sun, 25 Oct 2015 02:03:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZqEOZ-0004hG-OU for qemu-devel@nongnu.org; Sun, 25 Oct 2015 02:03:11 -0400 Received: from mail-pa0-x235.google.com ([2607:f8b0:400e:c03::235]:33577) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZqEOZ-0004h3-I5 for qemu-devel@nongnu.org; Sun, 25 Oct 2015 02:03:07 -0400 Received: by pacfa8 with SMTP id fa8so381951pac.0 for ; Sat, 24 Oct 2015 23:03:06 -0700 (PDT) References: <1445445464-5056-1-git-send-email-tianyu.lan@intel.com> <1445445464-5056-6-git-send-email-tianyu.lan@intel.com> <5627FB20.3020003@gmail.com> <562BA729.10903@intel.com> From: Alexander Duyck Message-ID: <562C7098.4030406@gmail.com> Date: Sat, 24 Oct 2015 23:03:04 -0700 MIME-Version: 1.0 In-Reply-To: <562BA729.10903@intel.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC Patch 05/12] IXGBE: Add new sysfs interface of "notify_vf" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Lan, Tianyu" , bhelgaas@google.com, carolyn.wyborny@intel.com, donald.c.skidmore@intel.com, eddie.dong@intel.com, nrupal.jani@intel.com, yang.z.zhang@intel.com, agraf@suse.de, kvm@vger.kernel.org, pbonzini@redhat.com, qemu-devel@nongnu.org, emil.s.tantilov@intel.com, intel-wired-lan@lists.osuosl.org, jeffrey.t.kirsher@intel.com, jesse.brandeburg@intel.com, john.ronciak@intel.com, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, matthew.vick@intel.com, mitch.a.williams@intel.com, netdev@vger.kernel.org, shannon.nelson@intel.com On 10/24/2015 08:43 AM, Lan, Tianyu wrote: > > On 10/22/2015 4:52 AM, Alexander Duyck wrote: >> Also have you even considered the MSI-X configuration on the VF? I >> haven't seen anything anywhere that would have migrated the VF's MSI-X >> configuration from BAR 3 on one system to the new system. > > MSI-X migration is done by Hypervisor(Qemu). > Following link is my Qemu patch to do that. > http://marc.info/?l=kvm&m=144544706530484&w=2 I really don't like the idea of trying to migrate the MSI-X across from host to host while it is still active. I really think Qemu shouldn't be moving this kind of data over in a migration. I think that having the VF do a suspend/resume is the best way to go. Then it simplifies things as all you have to deal with is the dirty page tracking for the Rx DMA and you should be able to do this without making things too difficult. - Alex