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]
Message-ID: <20100702161346.78896982@virtuousgeek.org>
Date:	Fri, 2 Jul 2010 16:13:46 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Matthew Garrett <mjg@...hat.com>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	lrodriguez@...eros.com, maximlevitsky@...il.com
Subject: Re: [PATCH] PCI: Default PCIe ASPM control to on and require
 !EMBEDDED to disable

On Tue, 22 Jun 2010 17:03:03 -0400
Matthew Garrett <mjg@...hat.com> wrote:

> The CONFIG_PCIEASPM option is confusing and potentially dangerous. ASPM is
> a hardware mediated feature rather than one under direct OS control, and
> even if the config option is disabled the system firmware may have turned
> on ASPM on various bits of hardware. This can cause problems later -
> various hardware that claims to support ASPM does a poor job of it and may
> hang or cause other difficulties. The kernel is able to recognise this in
> many cases and disable the ASPM functionality, but only if CONFIG_PCIEASPM
> is enabled.
> 
> Given that in its default configuration this option will either leave the
> hardware as it was originally or disable hardware functionality that may
> cause problems, it should by default y. The only reason to disable it
> ought to be to reduce code size, so make it dependent on CONFIG_EMBEDDED.
> 
> Signed-off-by: Matthew Garrett <mjg@...hat.com>
> Cc: lrodriguez@...eros.com
> Cc: maximlevitsky@...il.com
> ---
>  drivers/pci/pcie/Kconfig |   20 ++++++++++++++------
>  1 files changed, 14 insertions(+), 6 deletions(-)
> 

Applied to my linux-next branch, thanks.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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