From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [RESEND Patch v10 11/23] perf/x86: Enable XMM register sampling for REGS_USER case
Date: Tue, 25 Aug 2026 09:13:11 +0800 [thread overview]
Message-ID: <662c5d2e-0c6f-4d1f-a505-b6dba2ae8a4f@linux.intel.com> (raw)
In-Reply-To: <20260824101603.6D42D1F000E9@smtp.kernel.org>
On 8/24/2026 6:16 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [High] NMI re-entrancy corrupts per-CPU `x86_user_regs` during PEBS drains
> --
>
> --- Patch [11]: [RESEND Patch v10 11/23] perf/x86: Enable XMM register sampling for REGS_USER case ---
> commit 1dabe6f859e16c09faeea0ab1b864b14dc315cd4
> Author: Dapeng Mi <dapeng1.mi@linux.intel.com>
>
> perf/x86: Enable XMM register sampling for REGS_USER case
>
> This commit adds support for XMM register sampling in the REGS_USER case.
> It introduces a per-CPU x86_user_regs variable to store REGS_USER-specific
> XMM registers to prevent overwriting by REGS_INTR-specific data. A helper
> function x86_pmu_update_user_xregs() is introduced to read these registers
> from either cached task FPU states or hardware registers.
>
>> diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
>> index 1c3e2bfa2673a..20140643e21c9 100644
>> --- a/arch/x86/events/core.c
>> +++ b/arch/x86/events/core.c
> [ ... ]
>> @@ -1832,14 +1826,129 @@ static void x86_pmu_update_regs_intr(struct perf_event *event,
>> data->sample_flags |= PERF_SAMPLE_REGS_INTR;
>> }
>>
>> +static DEFINE_PER_CPU(struct x86_perf_regs, x86_user_regs);
>> +
>> +static void x86_pmu_get_regs_user(struct perf_sample_data *data,
>> + struct pt_regs *regs)
>> +{
>> + struct x86_perf_regs *x86_regs_user = this_cpu_ptr(&x86_user_regs);
>> + struct perf_regs regs_user;
>> +
>> + x86_pmu_clear_perf_regs(&x86_regs_user->regs);
>> +
>> + perf_get_regs_user(®s_user, regs);
>> + data->regs_user.abi = regs_user.abi;
>> + if (regs_user.regs) {
>> + x86_regs_user->regs = *regs_user.regs;
>> + data->regs_user.regs = &x86_regs_user->regs;
>> + } else {
>> + data->regs_user.regs = NULL;
>> + }
>> +}
>> +
>> +/*
>> + * The x86 specific variant of perf_sample_regs_user().
>> + * Update data->regs_user fields for extended registers (e.g., SIMD).
>> + */
>> +static void x86_pmu_update_regs_user(struct perf_event *event,
>> + struct perf_sample_data *data,
>> + struct pt_regs *regs)
>> +{
>> + struct x86_perf_regs *x86_regs_user = this_cpu_ptr(&x86_user_regs);
>> + struct perf_event_attr *attr = &event->attr;
>> + struct x86_perf_regs *perf_regs;
>> +
>> + /*
>> + * PERF_SAMPLE_REGS_INTR and PERF_SAMPLE_REGS_USER can both be
>> + * requested for one event. Keep user regs in a separate x86_perf_regs
>> + * instance, so intr-reg collection does not overwrite user-reg data.
>> + */
>> + if (user_mode(regs)) {
>> + x86_pmu_clear_perf_regs(&x86_regs_user->regs);
>> + perf_regs = container_of(regs, struct x86_perf_regs, regs);
>> + /* Copy all sampled regs data to x86_regs_user. */
>> + *x86_regs_user = *perf_regs;
>> + data->regs_user.regs = &x86_regs_user->regs;
> [Severity: High]
> Does this code corrupt the un-nested per-CPU x86_user_regs during NMIs?
>
> If a context-switch PEBS drain runs with local IRQs disabled but NMIs enabled,
> a PMI (NMI) could interrupt the drain. If the PMI handler processes a perf event
> requesting REGS_USER, it will call x86_pmu_update_regs_user(), which
> unconditionally overwrites the same per-CPU x86_user_regs variable here without
> in_nmi() protection.
>
> Upon returning from the NMI, the interrupted PEBS drain would resume copying
> the now-corrupted x86_user_regs into the ring buffer, silently corrupting the
> recorded user registers.
The x86_pmu_update_regs_user() is called in two places, one is in the NMI
handler (handle_pmi_common()), which naturally prevents the NMI reentry,
the other place is in the drain_pebs() helper. The patch
https://lore.kernel.org/all/20260813064346.335458-1-dapeng1.mi@linux.intel.com/
would block the drain_pebs() helper reentry.
Thanks.
>
next prev parent reply other threads:[~2026-08-25 1:13 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 8:27 [RESEND Patch v10 00/23] Support SIMD/eGPRs/SSP registers sampling for perf Dapeng Mi
2026-08-24 8:27 ` [RESEND Patch v10 01/23] perf/x86: Move hybrid PMU initialization before x86_pmu_starting_cpu() Dapeng Mi
2026-08-24 8:44 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 02/23] perf/x86/intel: Enable large PEBS sampling for XMMs Dapeng Mi
2026-08-24 8:52 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 03/23] perf/x86/intel: Convert x86_perf_regs to per-cpu variables Dapeng Mi
2026-08-24 8:46 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 04/23] perf: Eliminate duplicate arch-specific function definitions Dapeng Mi
2026-08-24 8:44 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 05/23] perf/x86: Use x86_perf_regs in NMI handlers Dapeng Mi
2026-08-24 8:54 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 06/23] x86/fpu/xstate: Add xsaves_nmi() helper Dapeng Mi
2026-08-24 8:54 ` sashiko-bot
2026-08-25 1:03 ` Mi, Dapeng
2026-08-24 8:27 ` [RESEND Patch v10 07/23] x86/fpu: Add update_fpu_state_and_flag() helper Dapeng Mi
2026-08-24 8:47 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 08/23] perf: Move and enhance has_extended_regs() for arch-specific use Dapeng Mi
2026-08-24 8:47 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 09/23] perf/x86/intel: Centralize PERF_PMU_CAP_EXTENDED_REGS updates Dapeng Mi
2026-08-24 8:46 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 10/23] perf/x86: Enable XMM register sampling for non-PEBS events Dapeng Mi
2026-08-24 8:53 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 11/23] perf/x86: Enable XMM register sampling for REGS_USER case Dapeng Mi
2026-08-24 10:16 ` sashiko-bot
2026-08-25 1:13 ` Mi, Dapeng [this message]
2026-08-24 8:27 ` [RESEND Patch v10 12/23] perf: Add sampling support for SIMD registers Dapeng Mi
2026-08-24 8:54 ` sashiko-bot
2026-08-25 1:19 ` Mi, Dapeng
2026-08-24 8:27 ` [RESEND Patch v10 13/23] perf/x86: Support XMM sampling using sample_simd_vec_reg_* fields Dapeng Mi
2026-08-24 9:12 ` sashiko-bot
2026-08-25 1:28 ` Mi, Dapeng
2026-08-24 8:27 ` [RESEND Patch v10 14/23] perf/x86: Support YMM " Dapeng Mi
2026-08-24 8:55 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 15/23] perf/x86: Support ZMM " Dapeng Mi
2026-08-24 8:58 ` sashiko-bot
2026-08-25 1:30 ` Mi, Dapeng
2026-08-24 8:27 ` [RESEND Patch v10 16/23] perf/x86: Support OPMASK sampling using sample_simd_pred_reg_* fields Dapeng Mi
2026-08-24 8:54 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 17/23] perf: Enhance perf_reg_validate() with simd_enabled argument Dapeng Mi
2026-08-24 8:56 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 18/23] perf/x86: Support eGPRs sampling using sample_regs_* fields Dapeng Mi
2026-08-24 8:59 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 19/23] perf/x86: Support SSP " Dapeng Mi
2026-08-24 9:39 ` sashiko-bot
2026-08-25 1:34 ` Mi, Dapeng
2026-08-24 8:27 ` [RESEND Patch v10 20/23] perf/x86/intel: Support arch-PEBS based SIMD/eGPRs sampling Dapeng Mi
2026-08-24 9:09 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 21/23] perf/x86/intel: Advertise PERF_PMU_CAP_SIMD_REGS capability Dapeng Mi
2026-08-24 9:25 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 22/23] perf/x86: Activate back-to-back NMI detection for arch-PEBS induced NMIs Dapeng Mi
2026-08-24 9:06 ` sashiko-bot
2026-08-24 8:27 ` [RESEND Patch v10 23/23] perf/x86/intel: Add sanity check for PEBS record/fragment size Dapeng Mi
2026-08-24 9:08 ` sashiko-bot
2026-08-25 1:39 ` Mi, Dapeng
2026-09-01 8:55 ` [RESEND Patch v10 00/23] Support SIMD/eGPRs/SSP registers sampling for perf Mi, Dapeng
2026-09-02 11:56 ` Peter Zijlstra
2026-09-02 12:13 ` Mi, Dapeng
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=662c5d2e-0c6f-4d1f-a505-b6dba2ae8a4f@linux.intel.com \
--to=dapeng1.mi@linux.intel.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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