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, 19 Jan 2022 04:55:01 +0000 (GMT)
From:   "Maciej W. Rozycki" <macro@...am.me.uk>
To:     Yao Hongbo <yaohongbo@...ux.alibaba.com>
cc:     Bjorn Helgaas <helgaas@...nel.org>, bhelgaas@...gle.com,
        zhangliguang@...ux.alibaba.com,
        alikernel-developer@...ux.alibaba.com, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] PCI: Add "pci=reassign_all_bus" boot parameter

On Mon, 17 Jan 2022, Yao Hongbo wrote:

> > Why can't we make Linux smart enough to fix this by itself, without
> > forcing the user to boot with "pci=reassign_all_bus"?
> 
>    You're right, it's better for us to make pci enumeration more smart.
> 
>    But i think it's better to provide an additional option for users on ACPI systems,
> 
> which can quickly distingguish the issues between the BIOS and the OS.

 Even if so, x86 has had `pci=assign-busses' for decades already (i.e. 
from Linux 2.4.6), so why not reuse it for whatever your ACPI platform is?

  Maciej

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ