Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1226401 > unrolled thread
| Started by | Ruudgoogle <netwerkforens@gmail.com> |
|---|---|
| First post | 2015-09-16 21:10 +0200 |
| Last post | 2015-09-16 21:50 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
Pcie bus enumeration and 64bit issues Ruudgoogle <netwerkforens@gmail.com> - 2015-09-16 21:10 +0200
Re: Pcie bus enumeration and 64bit issues Yinghai Lu <yinghai@kernel.org> - 2015-09-16 21:50 +0200
| From | Ruudgoogle <netwerkforens@gmail.com> |
|---|---|
| Date | 2015-09-16 21:10 +0200 |
| Subject | Pcie bus enumeration and 64bit issues |
| Message-ID | <q9qfE-4Y7-17@gated-at.bofh.it> |
Hello all, For a big system i use an external pcie enclosure. Unfortunately the bios fails to properly initialise the system. As work around i plan to start the chassis after the linux kernel has booted. This leads to some other problems i would like to discuss here/get pointers to kernel code to read. 1) the chassis adds several pcie busses, i would like to reserve a range of busnumbers at the last pcie switch in the host. Something like that seems to be done for cardbus, but not for pcie switches in general. The reason is clear: allocating big chunks of busnumbers will exhaust that resource. Looking for advice! 2) For unclear reasons the linux kernel maps the 64bit bars below 4G and that range get exhausted, how can i check if a 64bit mmio pool is present/do i need to specify it manually or should the bios indicate a range? Looking for advice as well. Ruud-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [next] | [standalone]
| From | Yinghai Lu <yinghai@kernel.org> |
|---|---|
| Date | 2015-09-16 21:50 +0200 |
| Message-ID | <q9qSm-5HH-17@gated-at.bofh.it> |
| In reply to | #1226401 |
On Wed, Sep 16, 2015 at 12:08 PM, Ruudgoogle <netwerkforens@gmail.com> wrote: > > For a big system i use an external pcie enclosure. Unfortunately the bios fails to properly initialise the system. As work around i plan to start the chassis after the linux kernel has booted. This leads to some other problems i would like to discuss here/get pointers to kernel code to read. > > 1) the chassis adds several pcie busses, i would like to reserve a range of busnumbers at the last pcie switch in the host. Something like that seems to be done for cardbus, but not for pcie switches in general. The reason is clear: allocating big chunks of busnumbers will exhaust that resource. Looking for advice! > > 2) For unclear reasons the linux kernel maps the 64bit bars below 4G and that range get exhausted, how can i check if a 64bit mmio pool is present/do i need to specify it manually or should the bios indicate a range? Looking for advice as well. > I have one patch set that would do pci busn allocation. So please check git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci-v4.3-rc1 and it also have latest resource allocation enhancement. please post boot log with "debug ignore_loglevel" along with output from lspci -vvv lspci -tv Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web