From: Steven Rostedt <rostedt@goodmis.org>
To: alison.schofield@intel.com
Cc: Dan Williams <dan.j.williams@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ben Widawsky <bwidawsk@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] trace, cxl: Introduce a TRACE_EVENT for CXL Poison Records
Date: Tue, 14 Jun 2022 21:15:50 -0400 [thread overview]
Message-ID: <20220614211550.335dde60@gandalf.local.home> (raw)
In-Reply-To: <32a761fe7046680a4d50762fc43988def24a4bcd.1655250669.git.alison.schofield@intel.com>
On Tue, 14 Jun 2022 17:10:26 -0700
alison.schofield@intel.com wrote:
> From: Alison Schofield <alison.schofield@intel.com>
>
> Add a trace event for CXL Poison List Media Error Records that
> includes the starting DPA of the poison, the length, and the
> the source of the poison.
>
> This trace event will be used by the CXL_MEM driver to log the
> Media Errors returned by the GET_POISON_LIST Mailbox command.
>
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> ---
> include/trace/events/cxl.h | 60 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 60 insertions(+)
> create mode 100644 include/trace/events/cxl.h
>
> diff --git a/include/trace/events/cxl.h b/include/trace/events/cxl.h
> new file mode 100644
> index 000000000000..17e707c3817e
> --- /dev/null
> +++ b/include/trace/events/cxl.h
> @@ -0,0 +1,60 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#undef TRACE_SYSTEM
> +#define TRACE_SYSTEM cxl
> +
> +#if !defined(_CXL_TRACE_H) || defined(TRACE_HEADER_MULTI_READ)
> +#define _CXL_TRACE_H
> +
> +#include <linux/tracepoint.h>
> +
> +TRACE_DEFINE_ENUM(CXL_POISON_SOURCE_UNKNOWN);
> +TRACE_DEFINE_ENUM(CXL_POISON_SOURCE_INTERNAL);
> +TRACE_DEFINE_ENUM(CXL_POISON_SOURCE_EXTERNAL);
> +TRACE_DEFINE_ENUM(CXL_POISON_SOURCE_INJECTED);
> +TRACE_DEFINE_ENUM(CXL_POISON_SOURCE_VENDOR);
> +TRACE_DEFINE_ENUM(CXL_POISON_SOURCE_INVALID);
> +
> +#define show_poison_source(source) \
> + __print_symbolic(source, \
> + {CXL_POISON_SOURCE_UNKNOWN, "UNKNOWN"}, \
> + {CXL_POISON_SOURCE_EXTERNAL, "EXTERNAL"}, \
> + {CXL_POISON_SOURCE_INTERNAL, "INTERNAL"}, \
> + {CXL_POISON_SOURCE_INJECTED, "INJECTED"}, \
> + {CXL_POISON_SOURCE_VENDOR, "VENDOR"}, \
> + {CXL_POISON_SOURCE_INVALID, "INVALID"})
> +
> +TRACE_EVENT(cxl_poison_list,
> +
> + TP_PROTO(struct device *dev,
> + int source,
> + unsigned long start,
> + unsigned int length),
> +
> + TP_ARGS(dev, source, start, length),
> +
> + TP_STRUCT__entry(
> + __string(name, dev_name(dev))
> + __field(int, source)
> + __field(u64, start)
> + __field(u32, length)
OK, the above order should be fine, without adding any holes. The
__string() is 4 bytes as well as the "int". Which keeps it aligned with the
u64 (8 bytes), followed by a u32, which is 4 bytes.
From a tracing perspective:
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
> + ),
> +
> + TP_fast_assign(
> + __assign_str(name, dev_name(dev));
> + __entry->source = source;
> + __entry->start = start;
> + __entry->length = length;
> + ),
> +
> + TP_printk("dev %s source %s start %llu length %u",
> + __get_str(name),
> + show_poison_source(__entry->source),
> + __entry->start,
> + __entry->length)
> +);
> +#endif /* _CXL_TRACE_H */
> +
> +/* This part must be outside protection */
> +#undef TRACE_INCLUDE_FILE
> +#define TRACE_INCLUDE_FILE cxl
> +#include <trace/define_trace.h>
next prev parent reply other threads:[~2022-06-15 1:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 0:10 [PATCH 0/3] CXL Poison List Retrieval & Tracing alison.schofield
2022-06-15 0:10 ` [PATCH 1/3] trace, cxl: Introduce a TRACE_EVENT for CXL Poison Records alison.schofield
2022-06-15 1:15 ` Steven Rostedt [this message]
2022-06-16 19:45 ` Davidlohr Bueso
2022-06-17 16:17 ` Jonathan Cameron
2022-06-17 18:04 ` Dan Williams
2022-06-15 0:10 ` [PATCH 2/3] cxl/mbox: Add GET_POISON_LIST mailbox command support alison.schofield
2022-06-15 3:22 ` Ira Weiny
2022-06-15 5:07 ` Alison Schofield
2022-06-15 15:01 ` Ira Weiny
2022-06-15 17:19 ` Alison Schofield
2022-06-16 19:43 ` Davidlohr Bueso
2022-06-16 20:34 ` Alison Schofield
2022-06-16 21:47 ` Davidlohr Bueso
2022-06-16 22:10 ` Alison Schofield
2022-06-16 22:20 ` Davidlohr Bueso
2022-06-16 22:45 ` Davidlohr Bueso
2022-06-16 23:15 ` Alison Schofield
2022-06-16 23:44 ` Verma, Vishal L
2022-06-17 0:03 ` Davidlohr Bueso
2022-06-17 19:02 ` Dan Williams
2022-06-20 10:53 ` Jonathan Cameron
2022-06-17 13:01 ` Jonathan Cameron
2022-06-17 14:05 ` Jonathan Cameron
2022-06-17 16:29 ` Alison Schofield
2022-06-17 17:29 ` Davidlohr Bueso
2022-06-17 19:32 ` Dan Williams
2022-06-20 10:56 ` Jonathan Cameron
2022-06-17 19:27 ` Dan Williams
2022-06-20 11:30 ` Jonathan Cameron
2022-06-17 18:26 ` Dan Williams
2022-06-15 0:10 ` [PATCH 3/3] cxl/core: Add sysfs attribute get_poison for list retrieval alison.schofield
2022-06-15 3:30 ` Ira Weiny
2022-06-16 15:04 ` Jonathan Cameron
2022-06-16 20:39 ` Alison Schofield
2022-06-17 18:42 ` Dan Williams
2022-06-18 0:21 ` Alison Schofield
2022-06-18 1:08 ` Dan Williams
2022-06-18 1:35 ` Alison Schofield
2022-06-17 17:52 ` [PATCH 0/3] CXL Poison List Retrieval & Tracing Dan Williams
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=20220614211550.335dde60@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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