All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajat Jain <rajatja@google.com>
To: Sinan Kaya <okaya@codeaurora.org>, jsorensen@fb.com
Cc: linux-pci <linux-pci@vger.kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci-owner@vger.kernel.org
Subject: Re: RFC: Counters for PCI Express AERs
Date: Thu, 17 May 2018 14:52:21 -0700	[thread overview]
Message-ID: <CACK8Z6F+PN=aoRaApRnG6To8JcFUUXXBok4QNS5Nziwt4We01A@mail.gmail.com> (raw)
In-Reply-To: <CACK8Z6FGxkO5JGQs3Rs2-2dtqDFnFgsmq5HT2D4nv0eGUZSg8g@mail.gmail.com>

[Fixing the new email address for Jes Sorensen now]

On Thu, May 17, 2018 at 2:48 PM, Rajat Jain <rajatja@google.com> wrote:
> [+Jes Sorensen]
>
> On Thu, May 17, 2018 at 2:25 PM,  <okaya@codeaurora.org> wrote:
>> On 2018-05-17 17:05, Rajat Jain wrote:
>>>
>>> Hello,
>>>
>>> I have been thinking about adding counters for different kinds of AERs
>>> and expose them via sysfs. IMHO this would help by giving some sense
>>> of "link quality" for PCIe links (a lot of correctable AERs may
>>> indicate system is workable, but may indicate some signal integrity
>>> issues etc). Currently, on a correctable AER, we do log them, but
>>> having them in sysfs would allow userspace tools to possibly
>>> (periodically) poll them and raise an appropriate warning in case of
>>> too many errors. I know that for my purposes, getting some idea of PCI
>>> link quality or a way to quantize it, would help.
>>>
>>> Do you think such counters make sense or would be helpful generically?
>>> Also, please let me know if something like this already exists?
>>
>>
>> This question came from FB folks last year. They were told to use the perf
>> events for counting.
>
> Thanks for the info. I think you are referring to this:
> https://linuxplumbersconf.org/2017/ocw/proposals/4803.html
>
> Jes: did anything come out of the proposal? I'm wondering if you have
> any patch that in work-in-progress that I could use may be as a
> starting point?
>
> Thanks,
>
> Rajat
>
>>
>> I don't honestly have a strong opinion.
>
> Thanks! I'd like to work on this if not already done.
>
>>
>>>
>>> Thanks,
>>>
>>> Rajat

  reply	other threads:[~2018-05-17 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 21:05 RFC: Counters for PCI Express AERs Rajat Jain
2018-05-17 21:25 ` okaya
2018-05-17 21:48   ` Rajat Jain
2018-05-17 21:52     ` Rajat Jain [this message]
2018-05-18 14:24       ` Jes Sorensen
2018-05-18 16:31         ` Rajat Jain
2018-05-23 22:20           ` Kyle McMartin

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='CACK8Z6F+PN=aoRaApRnG6To8JcFUUXXBok4QNS5Nziwt4We01A@mail.gmail.com' \
    --to=rajatja@google.com \
    --cc=bhelgaas@google.com \
    --cc=jsorensen@fb.com \
    --cc=linux-pci-owner@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=okaya@codeaurora.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 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.