From: Bjorn Helgaas <helgaas@kernel.org>
To: Ian Kumlien <ian.kumlien@gmail.com>
Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>,
linux-pci <linux-pci@vger.kernel.org>,
Alexander Duyck <alexander.duyck@gmail.com>,
"Saheed O. Bolarinwa" <refactormyself@gmail.com>,
Puranjay Mohan <puranjay12@gmail.com>
Subject: Re: [PATCH] Use maximum latency when determining L1 ASPM
Date: Wed, 14 Oct 2020 09:36:46 -0500 [thread overview]
Message-ID: <20201014143646.GA3946160@bjorn-Precision-5520> (raw)
In-Reply-To: <CAA85sZsnMd3SdnH2bchxfkR7_Ka1wDvu9Z592uaK3FFm4rszTw@mail.gmail.com>
On Wed, Oct 14, 2020 at 03:33:17PM +0200, Ian Kumlien wrote:
> I'm actually starting to think that reporting what we do with the
> latency bit could
> be beneficial - i.e. report which links have their L1 disabled due to
> which device...
>
> I also think that this could benefit debugging - I have no clue of how
> to read the lspci:s - I mean i do see some differences that might be
> the fix but nothing really specific without a proper message in
> dmesg....
Yeah, might be worth doing. Probably pci_dbg() since I think it would
be too chatty to be enabled all the time.
next prev parent reply other threads:[~2020-10-14 14:36 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 13:28 [PATCH] Use maximum latency when determining L1 ASPM Ian Kumlien
2020-10-08 4:20 ` Kai-Heng Feng
2020-10-08 16:13 ` Bjorn Helgaas
2020-10-12 10:20 ` Ian Kumlien
2020-10-14 8:34 ` Kai-Heng Feng
2020-10-14 13:33 ` Ian Kumlien
2020-10-14 14:36 ` Bjorn Helgaas [this message]
2020-10-14 15:39 ` Ian Kumlien
2020-10-16 14:53 ` Ian Kumlien
2020-10-16 21:28 ` Bjorn Helgaas
2020-10-16 22:41 ` Ian Kumlien
2020-10-18 11:35 ` Ian Kumlien
2020-10-22 15:37 ` Bjorn Helgaas
2020-10-22 15:41 ` Ian Kumlien
2020-10-22 18:30 ` Bjorn Helgaas
2020-10-24 20:55 ` [PATCH 1/3] PCI/ASPM: Use the path max in L1 ASPM latency check Ian Kumlien
2020-10-24 20:55 ` [PATCH 2/3] PCI/ASPM: Fix L0s max " Ian Kumlien
2020-11-15 21:49 ` Ian Kumlien
2020-10-24 20:55 ` [PATCH 3/3] [RFC] PCI/ASPM: Print L1/L0s latency messages per endpoint Ian Kumlien
2020-11-15 21:49 ` [PATCH 1/3] PCI/ASPM: Use the path max in L1 ASPM latency check Ian Kumlien
2020-12-07 11:04 ` Ian Kumlien
2020-12-12 23:47 ` Bjorn Helgaas
2020-12-13 21:39 ` Ian Kumlien
2020-12-14 5:44 ` Bjorn Helgaas
2020-12-14 5:44 ` [Intel-wired-lan] " Bjorn Helgaas
2020-12-14 9:14 ` Ian Kumlien
2020-12-14 9:14 ` [Intel-wired-lan] " Ian Kumlien
2020-12-14 14:02 ` Bjorn Helgaas
2020-12-14 14:02 ` [Intel-wired-lan] " Bjorn Helgaas
2020-12-14 15:47 ` Ian Kumlien
2020-12-14 15:47 ` [Intel-wired-lan] " Ian Kumlien
2020-12-14 19:19 ` Bjorn Helgaas
2020-12-14 19:19 ` [Intel-wired-lan] " Bjorn Helgaas
2020-12-14 22:56 ` Ian Kumlien
2020-12-14 22:56 ` [Intel-wired-lan] " Ian Kumlien
2020-12-15 0:40 ` Bjorn Helgaas
2020-12-15 0:40 ` [Intel-wired-lan] " Bjorn Helgaas
2020-12-15 13:09 ` Ian Kumlien
2020-12-15 13:09 ` [Intel-wired-lan] " Ian Kumlien
2020-12-16 0:08 ` Bjorn Helgaas
2020-12-16 0:08 ` [Intel-wired-lan] " Bjorn Helgaas
2020-12-16 11:20 ` Ian Kumlien
2020-12-16 11:20 ` [Intel-wired-lan] " Ian Kumlien
2020-12-16 23:21 ` Bjorn Helgaas
2020-12-16 23:21 ` [Intel-wired-lan] " Bjorn Helgaas
2020-12-17 23:37 ` Ian Kumlien
2020-12-17 23:37 ` [Intel-wired-lan] " Ian Kumlien
2021-01-12 20:42 ` Bjorn Helgaas
2021-01-28 12:41 ` Ian Kumlien
2021-02-24 22:19 ` Ian Kumlien
2021-02-25 22:03 ` Bjorn Helgaas
2021-04-26 14:36 ` Ian Kumlien
2021-04-28 21:15 ` Bjorn Helgaas
2021-05-15 11:52 ` Ian Kumlien
-- strict thread matches above, loose matches on Subject: below --
2020-07-27 21:30 [PATCH] Use maximum latency when determining L1 ASPM Ian Kumlien
2020-07-29 22:27 ` Bjorn Helgaas
2020-07-29 22:43 ` Ian Kumlien
2020-07-26 22:06 Ian Kumlien
2020-07-26 22:06 ` Ian Kumlien
2020-07-27 21:17 ` Ian Kumlien
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=20201014143646.GA3946160@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=ian.kumlien@gmail.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-pci@vger.kernel.org \
--cc=puranjay12@gmail.com \
--cc=refactormyself@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.