From: "Jörg Rödel" <joro@8bytes.org>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, x86@kernel.org,
dave.hansen@linux.intel.com, tglx@kernel.org, bp@alien8.de,
hpa@zytor.com, iommu@lists.linux.dev,
suravee.suthikulpanit@amd.com, sandipan.das@amd.com
Subject: Re: [PATCH] x86/events/amd/iommu: Fix cpumask of IOMMU events
Date: Mon, 27 Jul 2026 13:19:42 +0200 [thread overview]
Message-ID: <amc-s_W_TjLYnbw0@8bytes.org> (raw)
In-Reply-To: <20260517114026.6817-1-vasant.hegde@amd.com>
On Sun, May 17, 2026 at 11:40:26AM +0000, Vasant Hegde wrote:
> IOMMU performance counters are accessed via MMIO space. Currently IOMMU
> PMUs uses a single global cpumask (iommu_cpumask) shared across all AMD
> IOMMU PMU instances. This prevents collecting per-socket numbers
> (ex: perf stat --per-socket).
>
> Fix this by adjusting cpumask based on IOMMUs NUMA node.
>
> Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>
> ---
> arch/x86/events/amd/iommu.c | 29 +++++++++++++++++++++++------
> drivers/iommu/amd/init.c | 7 +++++++
> include/linux/amd-iommu.h | 1 +
> 3 files changed, 31 insertions(+), 6 deletions(-)
Acked-by: Joerg Roedel <joerg.roedel@amd.com>
prev parent reply other threads:[~2026-07-27 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 11:40 [PATCH] x86/events/amd/iommu: Fix cpumask of IOMMU events Vasant Hegde
2026-05-17 12:12 ` sashiko-bot
2026-05-18 17:58 ` Chun-Tse Shao
2026-05-19 8:00 ` Vasant Hegde
2026-05-28 7:28 ` Jörg Rödel
2026-05-29 6:58 ` Sandipan Das
2026-07-27 10:38 ` Vasant Hegde
2026-07-27 11:19 ` Jörg Rödel [this message]
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=amc-s_W_TjLYnbw0@8bytes.org \
--to=joro@8bytes.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux.dev \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@kernel.org \
--cc=vasant.hegde@amd.com \
--cc=x86@kernel.org \
/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