From: Sudeep Holla <sudeep.holla@arm.com>
To: Ayan Kumar Halder <ayankuma@amd.com>
Cc: mark.rutland@arm.com, lpieralisi@kernel.org,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Vladimir Murzin <vladimir.murzin@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: SMP enablement on Cortex-R52 (using PSCI ?)
Date: Wed, 19 Apr 2023 09:47:56 +0100 [thread overview]
Message-ID: <20230419084756.3gypfyuuezjj7tyd@bogus> (raw)
In-Reply-To: <1cb7d428-c047-1485-e39d-465806f6ef0b@amd.com>
Hi Ayan,
On Fri, Apr 14, 2023 at 12:24:38PM +0100, Ayan Kumar Halder wrote:
> Hi PSCI developers,
>
> We have a SoC where there are 4 Cortex-R52 which is distributed in two
> clusters. So we have 2 Cortex-R52 in one cluster and 2 Cortex-R52 in another
> cluster.
>
> We wish to enable SMP on the 2 R52 within a cluster with Xen hypervisor (EL2
> software) running on them.
>
> We are trying to explore if we can use PSCI for booting the secondary cores.
>
> Refer Cortex-R52 TRM
> (https://developer.arm.com/documentation/100026/0101/?lang=en ), it
> specifies the following :-
>
> Page 24 - Section 1.4.1
>
> "Support for Exception levels, EL0, EL1, and EL2."
>
> Page 30 - Section 2.1.6
>
> "The Cortex-R52 processor does not implement TrustZone® technology. It does
> not support the ability to distinguish between secure and non-secure
> physical memories."
>
> Thus, there is no EL3 and secure world in Cortex-R52. It implements
> AArch32-V8R architecture.
>
KVM hypervisor use PSCI to bring up secondaries in the VMs. So I am sure we
must be able to use the interface on Cortex-R52 without EL3.
>
> Refer PSCI design document,
> https://developer.arm.com/documentation/den0022/e/?lang=en
>
> Page 18 -
> "The PSCI specification focuses on the interface between Security states for
> power management. It provides a method for issuing power management
> requests. To deal with the requests, the PPF must include a PSCI
> implementation. A PSCI implementation might require communication between
> the PPF and a Trusted OS or SP."
>
> Page 17 - Privileged Platform Firmware (PPF)
>
> "For Armv7 systems, or Armv8 systems using AArch32 at EL3, PPF executes in
> EL3."
>
> From the above two statements, I infer that PSCI requires a PPF (running at
> EL3) and a Trusted OS (running at secure EL2). If this is correct, then R52
> cannot support PSCI. Please correct me if I am mistaken.
>
> I wish to know how do we wake up the secondary core if PSCI is not
> supported.
>
I will check with the authors if EL3 is a must for PSCI implementation, but
IMO it must not be though every aspects described in the spec may not apply
when used across EL2/EL1 boundaries especially when EL3 is not implemented
in the hardware.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-04-19 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 11:24 SMP enablement on Cortex-R52 (using PSCI ?) Ayan Kumar Halder
2023-04-18 12:14 ` Vladimir Murzin
2023-04-19 8:47 ` Sudeep Holla [this message]
2023-04-19 17:50 ` Robin Murphy
2023-04-20 9:51 ` Sudeep Holla
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=20230419084756.3gypfyuuezjj7tyd@bogus \
--to=sudeep.holla@arm.com \
--cc=ayankuma@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=sstabellini@kernel.org \
--cc=vladimir.murzin@arm.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