From: Bjorn Helgaas <bhelgaas@google.com>
To: Casey Leedom <leedom@chelsio.com>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
Komali Katari <komali@chelsio.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"Bryant G. Ly" <bryantly@linux.vnet.ibm.com>,
Steven Royer <seroyer@linux.vnet.ibm.com>,
Juan Alvarez <jjalvare@linux.vnet.ibm.com>
Subject: Re: 4.14.0-rc3 is auto-reloading PCIe SR-IOV Virtual Function device drivers when VFs are attached to VMs ...
Date: Tue, 17 Oct 2017 14:12:45 -0500 [thread overview]
Message-ID: <CAErSpo76LN8sMS6G0oFJuo_vWUeATt6TKT3SBEJVT+mAvxe1xw@mail.gmail.com> (raw)
In-Reply-To: <MWHPR12MB1600C4F1693E88236CA8F78EC84C0@MWHPR12MB1600.namprd12.prod.outlook.com>
[+cc Alex, Bryant, Steven, Juan]
On Tue, Oct 17, 2017 at 1:36 PM, Casey Leedom <leedom@chelsio.com> wrote:
>
> Hi there,
>
> I hope this is the right Linux list for this issue. One of our QA staff
> has noticed a new behavior starting about 4.14.0-rc3. We instantiate PCIe
> SR-IOV Virtual Functions and the corresponding driver (cxgb4vf in this case)
> is automatically loaded. That's fine and has been the case for some time.
> But, we remove the driver module (rmmod cxgb4vf) and then attach one of the
> VFs to a KVM Virtual Machine and the cxgb4vf driver module gets reloaded in
> the KVM Hypervisor. This is new behavior. I see that there was a pretty
> big change done by Luis R. Rodriguez in kernel.org commit revision 2355869
> but we haven't yet isolated the new behavior to that commit. That'll be our
> next test but I wanted to get this out there for comment.
This is a good list. I don't know what commit revision 2355869 refers
to. It would be helpful if you could cite the git SHA1 for the
commit.
We're also having a conversation about the question of binding drivers
to VFs on powerpc here:
https://lkml.kernel.org/r/20170922140608.47665-3-bryantly@linux.vnet.ibm.com
It's not exactly the same issue, but you might have useful input there.
next prev parent reply other threads:[~2017-10-17 19:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 18:36 4.14.0-rc3 is auto-reloading PCIe SR-IOV Virtual Function device drivers when VFs are attached to VMs Casey Leedom
2017-10-17 19:12 ` Bjorn Helgaas [this message]
2017-10-17 19:37 ` Alex Williamson
2017-10-17 20:54 ` Casey Leedom
[not found] ` <CAB=NE6U-1ytEbL9A2FeVjcOfN3VSNAJUa9JbsQH9UfjRfANKxw@mail.gmail.com>
2017-10-18 17:09 ` Casey Leedom
2017-10-18 17:18 ` Luis R. Rodriguez
2017-10-18 17:23 ` Casey Leedom
2017-12-13 21:33 ` Casey Leedom
2017-12-13 21:47 ` Dmitry Torokhov
2017-12-13 21:54 ` Eric Dumazet
2017-12-13 22:04 ` Dmitry Torokhov
2017-12-13 22:06 ` Eric Dumazet
2017-12-13 22:12 ` Eric Dumazet
2017-12-13 22:18 ` Casey Leedom
2017-10-18 18:02 ` Bjorn Helgaas
2017-10-18 18:26 ` Casey Leedom
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=CAErSpo76LN8sMS6G0oFJuo_vWUeATt6TKT3SBEJVT+mAvxe1xw@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=alex.williamson@redhat.com \
--cc=bryantly@linux.vnet.ibm.com \
--cc=jjalvare@linux.vnet.ibm.com \
--cc=komali@chelsio.com \
--cc=leedom@chelsio.com \
--cc=linux-pci@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=seroyer@linux.vnet.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).