Re: [PATCH v5 0/7] PCI: Change assign unassigned resources per rootbus bassis

From: Yinghai Lu
Date: Fri Jun 21 2013 - 23:00:54 EST

On Fri, May 31, 2013 at 11:03 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> BenH reported that there is some assign unassigned resource problem
> in powerpc.
> It turns out after
> | commit 0c5be0cb0edfe3b5c4b62eac68aa2aa15ec681af
> | Date: Thu Feb 23 19:23:29 2012 -0800
> |
> | PCI: Retry on IORESOURCE_IO type allocations
> even the root bus does not have io port range, it will keep retrying
> to realloc with mmio.
> After checking the code, found that we bound io port and mmio fail
> path together.
> First patch fix the problem, that will not make mmio fall back to must-only
> when only have io port fail with must+optional.
> During we found the fix for that problem, found that we can separate assign
> unassigned resources to per root bus.
> that will make the code simple, also could reuse it for hotadd path.
> These patches are targeted to 3.11
> -v4: split first patch into 4 patches per Bjorn.
> -v5: drop two patches that will pass root bus resource mask after we found
> simple and less intrusive way to fix the problem.
> PCI: Don't let mmio fallback to must-only, if ioport fails with must+optional
> PCI: Don't use temp bus for pci_bus_release_bridge_resources
> PCI: Use pci_walk_bus to detect unassigned resources
> PCI: Introduce enable_local to prepare per root bus handling
> PCI: Split pci_assign_unassigned_resources to per root bus
> PCI: Enable pci bridge when it is needed
> PCI: Retry assign unassigned resources for hotadd root bus

Hi, Bjorn,

Can you put this patchset in pci/next for 3.11?

Found another pciehp will need this one two. the pcie bridge does not
have io port range and it cause mmio get clear and retry.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at