linux-kernel - Re: [Bug #15124] PCI host bridge windows ignored (works with pci=use

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: <20100131024508.GA9334@srcf.ucam.org>
Date:	Sun, 31 Jan 2010 02:45:08 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Jeff Garrett <jeff@...rrett.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Myron Stowe <myron.stowe@...com>, Ingo Molnar <mingo@...e.hu>
Subject: Re: [Bug #15124] PCI host bridge windows ignored (works with
	pci=use_crs)

On Wed, Jan 27, 2010 at 09:26:02PM -0700, Bjorn Helgaas wrote:

> When ACPI is disabled, I think we just have to accept that we lose some
> functionality.  I don't see the need for alternate ways to accomplish
> everything that ACPI does.  It's becoming less and less useful to
> disable ACPI; I think it's only interesting as a debugging tool, and
> even then it's a sledgehammer.

I'd agree with this. The days where it was plausibly practical to boot 
non-ACPI operating systems on hardware are clearly gone, and people who 
are actually disabling ACPI in the field seem to be doing so in order to 
avoid other bugs - and we're failing to fix those bugs as a result.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/