All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Tai <thomas.tai@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, mr.nuke.me@gmail.com
Subject: Re: [PATCH V3 1/1] PCI/AER: add pcie TLP header information in the tracepoint
Date: Wed, 9 May 2018 10:12:42 -0400	[thread overview]
Message-ID: <f3248367-f702-2dba-5406-a1ba275e198a@oracle.com> (raw)
In-Reply-To: <20180509083814.149e8d8f@gandalf.local.home>



On 2018-05-09 08:38 AM, Steven Rostedt wrote:
> On Tue,  8 May 2018 19:04:56 -0400
> Thomas Tai <thomas.tai@oracle.com> wrote:
> 
>> When a PCIe AER occurs, the TLP header information is
>> printed in the kernel message but it is missing from
>> the tracepoint. A userspace program can use this information
>> in the tracepoint to better analyze problems.
>>
>> To enable the tracepoint:
>> echo 1 > /sys/kernel/debug/tracing/events/ras/aer_event/enable
>>
>> Example tracepoint output:
>> cat /sys/kernel/debug/tracing/trace
>> aer_event: 0000:01:00.0
>> PCIe Bus Error: severity=Uncorrected, non-fatal, Completer Abort
>> TLP Header={0x0,0x1,0x2,0x3}
>>
>> Signed-off-by: Thomas Tai <thomas.tai@oracle.com>
>> ---
> 
> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

Thank you very much Steven.

-Thomas

> 
> -- Steve
> 

  reply	other threads:[~2018-05-09 14:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 23:04 [PATCH V3 0/1] PCI/AER: add pcie TLP header information in the tracepoint Thomas Tai
2018-05-08 23:04 ` [PATCH V3 1/1] " Thomas Tai
2018-05-09 12:38   ` Steven Rostedt
2018-05-09 14:12     ` Thomas Tai [this message]
2018-05-10 13:37   ` Bjorn Helgaas
2018-05-10 13:47     ` Thomas Tai

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=f3248367-f702-2dba-5406-a1ba275e198a@oracle.com \
    --to=thomas.tai@oracle.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mr.nuke.me@gmail.com \
    --cc=rostedt@goodmis.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.