linux-kernel - Pcie bus enumeration and 64bit issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <EC5A38AB-1EEF-4989-8ED3-F539FF486509@gmail.com>
Date:	Wed, 16 Sep 2015 21:08:43 +0200
From:	Ruudgoogle <netwerkforens@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Pcie bus enumeration and 64bit issues

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/