From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: xl/SR-IOV: disposition of VFs when PF disappears? Date: Tue, 28 Oct 2014 10:00:29 -0400 Message-ID: <20141028140029.GC21290@laptop.dumpdata.com> References: <544E4A4E020000780004267D@mail.emea.novell.com> <1414414666.23883.13.camel@eu.citrix.com> <20141027133534.GC4050@laptop.dumpdata.com> <20141027180723.GD12989@laptop.dumpdata.com> <544F7D310200007800042BC2@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Xj7RV-00071z-1a for xen-devel@lists.xenproject.org; Tue, 28 Oct 2014 14:08:13 +0000 Content-Disposition: inline In-Reply-To: <544F7D310200007800042BC2@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Wei Liu , Stefano Stabellini , "ian.jackson@eu.citrix.com" , Ian Campbell , xen-devel , Anirban Chakraborty List-Id: xen-devel@lists.xenproject.org On Tue, Oct 28, 2014 at 10:25:37AM +0000, Jan Beulich wrote: > >>> On 27.10.14 at 19:07, wrote: > > 2). PF removal. Currently if you try to unload the PF and the VFs > > are in use (pciback owns them), the unloading will not happen. Until > > all of the VFs have been de-assigned. > > Is the "bug" here that the reporter (Intel?) wants the VFs to be > > automatically yanked out of a guest when the system admin wants to > > unload the PF? > > No. They see the VF still listed as assignable after the guest terminated > and the PF got made assignable. The PF driver unloading, however, > should trigger all VFs (which are about to disappear) to get removed > from pciback. I hope to find some time later today to look into why (if > at all) this isn't happening right now. That is due to PCI_DEV_FLAGS_ASSIGNED being set on the PF device which inhibits it from unloading until that flag has been cleared. That is odd that Intel is reporting it to you as Intel added that flag as part of the SR-IOV NICs to inhibit the PF unloading when VFs are still in-use. > > Jan >