From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Naga Chumbalkar <nagananda.chumbalkar@hp.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, bruce.w.allan@intel.com
Subject: Re: [RFC][PATCH]: e1000e: If ASPM L0s needs to be disabled, do it prior to enabling device
Date: Tue, 22 Mar 2011 21:08:26 -0700 [thread overview]
Message-ID: <AANLkTik0XBfbYuSa1v0v4vAdGAYXsn1c7qPpUJU593C8@mail.gmail.com> (raw)
In-Reply-To: <20110322194437.3043.97757.sendpatchset@nchumbalkar.americas.hpqcorp.net>
On Tue, Mar 22, 2011 at 12:48, Naga Chumbalkar
<nagananda.chumbalkar@hp.com> wrote:
> If ASPM L0s needs to be disabled due to HW errata, do it prior to
> "enabling" the device. This way if the kernel ever defaults its
> aspm_policy to POLICY_POWERSAVE, then the e1000e driver will get a
> chance to disable ASPM on the misbehaving device *prior* to calling
> pci_enable_device_mem(). This will be useful in situations
> where the BIOS indicates ASPM support on the server by clearing the
> ACPI FADT "ASPM Controls" bit.
>
> Note:
> The kernel (2.6.38) currently uses the BIOS "default" as its aspm_policy.
> However, Linux distros can diverge from that and set the default to "powersave".
>
> Signed-off-by: Naga Chumbalkar <nagananda.chumbalkar@hp.com>
> Cc: Bruce Allan <bruce.w.allan@intel.com>
>
> ---
> drivers/net/e1000e/82571.c | 10 +++++-----
> drivers/net/e1000e/e1000.h | 1 +
> drivers/net/e1000e/netdev.c | 25 +++++++++++++++++++++----
> 3 files changed, 27 insertions(+), 9 deletions(-)
>
I have added this patch to my queue of e1000e patches.
--
Cheers,
Jeff
prev parent reply other threads:[~2011-03-23 4:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 19:48 [RFC][PATCH]: e1000e: If ASPM L0s needs to be disabled, do it prior to enabling device Naga Chumbalkar
2011-03-22 20:16 ` Allan, Bruce W
2011-03-23 4:08 ` Jeff Kirsher [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=AANLkTik0XBfbYuSa1v0v4vAdGAYXsn1c7qPpUJU593C8@mail.gmail.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=nagananda.chumbalkar@hp.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).