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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQWaRAv_UvvEzhg6XFK11Gvq6Gkq_APLpbX8NDWhbi-c2w@mail.gmail.com>
Date:	Mon, 19 Oct 2015 10:00:21 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Roland Dreier <roland@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Running out of IO space because of innocuous-looking DSDT change

On Mon, Oct 19, 2015 at 9:00 AM, Roland Dreier <roland@...nel.org> wrote:
> Would it make sense to change the kernel to reduce PCIBIOS_MIN_IO in
> my case?  I could make it generic and send it upstream, or just hack
> it locally.  Or (given my ignorance of ACPI in the real world) is this
> a broken BIOS change that I should ask my BIOS vendor to revert?
> Or... ?

I would suggest to expand standard_io_resources[] to include all
possible conflict that we should avoid, like the io port for serial and cf8/cf9.

Then we could just set PCIBIOS_MIN_IO to 0 for x86.

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