Current we are using PCIBIOS_MAX_MEM_32 (4G limit) directly in the
pci_bus_alloc_resource to make sure that don't allocate too high
pref 64bit above 4G in the system that does not support that.

That is not right, as allocate_resource() should take resource limit.

Add pci_clip_resource() and use it check the pci bus address limit.

At last remove PCIBIOS_MAX_MEM_32.

Signed-off-by: Yinghai Lu <ying...@kernel.org>
---
 arch/x86/include/asm/pci.h |  1 -
 drivers/pci/bus.c          | 41 ++++++++++++++++++++++++++++++++++-------
 include/linux/pci.h        |  4 ----
 3 files changed, 34 insertions(+), 12 deletions(-)

diff --git a/arch/x86/include/asm/pci.h b/arch/x86/include/asm/pci.h
index 947b5c4..122c299 100644
--- a/arch/x86/include/asm/pci.h
+++ b/arch/x86/include/asm/pci.h
@@ -125,7 +125,6 @@ int setup_msi_irq(struct pci_dev *dev, struct msi_desc 
*msidesc,
 
 /* generic pci stuff */
 #include <asm-generic/pci.h>
-#define PCIBIOS_MAX_MEM_32 0xffffffff
 
 #ifdef CONFIG_NUMA
 /* Returns the node based on pci bus */
diff --git a/drivers/pci/bus.c b/drivers/pci/bus.c
index fc1b740..3ad4fd9 100644
--- a/drivers/pci/bus.c
+++ b/drivers/pci/bus.c
@@ -98,6 +98,25 @@ void pci_bus_remove_resources(struct pci_bus *bus)
        }
 }
 
+static struct pci_bus_region pci_mem_32 = {0, 0xffffffff};
+
+static void pci_clip_resource(struct resource *res, struct pci_bus *bus,
+                             struct pci_bus_region *region)
+{
+       struct pci_bus_region r;
+
+       pcibios_resource_to_bus(bus, &r, res);
+       if (r.start < region->start)
+               r.start = region->start;
+       if (r.end > region->end)
+               r.end = region->end;
+
+       if (r.end < r.start)
+               res->end = res->start - 1;
+       else
+               pcibios_bus_to_resource(bus, res, &r);
+}
+
 /**
  * pci_bus_alloc_resource - allocate a resource from a parent bus
  * @bus: PCI bus
@@ -125,15 +144,12 @@ pci_bus_alloc_resource(struct pci_bus *bus, struct 
resource *res,
 {
        int i, ret = -ENOMEM;
        struct resource *r;
-       resource_size_t max = -1;
 
        type_mask |= IORESOURCE_IO | IORESOURCE_MEM;
 
-       /* don't allocate too high if the pref mem doesn't support 64bit*/
-       if (!(res->flags & IORESOURCE_MEM_64))
-               max = PCIBIOS_MAX_MEM_32;
-
        pci_bus_for_each_resource(bus, r, i) {
+               struct resource avail;
+
                if (!r)
                        continue;
 
@@ -147,10 +163,21 @@ pci_bus_alloc_resource(struct pci_bus *bus, struct 
resource *res,
                    !(res->flags & IORESOURCE_PREFETCH))
                        continue;
 
+               /*
+                * don't allocate too high if the pref mem doesn't
+                * support 64bit.
+                */
+               avail = *r;
+               if (!(res->flags & IORESOURCE_MEM_64)) {
+                       pci_clip_resource(&avail, bus, &pci_mem_32);
+                       if (!resource_size(&avail))
+                               continue;
+               }
+
                /* Ok, try it out.. */
                ret = allocate_resource(r, res, size,
-                                       r->start ? : min,
-                                       max, align,
+                                       max(avail.start, r->start ? : min),
+                                       avail.end, align,
                                        alignf, alignf_data);
                if (ret == 0)
                        break;
diff --git a/include/linux/pci.h b/include/linux/pci.h
index da069fa..99e9040 100644
--- a/include/linux/pci.h
+++ b/include/linux/pci.h
@@ -1485,10 +1485,6 @@ static inline struct pci_dev *pci_dev_get(struct pci_dev 
*dev)
 
 #include <asm/pci.h>
 
-#ifndef PCIBIOS_MAX_MEM_32
-#define PCIBIOS_MAX_MEM_32 (-1)
-#endif
-
 /* these helpers provide future and backwards compatibility
  * for accessing popular PCI BAR info */
 #define pci_resource_start(dev, bar)   ((dev)->resource[(bar)].start)
-- 
1.8.4

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

Reply via email to