From: Sohil Mehta <sohil.mehta@intel.com>
To: Avadhut Naik <avadhut.naik@amd.com>,
<linux-trace-kernel@vger.kernel.org>,
<linux-edac@vger.kernel.org>
Cc: <rostedt@goodmis.org>, <tony.luck@intel.com>, <bp@alien8.de>,
<x86@kernel.org>, <linux-kernel@vger.kernel.org>,
<yazen.ghannam@amd.com>, <avadnaik@amd.com>
Subject: Re: [PATCH v2 2/2] tracing: Include Microcode Revision in mce_record tracepoint
Date: Thu, 25 Jan 2024 13:03:06 -0800 [thread overview]
Message-ID: <1792a925-172f-4a9e-ad59-dea474bc7cda@intel.com> (raw)
In-Reply-To: <20240125184857.851355-3-avadhut.naik@amd.com>
On 1/25/2024 10:48 AM, Avadhut Naik wrote:
> Currently, the microcode field (Microcode Revision) of struct mce is not
> exported to userspace through the mce_record tracepoint.
>
> Export it through the tracepoint as it may provide useful information for
> debug and analysis.
>
> Signed-off-by: Avadhut Naik <avadhut.naik@amd.com>
> ---
A couple of nits below.
Apart from that the patch looks fine to me.
Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
> include/trace/events/mce.h | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/include/trace/events/mce.h b/include/trace/events/mce.h
> index 657b93ec8176..203baccd3c5c 100644
> --- a/include/trace/events/mce.h
> +++ b/include/trace/events/mce.h
> @@ -34,6 +34,7 @@ TRACE_EVENT(mce_record,
> __field( u8, cs )
> __field( u8, bank )
> __field( u8, cpuvendor )
> + __field( u32, microcode )
Tab alignment is inconsistent.
> ),
>
> TP_fast_assign(
> @@ -55,9 +56,10 @@ TRACE_EVENT(mce_record,
> __entry->cs = m->cs;
> __entry->bank = m->bank;
> __entry->cpuvendor = m->cpuvendor;
> + __entry->microcode = m->microcode;
> ),
>
> - TP_printk("CPU: %d, MCGc/s: %llx/%llx, MC%d: %016Lx, IPID: %016Lx, ADDR/MISC/SYND: %016Lx/%016Lx/%016Lx, RIP: %02x:<%016Lx>, TSC: %llx, PPIN: %llx, PROCESSOR: %u:%x, TIME: %llu, SOCKET: %u, APIC: %x",
> + TP_printk("CPU: %d, MCGc/s: %llx/%llx, MC%d: %016Lx, IPID: %016Lx, ADDR/MISC/SYND: %016Lx/%016Lx/%016Lx, RIP: %02x:<%016Lx>, TSC: %llx, PPIN: %llx, PROCESSOR: %u:%x, TIME: %llu, SOCKET: %u, APIC: %x, MICROCODE REVISION: %u",
Should microcode by printed as a decimal or an hexadecimal? Elsewhere
such as __print_mce(), it is printed as an hexadecimal:
/*
* Note this output is parsed by external tools and old fields
* should not be changed.
*/
pr_emerg(HW_ERR "PROCESSOR %u:%x TIME %llu SOCKET %u APIC %x
microcode %x\n",
m->cpuvendor, m->cpuid, m->time, m->socketid, m->apicid,
m->microcode);
> __entry->cpu,
> __entry->mcgcap, __entry->mcgstatus,
> __entry->bank, __entry->status,
> @@ -69,7 +71,8 @@ TRACE_EVENT(mce_record,
> __entry->cpuvendor, __entry->cpuid,
> __entry->walltime,
> __entry->socketid,
> - __entry->apicid)
> + __entry->apicid,
> + __entry->microcode)
> );
>
> #endif /* _TRACE_MCE_H */
next prev parent reply other threads:[~2024-01-25 21:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 18:48 [PATCH v2 0/2] Update mce_record tracepoint Avadhut Naik
2024-01-25 18:48 ` [PATCH v2 1/2] tracing: Include PPIN in " Avadhut Naik
2024-01-25 20:58 ` Sohil Mehta
2024-01-25 18:48 ` [PATCH v2 2/2] tracing: Include Microcode Revision " Avadhut Naik
2024-01-25 21:03 ` Sohil Mehta [this message]
2024-01-26 1:35 ` Naik, Avadhut
2024-01-25 18:58 ` [PATCH v2 0/2] Update " Borislav Petkov
2024-01-25 19:19 ` Luck, Tony
2024-01-25 20:27 ` Naik, Avadhut
2024-01-26 10:27 ` Borislav Petkov
2024-01-26 17:10 ` Luck, Tony
2024-01-26 18:56 ` Borislav Petkov
2024-01-26 19:15 ` Luck, Tony
2024-01-26 19:45 ` Borislav Petkov
2024-01-26 20:49 ` Luck, Tony
2024-01-26 21:11 ` Borislav Petkov
2024-01-26 22:01 ` Luck, Tony
2024-01-27 12:19 ` Borislav Petkov
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=1792a925-172f-4a9e-ad59-dea474bc7cda@intel.com \
--to=sohil.mehta@intel.com \
--cc=avadhut.naik@amd.com \
--cc=avadnaik@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.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