From: Dave Jiang <dave.jiang@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: linux-cxl@vger.kernel.org, alison.schofield@intel.com,
vishal.l.verma@intel.com, bwidawsk@kernel.org,
dan.j.williams@intel.com, shiju.jose@huawei.com,
rrichter@amd.com, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH RFC v2 8/9] cxl/pci: add tracepoint events for CXL RAS
Date: Thu, 20 Oct 2022 10:07:30 -0700 [thread overview]
Message-ID: <d70a5bc5-2d1d-c038-fb78-b7f36a31677c@intel.com> (raw)
In-Reply-To: <20221020180235.00007320@huawei.com>
On 10/20/2022 10:02 AM, Jonathan Cameron wrote:
> On Fri, 16 Sep 2022 16:11:39 -0700
> Dave Jiang <dave.jiang@intel.com> wrote:
>
>> Add tracepoint events for recording the CXL uncorrectable and correctable
>> errors. For uncorrectable errors, there is additional data up to 512B from
>> the header log register (CXL spec rev3 8.2.4.16.7). The content of the
>> register depends on the Uncorrectable Errors (UC) register status (CXL spec
>> rev3 8.2.4.16.1). This implementation supports the Receiver_Overflow error
>> where the definition is defined as first 3 bits of the Header Log data. The
>> trace event will intake a dynamic array that will dump the Header Log data
>> based on error. If multiple errors are set in the status register, then the
>> 'first error' field (CXL spec rev3 v8.2.4.16.6) is read from the Error
>> Capabilities and Control Register in order to determine the error.
>>
>> This implementation does not include CXL IDE Error details.
>>
>> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> Given the useful review we've gotten on other race points seems wise to
> Cc Stephen.
Yes I will next rev.
>
> The overflow flags seems to be inconsistent wrt to spec. They aren't flags
> as such in the spec. However I note that isn't used anyway so maybe drop
> it for now?
Will do.
>
> Jonathan
>
>> ---
>> drivers/cxl/pci.c | 2 +
>> include/trace/events/cxl_ras.h | 117 ++++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 119 insertions(+)
>> create mode 100644 include/trace/events/cxl_ras.h
>>
>> diff --git a/drivers/cxl/pci.c b/drivers/cxl/pci.c
>> index 610b3a77f205..357de704e42c 100644
>> --- a/drivers/cxl/pci.c
>> +++ b/drivers/cxl/pci.c
>> @@ -13,6 +13,8 @@
>> #include "cxlmem.h"
>> #include "cxlpci.h"
>> #include "cxl.h"
>> +#define CREATE_TRACE_POINTS
>> +#include <trace/events/cxl_ras.h>
>>
>> /**
>> * DOC: cxl pci
>> diff --git a/include/trace/events/cxl_ras.h b/include/trace/events/cxl_ras.h
>> new file mode 100644
>> index 000000000000..6bb41c3b87c8
>> --- /dev/null
>> +++ b/include/trace/events/cxl_ras.h
>> @@ -0,0 +1,117 @@
>> +/* SPDX-License-Identifier: GPL-2.0 */
>> +#undef TRACE_SYSTEM
>> +#define TRACE_SYSTEM cxl_ras
>> +
>> +#if !defined(_CXL_RAS_EVENTS_H) || defined(TRACE_HEADER_MULTI_READ)
>> +#define _CXL_RAS_EVENTS_H
>> +
>> +#include <linux/tracepoint.h>
>> +
>> +#define CXL_RAS_UC_CACHE_DATA_PARITY BIT(0)
>> +#define CXL_RAS_UC_CACHE_ADDR_PARITY BIT(1)
>> +#define CXL_RAS_UC_CACHE_BE_PARITY BIT(2)
>> +#define CXL_RAS_UC_CACHE_DATA_ECC BIT(3)
>> +#define CXL_RAS_UC_MEM_DATA_PARITY BIT(4)
>> +#define CXL_RAS_UC_MEM_ADDR_PARITY BIT(5)
>> +#define CXL_RAS_UC_MEM_BE_PARITY BIT(6)
>> +#define CXL_RAS_UC_MEM_DATA_ECC BIT(7)
>> +#define CXL_RAS_UC_REINIT_THRESH BIT(8)
>> +#define CXL_RAS_UC_RSVD_ENCODE BIT(9)
>> +#define CXL_RAS_UC_POISON BIT(10)
>> +#define CXL_RAS_UC_RECV_OVERFLOW BIT(11)
>> +#define CXL_RAS_UC_INTERNAL_ERR BIT(14)
>> +#define CXL_RAS_UC_IDE_TX_ERR BIT(15)
>> +#define CXL_RAS_UC_IDE_RX_ERR BIT(16)
>> +
>> +#define show_uc_errs(status) __print_flags(status, " | ", \
>> + { CXL_RAS_UC_CACHE_DATA_PARITY, "Cache Data Parity Error" }, \
>> + { CXL_RAS_UC_CACHE_ADDR_PARITY, "Cache Address Parity Error" }, \
>> + { CXL_RAS_UC_CACHE_BE_PARITY, "Cache Byte Enable Parity Error" }, \
>> + { CXL_RAS_UC_CACHE_DATA_ECC, "Cache Data ECC Error" }, \
>> + { CXL_RAS_UC_MEM_DATA_PARITY, "Memory Data Parity Error" }, \
>> + { CXL_RAS_UC_MEM_ADDR_PARITY, "Memory Address Parity Error" }, \
>> + { CXL_RAS_UC_MEM_BE_PARITY, "Memory Byte Enable Parity Error" }, \
>> + { CXL_RAS_UC_MEM_DATA_ECC, "Memory Data ECC Error" }, \
>> + { CXL_RAS_UC_REINIT_THRESH, "REINIT Threshold Hit" }, \
>> + { CXL_RAS_UC_RSVD_ENCODE, "Received Unrecognized Encoding" }, \
>> + { CXL_RAS_UC_POISON, "Received Poison From Peer" }, \
>> + { CXL_RAS_UC_RECV_OVERFLOW, "Receiver Overflow" }, \
>> + { CXL_RAS_UC_INTERNAL_ERR, "Component Specific Error" }, \
>> + { CXL_RAS_UC_IDE_TX_ERR, "IDE Tx Error" }, \
>> + { CXL_RAS_UC_IDE_RX_ERR, "IDE Rx Error" } \
>> +)
>> +
>> +#define CXL_RAS_UC_OVFL_D2H_REQ BIT(0)
>> +#define CXL_RAS_UC_OVFL_D2H_RSP BIT(1)
>> +#define CXL_RAS_UC_OVFL_D2H_DATA BIT(2)
>> +#define CXL_RAS_UC_OVFL_S2M_NDR BIT(3)
>> +#define CXL_RAS_UC_OVFL_S2M_DRS BIT(4)
> Why not align these with the values in the spec?
> They aren't flags as such... Mind you not used anyway so probably just
> drop it for now?
>
>> +
>> +#define show_uc_ovfl(hl) __print_flags(hl, " | ", \
>> + { CXL_RAS_UC_OVFL_D2H_REQ, "Receiver Overflow D2H Req" }, \
>> + { CXL_RAS_UC_OVFL_D2H_RSP, "Receiver Overflow D2H Rsp" }, \
>> + { CXL_RAS_UC_OVFL_D2H_DATA, "Receiver Overflow D2H Data" }, \
>> + { CXL_RAS_UC_OVFL_S2M_NDR, "Receiver Overflow S2M NDR" }, \
>> + { CXL_RAS_UC_OVFL_S2M_DRS, "Receiver Overflow S2M DRS" } \
>> +)
>> +
>> +TRACE_EVENT(cxl_ras_uc,
>> + TP_PROTO(const char *dev_name, u32 status, u32 fe, u8 *hl, int hl_len),
>> + TP_ARGS(dev_name, status, fe, hl, hl_len),
>> + TP_STRUCT__entry(
>> + __string(dev_name, dev_name)
>> + __field(u32, status)
>> + __field(u32, first_error)
>> + __dynamic_array(u8, header_log, hl_len)
>> + __field(int, header_log_len)
>> + ),
>> + TP_fast_assign(
>> + __assign_str(dev_name, dev_name);
>> + __entry->status = status;
>> + __entry->first_error = fe;
>> + memcpy(__get_dynamic_array(header_log), hl, hl_len);
>> + __entry->header_log_len = hl_len;
>> + ),
>> + TP_printk("%s: status: '%s' first_error: '%s' header log: %s",
>> + __get_str(dev_name), show_uc_errs(__entry->status),
>> + show_uc_errs(__entry->first_error),
>> + __print_array(__get_dynamic_array(header_log), __entry->header_log_len, 1)
>> + )
>> +);
>> +
>> +#define CXL_RAS_CE_CACHE_DATA_ECC BIT(0)
>> +#define CXL_RAS_CE_MEM_DATA_ECC BIT(1)
>> +#define CXL_RAS_CE_CRC_THRESH BIT(2)
>> +#define CXL_RAS_CE_CACHE_POISON BIT(3)
>> +#define CXL_RAS_CE_MEM_POISON BIT(4)
>> +#define CXL_RAS_CE_PHYS_LAYER_ERR BIT(5)
>> +
>> +#define show_ce_errs(status) __print_flags(status, " | ", \
>> + { CXL_RAS_CE_CACHE_DATA_ECC, "Cache Data ECC Error" }, \
>> + { CXL_RAS_CE_MEM_DATA_ECC, "Memory Data Ecc Error" }, \
>> + { CXL_RAS_CE_CRC_THRESH, "CRC Threshold Hit" }, \
>> + { CXL_RAS_CE_CACHE_POISON, "Received Cache Poison From Peer" }, \
>> + { CXL_RAS_CE_MEM_POISON, "Received Memory Poison From Peer" }, \
>> + { CXL_RAS_CE_PHYS_LAYER_ERR, "Received Error From Physical Layer" } \
>> +)
>> +
>> +TRACE_EVENT(cxl_ras_ce,
>> + TP_PROTO(const char *dev_name, u32 status),
>> + TP_ARGS(dev_name, status),
>> + TP_STRUCT__entry(
>> + __string(dev_name, dev_name)
>> + __field(u32, status)
>> + ),
>> + TP_fast_assign(
>> + __assign_str(dev_name, dev_name);
>> + __entry->status = status;
>> + ),
>> + TP_printk("%s: status: '%s'",
>> + __get_str(dev_name), show_ce_errs(__entry->status)
>> + )
>> +);
>> +
>> +#endif /* _CXL_RAS_EVENTS_H */
>> +
>> +/* This part must be outside protection */
>> +#include <trace/define_trace.h>
>>
>>
next prev parent reply other threads:[~2022-10-20 17:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 23:10 [PATCH RFC v2 0/9] cxl/pci: Add fundamental error handling Dave Jiang
2022-09-16 23:11 ` [PATCH RFC v2 1/9] cxl/pci: Cleanup repeated code in cxl_probe_regs() helpers Dave Jiang
2022-09-16 23:11 ` [PATCH RFC v2 2/9] cxl/pci: Cleanup cxl_map_device_regs() Dave Jiang
2022-09-16 23:11 ` [PATCH RFC v2 3/9] cxl/pci: Kill cxl_map_regs() Dave Jiang
2022-10-18 13:43 ` Jonathan Cameron
2022-09-16 23:11 ` [PATCH RFC v2 4/9] cxl/core/regs: Make cxl_map_{component, device}_regs() device generic Dave Jiang
2022-09-16 23:11 ` [PATCH RFC v2 5/9] cxl/port: Limit the port driver to just the HDM Decoder Capability Dave Jiang
2022-10-20 16:54 ` Jonathan Cameron
2022-09-16 23:11 ` [PATCH RFC v2 6/9] cxl/pci: Prepare for mapping RAS Capability Structure Dave Jiang
2022-09-16 23:11 ` [PATCH RFC v2 7/9] cxl/pci: Find and map the " Dave Jiang
2022-09-16 23:11 ` [PATCH RFC v2 8/9] cxl/pci: add tracepoint events for CXL RAS Dave Jiang
2022-10-20 17:02 ` Jonathan Cameron
2022-10-20 17:07 ` Dave Jiang [this message]
2022-10-20 17:52 ` Steven Rostedt
2022-09-16 23:11 ` [PATCH RFC v2 9/9] cxl/pci: Add (hopeful) error handling support Dave Jiang
2022-10-20 13:45 ` Jonathan Cameron
2022-10-20 14:50 ` Dave Jiang
2022-10-20 14:03 ` Jonathan Cameron
2022-10-20 14:57 ` Dave Jiang
2022-10-20 15:52 ` Jonathan Cameron
2022-10-20 16:06 ` Dave Jiang
2022-10-20 16:11 ` Jonathan Cameron
2022-10-11 14:17 ` [PATCH RFC v2 0/9] cxl/pci: Add fundamental error handling Jonathan Cameron
2022-10-11 15:18 ` Dave Jiang
2022-10-11 17:19 ` Jonathan Cameron
2022-10-19 17:30 ` Jonathan Cameron
2022-10-19 17:38 ` Dave Jiang
2022-10-24 16:01 ` Jonathan Cameron
2022-10-25 15:22 ` Dave Jiang
2022-11-03 12:58 ` Jonathan Cameron
2022-11-03 13:27 ` Jonathan Cameron
2022-11-16 23:20 ` Dave Jiang
2022-11-17 13:50 ` Jonathan Cameron
2022-11-18 17:15 ` Dave Jiang
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=d70a5bc5-2d1d-c038-fb78-b7f36a31677c@intel.com \
--to=dave.jiang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rrichter@amd.com \
--cc=shiju.jose@huawei.com \
--cc=vishal.l.verma@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