[PATCH] iov: initialize NumVFs register to 0 at the end of sriov_init()

From	Ethan Zhao <ethan.zhao@oracle.com>
Newsgroups	linux.kernel
Subject	[PATCH] iov: initialize NumVFs register to 0 at the end of sriov_init()
Date	2015-08-21 12:00 +0200
Message-ID	<pZRh8-8t7-19@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

After commit 4449f079722c ("PCI: Calculate maximum number of buses
required for VFs"),the initial value of NumVFs register was set to
non-zero after sriov_init() and no VFs was enabled in device driver.
this changed the behaviour of kernel exported by lspci and sysfs etc.
so this patch initialize the NumVFs register to zero after the
calculation of max_VF_buses was done.

Tested on stable 4.1 and passed building on stable 4.2-rc7

Signed-off-by: Ethan Zhao <ethan.zhao@oracle.com>
Tested-by: Sriharsha Yadagudde <sriharsha.devdas@oracle.com>
---
 drivers/pci/iov.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
index ee0ebff..6969084 100644
--- a/drivers/pci/iov.c
+++ b/drivers/pci/iov.c
@@ -476,6 +476,7 @@ found:
 	dev->is_physfn = 1;
 	iov->max_VF_buses = virtfn_max_buses(dev);
 
+	pci_iov_set_numvfs(dev, 0);
 	return 0;
 
 failed:
-- 
1.8.3.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

[PATCH] iov: initialize NumVFs register to 0 at the end of sriov_init() Ethan Zhao <ethan.zhao@oracle.com> - 2015-08-21 12:00 +0200

csiph-web