Linux Perf Users
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Dapeng Mi" <dapeng1.mi@linux.intel.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [Patch v9 05/10] perf regs: Support x86 eGPRs/SSP sampling
Date: Mon, 06 Jul 2026 02:59:25 +0000	[thread overview]
Message-ID: <20260706025926.3AA051F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260706023444.3067660-6-dapeng1.mi@linux.intel.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Reclaiming XMM register space breaks explicit XMM register selection on SIMD-capable hosts.
--

commit 4a688e42468a5e89b85174c21cc87866b350369c
Author: Dapeng Mi <dapeng1.mi@linux.intel.com>

perf regs: Support x86 eGPRs/SSP sampling

This commit adds support for sampling x86 extended GP registers (R16-R31)
and the shadow stack pointer (SSP) by reclaiming the original XMM register
space. A new abi argument is introduced to distinguish the register layout,
defaulting to the new SIMD layout on supported platforms.

> diff --git a/tools/perf/util/parse-regs-options.c b/tools/perf/util/parse-regs-options.c
> --- a/tools/perf/util/parse-regs-options.c
> +++ b/tools/perf/util/parse-regs-options.c
[ ... ]
> @@ -87,14 +100,16 @@ __parse_regs(const struct option *opt, const char *str, int unset, bool intr)
>  			*p = '\0';
>  
>  		if (!strcmp(s, "?")) {
> -			list_perf_regs(stderr, mask);
> +			list_perf_regs(stderr, mask, abi);
>  			goto error;
>  		}
>  
> -		reg_mask = name_to_perf_reg_mask(s, mask);
> -		if (reg_mask == 0) {
> -			ui__warning("Unknown register \"%s\", check man page or run \"perf record %s?\"\n",
> -				s, intr ? "-I" : "--user-regs=");
> +		reg_mask = name_to_perf_reg_mask(s, mask, abi);
> +		if (reg_mask) {
> +			if (abi & PERF_SAMPLE_REGS_ABI_SIMD)
> +				opts->sample_simd_regs_enabled = 1;
> +		} else {
> +			ui__warning(warn, s, intr ? "-I" : "--user-regs=");

[Severity: Medium]
Will this change break explicit XMM register selection on SIMD-capable hosts?

Because PERF_SAMPLE_REGS_ABI_SIMD is set by default on platforms with SIMD
support, the reclaimed register space means name_to_perf_reg_mask will now map
to eGPRs instead of XMM registers. 

If a user runs an existing script that explicitly requests individual XMM
registers, such as perf record -I xmm0, won't this branch fail to match the
string, return an Unknown register warning, and break backward compatibility
for those CLI options?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260706023444.3067660-1-dapeng1.mi@linux.intel.com?part=5

  reply	other threads:[~2026-07-06  2:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  2:34 [Patch v9 00/10] Perf tools: Support eGPRs/SSP/SIMD registers sampling Dapeng Mi
2026-07-06  2:34 ` [Patch v9 01/10] perf dwarf-regs: Fix DWARF register index bounds check Dapeng Mi
2026-07-06  2:34 ` [Patch v9 02/10] perf util: Add missed fields in _attr__fprintf() and __attr_swap() Dapeng Mi
2026-07-06  2:34 ` [Patch v9 03/10] tools headers: Sync x86 headers with kernel sources Dapeng Mi
2026-07-06  2:54   ` sashiko-bot
2026-07-06  2:34 ` [Patch v9 04/10] perf headers: Sync perf_event.h/perf_regs.h with the kernel headers Dapeng Mi
2026-07-06  2:34 ` [Patch v9 05/10] perf regs: Support x86 eGPRs/SSP sampling Dapeng Mi
2026-07-06  2:59   ` sashiko-bot [this message]
2026-07-06  2:34 ` [Patch v9 06/10] perf regs: Support x86 SIMD registers sampling Dapeng Mi
2026-07-06  2:34 ` [Patch v9 07/10] perf regs: Enable dumping of SIMD registers Dapeng Mi
2026-07-06  2:55   ` sashiko-bot
2026-07-06  2:34 ` [Patch v9 08/10] perf dwarf-regs: Add SIMD/eGPRs support for x86 DWARF registers Dapeng Mi
2026-07-06  2:34 ` [Patch v9 09/10] perf tests: Add x86 eGPRs/SSP registers sampling test Dapeng Mi
2026-07-06  3:00   ` sashiko-bot
2026-07-06  2:34 ` [Patch v9 10/10] perf tests: Add SIMD " Dapeng Mi

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=20260706025926.3AA051F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=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