From: Borislav Petkov <bp@alien8.de>
To: Avadhut Naik <avadhut.naik@amd.com>
Cc: linux-trace-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
rostedt@goodmis.org, tony.luck@intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org, yazen.ghannam@amd.com,
avadnaik@amd.com
Subject: Re: [PATCH v2 0/2] Update mce_record tracepoint
Date: Thu, 25 Jan 2024 19:58:21 +0100 [thread overview]
Message-ID: <20240125185821.GDZbKvTW93APAiY1LP@fat_crate.local> (raw)
In-Reply-To: <20240125184857.851355-1-avadhut.naik@amd.com>
On Thu, Jan 25, 2024 at 12:48:55PM -0600, Avadhut Naik wrote:
> 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.
This is a lot of static information to add to *every* MCE.
And where does it end? Stick full dmesg in the tracepoint too?
What is the real-life use case here?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-01-25 18:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 18:48 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
2024-01-26 1:35 ` Naik, Avadhut
2024-01-25 18:58 ` Borislav Petkov [this message]
2024-01-25 19:19 ` [PATCH v2 0/2] Update " 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=20240125185821.GDZbKvTW93APAiY1LP@fat_crate.local \
--to=bp@alien8.de \
--cc=avadhut.naik@amd.com \
--cc=avadnaik@amd.com \
--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
all inboxes | Powered by JetHome®