From: Myron Stowe <myron.stowe@redhat.com>
To: jbarnes@virtuousgeek.org
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] PCI: Convert maintaining FW-assigned BIOS BAR values to a list of temporary entries
Date: Wed, 09 Nov 2011 17:43:39 -0700 [thread overview]
Message-ID: <20111110004339.5866.28478.stgit@amt.stowe> (raw)
In commit 58c84eda075 functionality was introduced that tries to reinstate
the original, FW-assigned, BAR addresses of a PCI device when normal
resource assignment attempts fail. To keep track of the BIOS BAR
addresses, struct pci_dev was augmented with an array to hold the BAR
addresses of the PCI device: 'resource_size_t
fw_addr[DEVICE_COUNT_RESOURCE]'.
The reinstatement of BAR addresses is an uncommon event leaving the
'fw_addr' array unused normally. As the use of struct pci_dev is so
prevalent, this seems wasteful.
This patch series introduces a stand alone data structure and
corresponding set of interfacing routines, converting the underlying
aspects of the existing maintanence scheme to a list of temporary BIOS
BAR value entries instead.
---
Myron Stowe (3):
x86/PCI: Convert maintaining FW-assigned BIOS BAR values to use a list
PCI: Maintain a list of FW-assigned BIOS BAR values
PCI: Fix starting basis for resource requests
arch/x86/pci/i386.c | 2 -
drivers/pci/setup-res.c | 100 ++++++++++++++++++++++++++++++++++++++++++-----
include/linux/pci.h | 2 -
3 files changed, 92 insertions(+), 12 deletions(-)
--
next reply other threads:[~2011-11-10 0:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 0:43 Myron Stowe [this message]
2011-11-10 0:43 ` [PATCH 1/3] PCI: Fix starting basis for resource requests Myron Stowe
2011-11-10 0:43 ` [PATCH 2/3] PCI: Maintain a list of FW-assigned BIOS BAR values Myron Stowe
2011-11-11 17:45 ` Jesse Barnes
2011-11-14 17:47 ` Myron Stowe
2011-11-10 0:43 ` [PATCH 3/3] x86/PCI: Convert maintaining FW-assigned BIOS BAR values to use a list Myron Stowe
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=20111110004339.5866.28478.stgit@amt.stowe \
--to=myron.stowe@redhat.com \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome