From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <dan.j.williams@intel.com>,
<linuxarm@huawei.com>, <ira.weiny@intel.com>,
<vishal.l.verma@intel.com>, <alison.schofield@intel.com>
Subject: Re: [RFC PATCH 2/2] cxl: Add tprintk support for header log hex dump
Date: Wed, 18 Jan 2023 09:43:09 +0000 [thread overview]
Message-ID: <20230118094309.0000008c@Huawei.com> (raw)
In-Reply-To: <0907017b-a620-0089-8d10-b3dc92e145ed@intel.com>
On Tue, 17 Jan 2023 11:08:26 -0700
Dave Jiang <dave.jiang@intel.com> wrote:
> On 1/13/23 8:40 AM, Jonathan Cameron wrote:
> > May not make sense in general, but very helpful when writing multiple
> > header logging support.
> >
> > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> The user logging software would be retrieving from the log data directly
> instead of parsing the trace output right? Will people visually inspect
> the formatted trace output? Useful for debugging?
Rather depends on the use case and rate of expected errors + if you are
trying to debug errors before your logging infrastructure is up.
Sure in production, likely these tracepoints would just get stored to a DB for later
querying. But in debug, I often just use the kernel parameter
to directly dump them in the main kernel log, or perf's own decoding of a trace.
The nearest equivalent to this is AER which does print the log.
https://elixir.bootlin.com/linux/v6.2-rc4/source/include/ras/ras_event.h#L337
though that uses __print_array so maybe that's a better choice.
Don't get the nice offsets though if we do that though...
I'm not fussed about this patch going upstream or not, it just makes testing
patch 1 a lot easier :)
Jonathan
>
> > ---
> > drivers/cxl/core/trace.h | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/cxl/core/trace.h b/drivers/cxl/core/trace.h
> > index 20ca2fe2ca8e..64f6ad13529d 100644
> > --- a/drivers/cxl/core/trace.h
> > +++ b/drivers/cxl/core/trace.h
> > @@ -62,10 +62,13 @@ TRACE_EVENT(cxl_aer_uncorrectable_error,
> > */
> > memcpy(__entry->header_log, hl, CXL_HEADERLOG_SIZE);
> > ),
> > - TP_printk("%s: status: '%s' first_error: '%s'",
> > + 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)
> > + show_uc_errs(__entry->first_error),
> > + __print_hex_dump("", DUMP_PREFIX_OFFSET, 32, 4,
> > + (char *)__entry->header_log,
> > + CXL_HEADERLOG_SIZE_U32, false)
> > )
> > );
> >
next prev parent reply other threads:[~2023-01-18 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 15:40 [RFC PATCH 0/2] CXL UE RAS Multiple Header Logging support Jonathan Cameron
2023-01-13 15:40 ` [RFC PATCH 1/2] cxl: RAS: Multiple header recording support Jonathan Cameron
2023-01-17 18:05 ` Dave Jiang
2023-01-13 15:40 ` [RFC PATCH 2/2] cxl: Add tprintk support for header log hex dump Jonathan Cameron
2023-01-17 18:08 ` Dave Jiang
2023-01-18 9:43 ` Jonathan Cameron [this message]
2023-01-18 15:19 ` 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=20230118094309.0000008c@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@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 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.