From: Avadhut Naik <avadhut.naik@amd.com>
To: <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: [PATCH v2 0/2] Update mce_record tracepoint
Date: Thu, 25 Jan 2024 12:48:55 -0600 [thread overview]
Message-ID: <20240125184857.851355-1-avadhut.naik@amd.com> (raw)
This patchset updates the mce_record tracepoint so that the recently added
fields of struct mce are exported through it to userspace.
The first patch adds PPIN (Protected Processor Inventory Number) field to
the tracepoint.
The second patch adds the microcode field (Microcode Revision) to the
tracepoint.
Changes in v2:
- Export microcode field (Microcode Revision) through the tracepoiont in
addition to PPIN.
Avadhut Naik (2):
tracing: Include PPIN in mce_record tracepoint
tracing: Include Microcode Revision in mce_record tracepoint
include/trace/events/mce.h | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
base-commit: 0d4f19418f067465b0a84a287d9a51e443a0bc3a
--
2.34.1
next reply other threads:[~2024-01-25 18:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 18:48 Avadhut Naik [this message]
2024-01-25 18:48 ` [PATCH v2 1/2] tracing: Include PPIN in mce_record tracepoint 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
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=20240125184857.851355-1-avadhut.naik@amd.com \
--to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).