From: Sudeep Holla <sudeep.holla@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Gavin Shan <gshan@redhat.com>,
kvm@vger.kernel.org, Sudeep Holla <sudeep.holla@kernel.org>,
kvmarm@lists.linux.dev, maz@kernel.org, will@kernel.org,
catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, steven.price@arm.com,
aneesh.kumar@kernel.org, oupton@kernel.org, joey.gouly@arm.com,
tabba@google.com, yuzenghui@huawei.com,
linux-coco@lists.linux.dev, gankulkarni@os.amperecomputing.com,
sdonthineni@nvidia.com, alpergun@google.com,
fj0570is@fujitsu.com, WeiLin.Chang@arm.com,
lpieralisi@kernel.org, enju.kohei@fujitsu.com,
jonathan.cameron@oss.qualcomm.com
Subject: Re: [PATCH v22 02/10] firmware: arm_rmm: Check for RMI support at init
Date: Wed, 14 Oct 2026 13:05:25 +0100 [thread overview]
Message-ID: <20261014-victorious-prompt-kelpie-cf3a87@sudeepholla> (raw)
In-Reply-To: <ade8dd16-4f09-47d0-a821-636ca4c62565@arm.com>
On Wed, Oct 14, 2026 at 12:06:54PM +0100, Suzuki K Poulose wrote:
[...]
>
> Then it is RMM's problem if it doesn't check that the right level of
> SMCCC version is not implemented by the EL3. Also, where do we stop
> the checks ? e.g., We need SMCCC >= v1.3, when SVE is supported.
> And >= v1.4 if SME is supported. Shouldn't we leave this to the RMM
> to verify on init and fail the init ? I can raise this with the
> tf-RMM team.
Fair enough for v1.3+/SME/SVE checks, but RMI interface relying on more
that 8 input registers for one or more of it's interfaces (e.g.
RSI_ATTESTATION_TOKEN_INIT, RSI_MEASUREMENT_EXTEND, ...etc) indicate
it can't work with SMCCC v1.1 or below
.
So IMO check for v1.2+ is completely justified here.
--
Regards,
Sudeep
next prev parent reply other threads:[~2026-10-14 12:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 6:14 [PATCH v22 00/10] firmware: arm_rmm: Add RMM v2.0 base RMI support Suzuki K Poulose
2026-10-02 6:14 ` [PATCH v22 01/10] firmware: arm_rmm: Add SMC definitions for calling the RMM Suzuki K Poulose
2026-10-02 6:14 ` [PATCH v22 02/10] firmware: arm_rmm: Check for RMI support at init Suzuki K Poulose
2026-10-13 3:53 ` Gavin Shan
2026-10-13 9:58 ` Suzuki K Poulose
2026-10-14 7:26 ` Gavin Shan
2026-10-14 9:19 ` Suzuki K Poulose
2026-10-14 10:58 ` Gavin Shan
2026-10-14 11:06 ` Sudeep Holla
2026-10-14 11:06 ` Suzuki K Poulose
2026-10-14 12:05 ` Sudeep Holla [this message]
2026-10-14 12:40 ` Suzuki K Poulose
2026-10-02 6:14 ` [PATCH v22 03/10] firmware: arm_rmm: Configure the RMM with the host's page size Suzuki K Poulose
2026-10-02 6:15 ` [PATCH v22 04/10] firmware: arm_rmm: Add support for SRO Suzuki K Poulose
2026-10-02 6:15 ` [PATCH v22 05/10] firmware: arm_rmm: Activate the RMM Suzuki K Poulose
2026-10-02 6:15 ` [PATCH v22 06/10] firmware: arm_rmm: Ensure the RMM has GPT entries for memory Suzuki K Poulose
2026-10-02 6:15 ` [PATCH v22 07/10] kernel: hibernate: Add an arch hook for preventing hiberation Suzuki K Poulose
2026-10-02 11:03 ` Catalin Marinas
2026-10-02 15:29 ` Suzuki K Poulose
2026-10-12 19:11 ` Rafael J. Wysocki (Intel)
2026-10-02 13:32 ` Sudeep Holla
2026-10-02 6:15 ` [PATCH v22 08/10] arm64: Block hibernate and kexec while RMM is active Suzuki K Poulose
2026-10-02 6:15 ` [PATCH v22 09/10] firmware: arm_rmm: Add wrappers for Realm related RMI commands Suzuki K Poulose
2026-10-02 11:05 ` Catalin Marinas
2026-10-02 15:28 ` Suzuki K Poulose
2026-10-02 6:15 ` [PATCH v22 10/10] firmware: arm_rmm: hotplug: Skip memory added to ZONE_MOVABLE Suzuki K Poulose
2026-10-02 7:57 ` David Hildenbrand (Arm)
2026-10-02 18:49 ` [PATCH v22 00/10] firmware: arm_rmm: Add RMM v2.0 base RMI support Catalin Marinas
2026-10-03 5:57 ` Suzuki K Poulose
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=20261014-victorious-prompt-kelpie-cf3a87@sudeepholla \
--to=sudeep.holla@kernel.org \
--cc=WeiLin.Chang@arm.com \
--cc=alpergun@google.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=enju.kohei@fujitsu.com \
--cc=fj0570is@fujitsu.com \
--cc=gankulkarni@os.amperecomputing.com \
--cc=gshan@redhat.com \
--cc=joey.gouly@arm.com \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=sdonthineni@nvidia.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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
all inboxes | Powered by JetHome®