All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Matt Turner" <mattst88@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf regs: Add alpha support
Date: Sun, 11 Oct 2026 20:42:41 +0000	[thread overview]
Message-ID: <sashiko-outbox-167456@kernel.org> (raw)
In-Reply-To: <20261011-alpha-perf-tools-regs-v1-1-2a5940e22548@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] perf: missing POSIX header inclusions in perf_regs_alpha.c
--

commit fd8853fd5c4e09ccccf58c76fbab7cdfcce13a97
Author: Matt Turner <mattst88@gmail.com>

perf regs: Add alpha support

Add the alpha perf register tables so that -I/--user-regs and
--call-graph dwarf work. r9-r15 cannot be sampled and are left out of the
mask.

> diff --git a/tools/perf/util/perf-regs-arch/perf_regs_alpha.c b/tools/perf/util/perf-regs-arch/perf_regs_alpha.c
> new file mode 100644
> index 0000000000000..cb9c8a1cd74b9
> --- /dev/null
> +++ b/tools/perf/util/perf-regs-arch/perf_regs_alpha.c
> @@ -0,0 +1,34 @@
> +// SPDX-License-Identifier: GPL-2.0
> +
> +#include "../perf_regs.h"
> +#include "../../arch/alpha/include/perf_regs.h"

[Severity: Low]
Does this file need explicit inclusions for stdint.h, stdbool.h, and stddef.h?

The code below relies on uint64_t, bool, and NULL. Relying on implicit header
dependencies might cause build failures on systems using musl libc where these
headers are not automatically included by other subsystem headers.

> +
> +static const char * const alpha_reg_names[PERF_REG_ALPHA_MAX] = {
> +	"r0", "r1", "r2", "r3", "r4", "r5", "r6", "r7",
> +	"r8", "r9", "r10", "r11", "r12", "r13", "r14", "r15",
> +	"r16", "r17", "r18", "r19", "r20", "r21", "r22", "r23",
> +	"r24", "r25", "r26", "r27", "r28", "gp", "sp", "pc",
> +};
> +
> +uint64_t __perf_reg_mask_alpha(bool intr __maybe_unused)

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261011-alpha-perf-tools-regs-v1-1-2a5940e22548@gmail.com?part=1

  reply	other threads:[~2026-10-11 20:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11 20:37 [PATCH] perf regs: Add alpha support Matt Turner
2026-10-11 20:42 ` sashiko-bot [this message]
2026-10-11 21:46 ` Ian Rogers
2026-10-11 21:50 ` Ian Rogers
2026-10-12 17:37 ` Magnus Lindholm
2026-10-12 21:41   ` Magnus Lindholm
2026-10-12 21:45     ` Ian Rogers
2026-10-12 22:38       ` Magnus Lindholm
2026-10-12 22:46         ` Ian Rogers

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=sashiko-outbox-167456@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.