From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Avadhut Naik <avadhut.naik@amd.com>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yazen.ghannam@amd.com" <yazen.ghannam@amd.com>,
"avadnaik@amd.com" <avadnaik@amd.com>
Subject: Re: [PATCH v2 0/2] Update mce_record tracepoint
Date: Fri, 26 Jan 2024 19:56:49 +0100 [thread overview]
Message-ID: <20240126185649.GFZbQAccZphdW_0CkH@fat_crate.local> (raw)
In-Reply-To: <SJ1PR11MB60839509241AA98A59B78D15FC792@SJ1PR11MB6083.namprd11.prod.outlook.com>
On Fri, Jan 26, 2024 at 05:10:20PM +0000, Luck, Tony wrote:
> 12 extra bytes divided by (say) 64GB (a very small server these days, may laptop has that much)
> = 0.00000001746%
>
> We will need 57000 changes like this one before we get to 0.001% :-)
You're forgetting that those 12 bytes repeat per MCE tracepoint logged.
And there's other code which adds more 0.01% here and there, well,
because we can.
> But the key there is keeping the details of the source machine attached to
> the error record. My first contact with machine check debugging is always
> just the raw error record (from mcelog, rasdaemon, or console log).
Yes, that is somewhat sensible reason to have the PPIN together with the
MCE record.
> Knowing which microcode version was loaded on a core *at the time of
> the error* is critical.
So is the rest of the debug info you're going to need from that machine.
And yet we're not adding that to the tracepoint.
> You've spent enough time with Ashok and Thomas tweaking the Linux
> microcode driver to know that going back to the machine the next day
> to ask about microcode version has a bunch of ways to get a wrong
> answer.
Huh, what does that have to do with this?
IIUC, if someone changes something on the system, whether that is
updating microcode or swapping a harddrive or swapping memory or
whatever, that invalidates the errors reported, pretty much.
You can't put it all in the trace record, you just can't.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-01-26 18:57 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 ` [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 [this message]
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=20240126185649.GFZbQAccZphdW_0CkH@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®