linux-kernel - Re: [git pull] PCI changes

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]

Date:	Wed, 11 Jan 2012 19:38:25 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Matthew Garrett <mjg@...hat.com>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [git pull] PCI changes

On Wed, Jan 11, 2012 at 10:34 AM, Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
>
> Matthew Garrett (1):
>      PCI: Rework ASPM disable code

Yay.

However, looking this through some more, I'm still a bit confused by
the pcie_clear_aspm() call in acpi_pci_root_add().

It seems to be explicitly against the rules elsewhere - we clear ASPM
even though ACPI_FADT_NO_ASPM is set - which the changelog (and the
other parts of that commit) says means "don't touch pre-existing ASPM
state").

So why is acpi_pci_root_add() special? Cna you explain that part to me?

                    Linus
--
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/