From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Marciniszyn\, Mike" <mike.marciniszyn@intel.com>, "Dalessandro\,
Dennis" <dennis.dalessandro@intel.com>,
Doug Ledford <dledford@redhat.com>, "Hefty\,
Sean" <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
"linux-rdma\@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci\@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: hfi1 use of PCI internals
Date: Thu, 16 Jun 2016 14:48:30 -0400 [thread overview]
Message-ID: <tnm1toa71hsw1.fsf@phwtpriv05.ph.intel.com> (raw)
In-Reply-To: <20160616162052.GA2144@localhost> (Bjorn Helgaas's message of "Thu, 16 Jun 2016 10:20:52 -0600")
On Thu, Jun 16 2016 at 12:20:52 PM, Bjorn Helgaas <helgaas@kernel.org> wrote:
> I noticed drivers/infiniband/hw/hfi1 got moved from staging to
> drivers/ for v4.7. It does a bunch of grubbing around in PCIe ASPM
> configuration, e.g., see drivers/infiniband/hw/hfi1/aspm.h.
>
> I know there have been lots of ASPM issues, both hardware problems and
> Linux kernel problems, but it is *supposed* to be manageable by the
> core, without special driver support. What's the justification for
> having to do this in the hfi1 driver?
The description for commit affa48de84 "staging/rdma/hfi1: Add support
for enabling/disabling PCIe ASPM" anticipates this question and
describes why this was done in the hfi1 driver:
Finally, the kernel ASPM API is not used in this patch. This is
because this patch does several non-standard things as SW
workarounds for HW issues. As mentioned above, it enables ASPM even
when advertised actual latencies are greater than acceptable
latencies. Also, whereas the kernel API only allows drivers to
disable ASPM from driver probe, this patch enables/disables ASPM
directly from interrupt context. Due to these reasons the kernel
ASPM API was not used.
next prev parent reply other threads:[~2016-06-16 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 16:20 Bjorn Helgaas
2016-06-16 18:48 ` Ashutosh Dixit [this message]
2016-06-16 20:08 ` Bjorn Helgaas
2016-06-17 13:58 ` Dennis Dalessandro
2016-06-17 22:05 ` Ashutosh Dixit
2016-06-17 23:04 ` Bjorn Helgaas
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=tnm1toa71hsw1.fsf@phwtpriv05.ph.intel.com \
--to=ashutosh.dixit@intel.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=sean.hefty@intel.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
Powered by JetHome