From: KobaK <kobak@nvidia.com>
To: Breno Leitao <leitao@debian.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Fenghua Yu <fenghuay@nvidia.com>, Tushar Dave <tdave@nvidia.com>,
Kai-Heng Feng <kaihengf@nvidia.com>,
Rupak Roy <rupakr@nvidia.com>,
Mohammed Karamathulla <mohammedk@nvidia.com>
Subject: Re: [RFC PATCH 1/3] arm64: add CPU prefetch and cache modulation sysfs interface
Date: Mon, 24 Aug 2026 17:54:05 +0800 [thread overview]
Message-ID: <20260824095405.3-3-kobak@nvidia.com> (raw)
In-Reply-To: <aoXEBXXvTDBimnHi@gmail.com>
Hi Breno,
Thanks for reviewing and testing this.
The current read result is consumed by cpumod_attr_show(), but you are right
that the persistent cached-value plumbing is unnecessary. For v2, I plan to
return the value through call.value, emit it directly, and remove the cached
fields and helpers that no longer have a consumer.
I also agree about the permissions issue. The register-backed reads perform a
synchronous IPI, so allowing unprivileged reads could generate a steady IPI
stream. I plan to change the six register-backed controls to 0600 and retain
affected_cpus as 0444 metadata.
I have recorded your Tested-by, but I will confirm that it still applies after
these changes before carrying it into v2. The resend is currently on hold
pending arm64 maintainer direction.
Thanks,
Koba
next prev parent reply other threads:[~2026-08-24 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 2:23 [RFC PATCH 0/3] arm64: expose CPU prefetch and cache modulation controls KobaK
2026-08-17 2:23 ` [RFC PATCH 1/3] arm64: add CPU prefetch and cache modulation sysfs interface KobaK
2026-08-17 22:07 ` Rob Herring
2026-08-24 9:54 ` KobaK
2026-08-19 14:43 ` Breno Leitao
2026-08-19 14:57 ` Breno Leitao
2026-08-24 9:54 ` KobaK [this message]
2026-08-17 2:23 ` [RFC PATCH 2/3] Documentation/arch/arm64: document arm_cpumod KobaK
2026-08-17 22:03 ` Rob Herring
2026-08-24 9:54 ` KobaK
2026-08-17 2:23 ` [RFC PATCH 3/3] selftests: arm64: add arm_cpumod kselftest KobaK
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=20260824095405.3-3-kobak@nvidia.com \
--to=kobak@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=fenghuay@nvidia.com \
--cc=kaihengf@nvidia.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mohammedk@nvidia.com \
--cc=rupakr@nvidia.com \
--cc=skhan@linuxfoundation.org \
--cc=tdave@nvidia.com \
--cc=will@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