[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AE2C827.8040905@kernel.org>
Date: Sat, 24 Oct 2009 02:25:59 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
CC: "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>
Subject: [PATCH] pci: only release that resource index is less than 3
after
| commit 308cf8e13f42f476dfd6552aeff58fdc0788e566
|
| PCI: get larger bridge ranges when space is available
found one of resource of peer root bus (0x00) get released from root
resource. later one hotplug device can not get big range anymore.
other peer root buses is ok.
it turns out it is from transparent path.
those resources will be used for pci bridge BAR updated.
so need to limit it to 3.
Signed-off-by: Yinghai Lu <yinghai@...nel.org>
---
drivers/pci/setup-bus.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
Index: linux-2.6/drivers/pci/setup-bus.c
===================================================================
--- linux-2.6.orig/drivers/pci/setup-bus.c
+++ linux-2.6/drivers/pci/setup-bus.c
@@ -344,9 +344,14 @@ static struct resource *find_free_bus_re
* if there is no child under that, we should release
* and use it. don't need to reset it, pbus_size_* will
* set it again
+ * need to be less 3, otherwise can not write it to
+ * bridge, also need to avoid releasing it from
+ * transparent bus path
*/
- if (!r->child && !release_resource(r))
- return r;
+ if (i < 3 && !r->child) {
+ if (!release_resource(r))
+ return r;
+ }
}
}
return NULL;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists