From: sashiko-bot@kernel.org
To: "Qi Liu" <liuqi@hygon.cn>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v5 1/2] perf/x86/amd/uncore: Add Hygon uncore PMU support
Date: Tue, 18 Aug 2026 10:16:26 +0000 [thread overview]
Message-ID: <20260818101627.5424B1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260818100118.12944-2-liuqi@hygon.cn>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Removal of Hygon L3 Uncore PMU support without a replacement in the new driver.
--
--- Patch [1]: [PATCH v5 1/2] perf/x86/amd/uncore: Add Hygon uncore PMU support ---
commit 1b6dd18387bea20f9f548951bf79cae006705b47
Author: Qi Liu <liuqi@hygon.cn>
perf/x86/amd/uncore: Add Hygon uncore PMU support
This commit introduces a separate uncore PMU driver for Hygon processors to
support Data Fabric (DF) and Data Fabric IO Die (DF_IOD) counters. It also
removes the Hygon vendor checks from the AMD uncore driver to keep the
vendor-specific features separated.
> diff --git a/arch/x86/events/amd/hygon_uncore.c b/arch/x86/events/amd/hygon_uncore.c
> new file mode 100644
> index 0000000000000..471955d6fc282
> --- /dev/null
> +++ b/arch/x86/events/amd/hygon_uncore.c
[ ... ]
> +static struct hygon_uncore uncores[HYGON_UNCORE_TYPE_MAX] = {
> + /* HYGON DF */
> + {
> + .scan = hygon_uncore_df_ctx_scan,
> + .init = hygon_uncore_df_ctx_init,
> + .move = hygon_uncore_ctx_move,
> + .free = hygon_uncore_ctx_free,
> + },
> + /* HYGON DF IOD */
> + {
> + .scan = hygon_uncore_df_iod_ctx_scan,
> + .init = hygon_uncore_df_iod_ctx_init,
> + .move = hygon_uncore_ctx_move,
> + .free = hygon_uncore_ctx_free,
> + }
> +};
[ ... ]
> diff --git a/arch/x86/events/amd/uncore.c b/arch/x86/events/amd/uncore.c
> index dbc00b6dd69ee..6c486e1ab001a 100644
> --- a/arch/x86/events/amd/uncore.c
> +++ b/arch/x86/events/amd/uncore.c
[ ... ]
> @@ -1120,8 +1116,7 @@ static int __init amd_uncore_init(void)
> int ret = -ENODEV;
> int i;
>
> - if (boot_cpu_data.x86_vendor != X86_VENDOR_AMD &&
> - boot_cpu_data.x86_vendor != X86_VENDOR_HYGON)
> + if (boot_cpu_data.x86_vendor != X86_VENDOR_AMD)
> return -ENODEV;
>
> if (!boot_cpu_has(X86_FEATURE_TOPOEXT))
[Severity: Medium]
Does this inadvertently remove L3 uncore PMU support for Hygon systems?
Removing the Hygon vendor check in amd_uncore_init() prevents the AMD uncore
driver from initializing on Hygon CPUs, which previously provided L3 cache PMU
support.
Looking at the new driver in hygon_uncore.c, the uncores[] array only
implements the DF and DF_IOD components. It does not appear to provide a
replacement for the L3 cache PMU that was previously available.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260818100118.12944-1-liuqi@hygon.cn?part=1
next prev parent reply other threads:[~2026-08-18 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 10:01 [PATCH v5 0/2] perf/x86/amd/uncore: Add Hygon uncore PMU and JSON events Qi Liu
2026-08-18 10:01 ` [PATCH v5 1/2] perf/x86/amd/uncore: Add Hygon uncore PMU support Qi Liu
2026-08-18 10:16 ` sashiko-bot [this message]
2026-08-18 11:32 ` Qi Liu
2026-08-18 10:01 ` [PATCH v5 2/2] perf vendor events hygon: Add Hygon Data Fabric PMU events and metrics Qi Liu
2026-08-18 10:12 ` sashiko-bot
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=20260818101627.5424B1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=liuqi@hygon.cn \
--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.