From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Anirban Chakraborty <abchak@juniper.net>
Subject: Re: xl/SR-IOV: disposition of VFs when PF disappears?
Date: Tue, 28 Oct 2014 10:00:29 -0400 [thread overview]
Message-ID: <20141028140029.GC21290@laptop.dumpdata.com> (raw)
In-Reply-To: <544F7D310200007800042BC2@mail.emea.novell.com>
On Tue, Oct 28, 2014 at 10:25:37AM +0000, Jan Beulich wrote:
> >>> On 27.10.14 at 19:07, <konrad.wilk@oracle.com> 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
>
next prev parent reply other threads:[~2014-10-28 14:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 12:36 xl/SR-IOV: disposition of VFs when PF disappears? Jan Beulich
2014-10-27 12:57 ` Ian Campbell
2014-10-27 13:07 ` Jan Beulich
2014-10-27 13:35 ` Konrad Rzeszutek Wilk
2014-10-27 17:53 ` Anirban Chakraborty
2014-10-27 17:57 ` Stefano Stabellini
2014-10-27 18:07 ` Konrad Rzeszutek Wilk
2014-10-27 19:53 ` Anirban Chakraborty
2014-10-28 10:25 ` Jan Beulich
2014-10-28 14:00 ` Konrad Rzeszutek Wilk [this message]
2014-10-28 15:18 ` Jan Beulich
2014-10-28 16:25 ` Jan Beulich
2014-10-28 16:30 ` Jan Beulich
2014-10-28 16:56 ` Konrad Rzeszutek Wilk
2014-10-29 7:45 ` Jan Beulich
2014-10-27 13:03 ` Andrew Cooper
2014-10-27 13:12 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141028140029.GC21290@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=abchak@juniper.net \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.