From: Yinghai Lu <yinghai@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Guo Chao <yan@linux.vnet.ibm.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH v6 1/2] PCI: Try to allocate mem64 above 4G at first
Date: Thu, 19 Dec 2013 12:44:02 -0800 [thread overview]
Message-ID: <1387485843-17403-2-git-send-email-yinghai@kernel.org> (raw)
In-Reply-To: <1387485843-17403-1-git-send-email-yinghai@kernel.org>
On system with more pcie cards, we do not have enough range under 4G
to allocate those pci devices.
On 64bit system, we could try to allocate mem64 above 4G at first,
and fall back to below 4g if it can not find any above 4g.
-v2: update bottom assigning to make it clear for non-pae support machine.
-v3: Bjorn's change:
use MAX_RESOURCE instead of -1
use start/end instead of bottom/max
for all arch instead of just x86_64
-v4: updated after PCI_MAX_RESOURCE_32 change.
-v5: restore io handling to use PCI_MAX_RESOURCE_32 as limit.
-v6: checking pcibios_resource_to_bus return for every bus res, to decide it
if we need to try high at first.
It supports all arches instead of just x86_64.
-v7: split 4G limit change out to another patch according to Bjorn.
also use pci_clip_resource instead.
-v8: refresh after changes in pci/resource.
-v9: make second try to restart from first res of bus.
so we can ommit the patch that sort resource list of pci root bus.
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
---
drivers/pci/bus.c | 34 ++++++++++++++++++++++++----------
1 file changed, 24 insertions(+), 10 deletions(-)
diff --git a/drivers/pci/bus.c b/drivers/pci/bus.c
index 263b90c..d49e6cb 100644
--- a/drivers/pci/bus.c
+++ b/drivers/pci/bus.c
@@ -100,6 +100,9 @@ void pci_bus_remove_resources(struct pci_bus *bus)
/* The region that can be mapped by a 32-bit BAR. */
static struct pci_bus_region pci_32_bit = {0, 0xffffffff};
+/* The region that can be mapped by a 64-bit BAR above 4G */
+static struct pci_bus_region pci_64_bit = {(resource_size_t)(1ULL<<32),
+ (resource_size_t)(-1ULL)};
/*
* @res contains CPU addresses. Clip it so the corresponding bus addresses
@@ -150,10 +153,11 @@ pci_bus_alloc_resource(struct pci_bus *bus, struct resource *res,
{
int i, ret = -ENOMEM;
struct resource *r;
- resource_size_t max;
+ bool try_again = !!(res->flags & IORESOURCE_MEM_64);
type_mask |= IORESOURCE_IO | IORESOURCE_MEM;
+again:
pci_bus_for_each_resource(bus, r, i) {
struct resource avail;
@@ -170,13 +174,21 @@ pci_bus_alloc_resource(struct pci_bus *bus, struct resource *res,
!(res->flags & IORESOURCE_PREFETCH))
continue;
+ /* If this is a 64-bit BAR, try above 4G first. */
+ avail = *r;
+ if (try_again) {
+ /* res->flags has IORESOURCE_MEM_64 set */
+ pci_clip_resource_to_bus(bus, &avail, &pci_64_bit);
+ if (!resource_size(&avail))
+ continue;
+ }
+
/*
* Unless this is a 64-bit BAR, we have to clip the
* available space to the part that maps to the region of
* 32-bit bus addresses.
*/
- avail = *r;
- if (!(res->flags & IORESOURCE_MEM_64)) {
+ if (!try_again && !(res->flags & IORESOURCE_MEM_64)) {
pci_clip_resource_to_bus(bus, &avail, &pci_32_bit);
if (!resource_size(&avail))
continue;
@@ -188,17 +200,19 @@ pci_bus_alloc_resource(struct pci_bus *bus, struct resource *res,
* this is an already-configured bridge window, its start
* overrides "min".
*/
- if (avail.start)
- min = avail.start;
-
- max = avail.end;
/* Ok, try it out.. */
- ret = allocate_resource(r, res, size, min, max,
- align, alignf, alignf_data);
+ ret = allocate_resource(r, res, size, avail.start ? : min,
+ avail.end, align, alignf, alignf_data);
if (ret == 0)
- break;
+ return 0;
}
+
+ if (try_again) {
+ try_again = false;
+ goto again;
+ }
+
return ret;
}
--
1.8.4
next prev parent reply other threads:[~2013-12-19 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 20:44 [PATCH v6 0/2] PCI: allocate 64bit mmio pref Yinghai Lu
2013-12-19 20:44 ` Yinghai Lu [this message]
2013-12-19 20:44 ` [PATCH v6 2/2] PCI: Try best to allocate pref mmio 64bit above 4g Yinghai Lu
2013-12-23 0:00 ` Bjorn Helgaas
2013-12-23 1:14 ` Yinghai Lu
2014-01-08 23:34 ` Yinghai Lu
2014-01-10 9:41 ` Guo Chao
2014-01-10 17:06 ` 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=1387485843-17403-2-git-send-email-yinghai@kernel.org \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yan@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