mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Naik, Avadhut" <avadnaik@amd.com>
To: bp@alien8.de
Cc: linux-trace-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
	tony.luck@intel.com, x86@kernel.org,
	linux-kernel@vger.kernel.org, yazen.ghannam@amd.com,
	Steven Rostedt <rostedt@goodmis.org>,
	Avadhut Naik <avadhut.naik@amd.com>
Subject: [PATCH v3 0/2] Update mce_record tracepoint
Date: Mon, 25 Mar 2024 15:12:14 -0500	[thread overview]
Message-ID: <9e68a369-2667-4dd4-b715-ca1e13948a8f@amd.com> (raw)
In-Reply-To: <20240208121013.1946ef7f@rorschach.local.home>

Hi Boris,

Can this patchset be merged in? Or would you prefer me sending out another
revision with Steven's "Reviewed-by:" tag?

On 2/8/2024 11:10, Steven Rostedt wrote:
> On Fri, 26 Jan 2024 01:57:58 -0600
> Avadhut Naik <avadhut.naik@amd.com> 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.
> 
> From a tracing POV only:
> 
> Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> 
> -- Steve

-- 
Thanks,
Avadhut Naik

  reply	other threads:[~2024-03-25 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26  7:57 Avadhut Naik
2024-01-26  7:57 ` [PATCH v3 1/2] tracing: Include PPIN in " Avadhut Naik
2024-01-26  7:58 ` [PATCH v3 2/2] tracing: Include Microcode Revision " Avadhut Naik
2024-02-08 17:10 ` [PATCH v3 0/2] Update " Steven Rostedt
2024-03-25 20:12   ` Naik, Avadhut [this message]
2024-03-25 20:31     ` Borislav Petkov
2024-03-25 21:39       ` Naik, Avadhut

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=9e68a369-2667-4dd4-b715-ca1e13948a8f@amd.com \
    --to=avadnaik@amd.com \
    --cc=avadhut.naik@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

all inboxes | Powered by JetHome®