All of lore.kernel.org
 help / color / mirror / Atom feed
From: KobaK <kobak@nvidia.com>
To: Rob Herring <robh@kernel.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 2/3] Documentation/arch/arm64: document arm_cpumod
Date: Mon, 24 Aug 2026 17:54:04 +0800	[thread overview]
Message-ID: <20260824095405.3-2-kobak@nvidia.com> (raw)
In-Reply-To: <20260817220354.GA2274565-robh@kernel.org>

Hi Rob,

Thanks for the documentation feedback.

I have prepared the documentation changes: the arm64 guide no longer uses
“Current ABI” or duplicates the file descriptions, and the seven sysfs files
are now documented using the standard Documentation/ABI format.

The driver accesses IMP_CPUECTLR_EL1 (S3_0_C15_C1_4) and
IMP_CPUECTLR2_EL1 (S3_0_C15_C1_5). I am checking with our firmware team for
the kernel-visible contract that guarantees or reports EL1 access. I will not
add a speculative write-and-see-if-the-system-survives probe.

I will hold v2 pending that answer and the arm64 maintainers’ direction on
the interface.

Thanks,
Koba

  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
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 [this message]
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-2-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=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=robh@kernel.org \
    --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 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.