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-prev] [day] [month] [year] [list]
Date:	Wed, 16 Sep 2015 12:41:26 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Ruudgoogle <netwerkforens@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Pcie bus enumeration and 64bit issues

On Wed, Sep 16, 2015 at 12:08 PM, Ruudgoogle <netwerkforens@...il.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@...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

Powered by Openwall GNU/*/Linux Powered by OpenVZ