From: "Zhoujian (jay)" <jianjay.zhou@huawei.com>
To: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>
Cc: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
zhuangshengen <zhuangshengen@huawei.com>
Subject: [Question] Any plan to support enable PCI SRIOV concurrently in kernel side?
Date: Wed, 17 Aug 2022 07:43:34 +0000 [thread overview]
Message-ID: <0a8ce5714e2d4eed909cb096d4832036@huawei.com> (raw)
Hi,
Enable SRIOV concurrently with many different PFs in userspace seems workable.
I'm trying to do it with 8 PFs(each one with 240+ VFs), but get some warnings,
here is the backtrace:
Warning 1:
---
sysfs: cannot create duplicate filename '/devices/pci0000:30/0000:30:02.0/pci_bus/0000:32'
Call Trace:
dump_stack+0x6f/0xab
sysfs_warn_dup+0x56/0x70
sysfs_create_dir_ns+0x80/0x90
kobject_add_internal+0xa0/0x2b0
kobject_add+0x71/0xd0
device_add+0x126/0x630
pci_add_new_bus+0x17c/0x4b0
pci_iov_add_virtfn+0x336/0x390
sriov_enable+0x26e/0x450
virtio_pci_sriov_configure+0x61/0xc0 [virtio_pci]
---
The reason is that different VFs may create the same pci bus number
and try to add new bus concurrently in virtfn_add_bus.
Warning 2:
---
proc_dir_entry 'pci/33' already registered
WARNING: CPU: 71 PID: 893 at fs/proc/generic.c:360 proc_register+0xf8/0x130
Call Trace:
proc_mkdir_data+0x5d/0x80
pci_proc_attach_device+0xe9/0x120
pci_bus_add_device+0x33/0x90
pci_iov_add_virtfn+0x375/0x390
sriov_enable+0x26e/0x450
virtio_pci_sriov_configure+0x61/0xc0 [virtio_pci]
---
The reason is that different VFs may create '/proc/bus/pci/bus_number'
directory using the same bus number in pci_proc_attach_device concurrently.
Mutex lock can avoid potential conflict. With the patch below the warnings above
are no longer appear.
My question is that any plan to support enable PCI SRIOV concurrently in kernel side?
Thanks
---
drivers/pci/iov.c | 29 +++++++++++++++++++++++++++--
1 file changed, 27 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
index 952217572113..6a8a849298c4 100644
--- a/drivers/pci/iov.c
+++ b/drivers/pci/iov.c
@@ -16,6 +16,12 @@
#define VIRTFN_ID_LEN 16
+static struct mutex add_bus_mutex;
+static int add_bus_mutex_initialized;
+
+static struct mutex add_device_mutex;
+static int add_device_mutex_initialized;
+
int pci_iov_virtfn_bus(struct pci_dev *dev, int vf_id)
{
if (!dev->is_physfn)
@@ -127,13 +133,24 @@ static struct pci_bus *virtfn_add_bus(struct pci_bus *bus, int busnr)
if (bus->number == busnr)
return bus;
+ if (!add_bus_mutex_initialized) {
+ mutex_init(&add_bus_mutex);
+ add_bus_mutex_initialized = 1;
+ }
+ mutex_lock(&add_bus_mutex);
+
child = pci_find_bus(pci_domain_nr(bus), busnr);
- if (child)
+ if (child) {
+ mutex_unlock(&add_bus_mutex);
return child;
+ }
child = pci_add_new_bus(bus, NULL, busnr);
- if (!child)
+ if (!child) {
+ mutex_unlock(&add_bus_mutex);
return NULL;
+ }
+ mutex_unlock(&add_bus_mutex);
pci_bus_insert_busn_res(child, busnr, busnr);
@@ -339,8 +356,16 @@ int pci_iov_add_virtfn(struct pci_dev *dev, int id)
if (rc)
goto failed1;
+ if (!add_device_mutex_initialized) {
+ mutex_init(&add_device_mutex);
+ add_device_mutex_initialized = 1;
+ }
+ mutex_lock(&add_device_mutex);
+
pci_bus_add_device(virtfn);
+ mutex_unlock(&add_device_mutex);
+
return 0;
failed1:
---
next reply other threads:[~2022-08-17 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 7:43 Zhoujian (jay) [this message]
2022-08-17 19:49 ` [Question] Any plan to support enable PCI SRIOV concurrently in kernel side? Bjorn Helgaas
2022-08-21 11:25 ` 答复: " zhuangshengen
2022-09-23 21:26 ` Bjorn Helgaas
2022-08-27 8:01 ` Zhoujian (jay)
-- strict thread matches above, loose matches on Subject: below --
2022-08-21 11:35 zhuangshengen
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=0a8ce5714e2d4eed909cb096d4832036@huawei.com \
--to=jianjay.zhou@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=zhuangshengen@huawei.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