From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Matthew Garrett <mjg@redhat.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
lrodriguez@atheros.com, maximlevitsky@gmail.com
Subject: Re: [PATCH] PCI: Default PCIe ASPM control to on and require !EMBEDDED to disable
Date: Fri, 2 Jul 2010 16:13:46 -0700 [thread overview]
Message-ID: <20100702161346.78896982@virtuousgeek.org> (raw)
In-Reply-To: <1277240583-5607-1-git-send-email-mjg@redhat.com>
On Tue, 22 Jun 2010 17:03:03 -0400
Matthew Garrett <mjg@redhat.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@redhat.com>
> Cc: lrodriguez@atheros.com
> Cc: maximlevitsky@gmail.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
prev parent reply other threads:[~2010-07-02 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 21:03 Matthew Garrett
2010-07-02 23:13 ` Jesse Barnes [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100702161346.78896982@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=maximlevitsky@gmail.com \
--cc=mjg@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®