On Tue, Dec 18, 2007 at 01:46:56PM -0800, Linus Torvalds wrote:
> Heh, indeed. Good catch - that
>
> Prefetchable memory behind bridge: 0000000000000000-000000000fffffff
>
> on device 00:01.0 does look totally broken, and it would make more sense
> if it matched what the device has (and what /proc/iomem resports).
Sigh. The patch was way too incomplete - I somehow missed
PCI_PREF_LIMIT_UPPER32... Corrected patch appended - I think it's
worth applying in either case since a bridge window at address 0 is
an obvious bug and this patch fixes it.
> That said, Intel bridges tend to be transparent even when they *claim*
> normal decode, so I wonder whether it actually matters in this case. But
> your patch looks very obviously right.
I don't think that transparency is the case here - I read specs for some
recent Intel chipsets and it looks like they are pretty accurate now with
a "subtractive decode" flag - over the last couple of years, at least.
There are, of course, some strange "priority decode rules", but they
can be safely ignored as far as the kernel resource management is
concerned.
> So maybe the rest of the kernel and X both already did everything right,
> and it was just this stupid bridge setup thing that was broken (and
> forcing the IOMEM resource to below the 4G mark just hid it).
I've just checked the setup-bus code and have to say that its ability to
correctly handle the 64-bit BARs is close to zero...
On the positive side, getting it right doesn't seem to be as complicated
as I thought initially - mainly because only the prefetchable memory
window of p2p bridge is 64-bit. This effectively limits >4G allocations
to prefetchable resources only.
Anyway, using PCI bus space above 4G on x86 seems to be a must these
days, and I have some spare hardware to play with. Maybe I'll be able
to get something working by mid January or so...
Ivan.
---
PCI: do respect full 64-bit address for bridge prefetch window
Prevent the prefetch window from being programmed with a bogus address
when its respective resource gets allocated above the 4G mark.
Note that we cannot yet guarantee correct resource allocations
above 4G, though it might work in some simple cases.
Signed-off-by: Ivan Kokshaysky <[email protected]>
---
drivers/pci/setup-bus.c | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
index 401e03c..643e72e 100644
--- a/drivers/pci/setup-bus.c
+++ b/drivers/pci/setup-bus.c
@@ -208,8 +208,11 @@ pci_setup_bridge(struct pci_bus *bus)
}
pci_write_config_dword(bridge, PCI_PREF_MEMORY_BASE, l);
- /* Clear out the upper 32 bits of PREF base. */
- pci_write_config_dword(bridge, PCI_PREF_BASE_UPPER32, 0);
+ /* Set up the upper 32 bits of PREF base/limit. */
+ l = region.start >> 16 >> 16;
+ pci_write_config_dword(bridge, PCI_PREF_BASE_UPPER32, l);
+ l = region.end >> 16 >> 16;
+ pci_write_config_dword(bridge, PCI_PREF_LIMIT_UPPER32, l);
pci_write_config_word(bridge, PCI_BRIDGE_CONTROL, bus->bridge_ctl);
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
