From: Ram Pai <linuxram@us.ibm.com>
To: linux-pci@vger.kernel.org
Subject: [RFC PATCH] methods to access resources of a struct pci_dev
Date: Mon, 18 Jun 2012 13:03:33 +0800 [thread overview]
Message-ID: <20120618050333.GA13469@ram-ThinkPad-T61> (raw)
PCI: methods to access resources of struct pci_dev
Currently pci_dev structure holds an array of 17 PCI resources; six base
BARs, one ROM BAR, four BRIDGE BARs, six sriov BARs. This is wasteful.
A bridge device just needs the 4 bridge resources. A non-bridge device
just needs the six base resources and one ROM resource. The sriov
resources are needed only if the device has SRIOV capability.
The pci_dev structure needs to be re-organized to avoid unnecessary
bloating. However too much code outside the pci-bus driver, assumes the
internal details of the pci_dev structure, thus making it hard to
re-organize the datastructure.
As a first step this patch provides generic methods to access the
resource structure of the pci_dev.
Once this patch is accepted, I have another 40+ patches that modify all
the files that directly access the resource structure, to use the new
methods provided in the first step.
Finally we can re-organize the resource structure in the pci_dev
structure and correspondingly update the methods.
Signed-off-by: Ram Pai <linuxram@us.ibm.com>
diff --git a/include/linux/pci.h b/include/linux/pci.h
index e444f5b..475b10d 100644
--- a/include/linux/pci.h
+++ b/include/linux/pci.h
@@ -1350,6 +1350,58 @@ static inline int pci_domain_nr(struct pci_bus *bus)
\
(pci_resource_end((dev), (bar)) - \
pci_resource_start((dev), (bar)) + 1))
+#define pci_get_std_resource(dev, bar) (((dev)->resource)+bar)
+#define pci_get_sriov_resource(dev, bar) (((dev)->resource)+bar+PCI_IOV_RESOURCES)
+#define pci_get_bridge_resource(dev, bar) (((dev)->resource)+bar+PCI_BRIDGE_RESOURCES)
+#define pci_get_rom_resource(dev) (((dev)->resource)+PCI_ROM_RESOURCE)
+#define pci_resource_number(dev, res) (res - (dev)->resource)
+
+/* code that assume the current resource layout will continue to operate */
+static inline struct resource *pci_get_resource(struct pci_dev *pdev, int bar)
+{
+ if (bar >= 0 && bar < PCI_ROM_RESOURCE)
+ return pci_get_std_resource(pdev, bar);
+ else if (bar == PCI_ROM_RESOURCE)
+ return pci_get_rom_resource(pdev);
+ else if (bar <= PCI_IOV_RESOURCE_END)
+ return pci_get_sriov_resource(pdev, bar-PCI_IOV_RESOURCES);
+ else if (bar <= PCI_BRIDGE_RESOURCE_END)
+ return pci_get_bridge_resource(pdev, bar-PCI_BRIDGE_RESOURCES);
+ else
+ return NULL;
+}
+
+#define for_each_resource(dev, res, i) \
+ for (i = 0; \
+ (res = pci_get_resource(dev, i)) || i < PCI_NUM_RESOURCES; \
+ i++)
+
+#define for_each_std_resource(dev, res, i) \
+ for (i = 0; \
+ (res = pci_get_std_resource(dev, i)) || i <= PCI_STD_RESOURCE_END; \
+ i++)
+
+#define for_each_std_and_rom_resource(dev, res, i) \
+ for (i = 0; \
+ (res = (i==PCI_ROM_RESOURCE)? pci_get_rom_resource(dev) : \
+ pci_get_std_resource(dev, i)) || \
+ i <= PCI_ROM_RESOURCE; \
+ i++)
+
+#define for_each_sriov_resource(dev, res, i) \
+ for (i = 0; \
+ (res = pci_get_sriov_resource(dev, i)) || i < PCI_SRIOV_NUM_BARS; \
+ i++)
+
+#define for_each_bridge_resource(dev, res, i) \
+ for (i = 0; \
+ (res = pci_get_bridge_resource(dev, i)) || i < PCI_BRIDGE_RESOURCE_NUM; \
+ i++)
+
+#define pci_get_res_attr(dev, bar) (((dev)->res_attr)[bar])
+#define pci_get_res_attrwc(dev, bar) (((dev)->res_attr_wc)[bar])
+#define pci_set_res_attr(dev, bar, value) (((dev)->res_attr)[bar] = value)
+#define pci_set_res_attrwc(dev, bar, value) (((dev)->res_attr_wc)[bar] = value)
/* Similar to the helpers above, these manipulate per-pci_dev
* driver-specific data. They are really just a wrapper around
next reply other threads:[~2012-06-18 5:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 5:03 Ram Pai [this message]
2012-06-18 18:30 ` [RFC PATCH] methods to access resources of a struct pci_dev Yinghai Lu
2012-06-19 1:46 ` Ram Pai
2012-06-19 2:57 ` Yinghai Lu
2012-08-15 21:25 ` Bjorn Helgaas
2012-08-16 3:26 ` Ram Pai
2012-08-16 4:11 ` Yinghai Lu
2012-08-16 4:41 ` Ram Pai
2012-08-21 15:13 ` [RFC PATCH v2 ]pci: pci resource iterator Ram Pai
2012-08-21 23:22 ` Yinghai Lu
2012-08-22 10:15 ` Ram Pai
2012-08-22 17:31 ` Yinghai Lu
2012-08-22 17:35 ` Yinghai Lu
2012-08-23 0:28 ` Yinghai Lu
2012-08-23 5:09 ` [RFC PATCH v3 " Ram Pai
2012-08-23 19:30 ` Yinghai Lu
2012-08-27 7:33 ` Ram Pai
2012-09-03 8:07 ` Yinghai Lu
2012-09-03 9:08 ` Ram Pai
2012-09-03 18:20 ` Yinghai Lu
2012-09-04 3:27 ` Ram Pai
2012-09-18 0:03 ` Yinghai Lu
2012-09-21 6:18 ` Ram Pai
2012-09-21 6:27 ` Yinghai Lu
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=20120618050333.GA13469@ram-ThinkPad-T61 \
--to=linuxram@us.ibm.com \
--cc=linux-pci@vger.kernel.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 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).