From: Will Deacon <will@kernel.org>
To: Xiquan Zhang <zhangxiquan@hisilicon.com>
Cc: catalin.marinas@arm.com, corbet@lwn.net,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, maz@kernel.org
Subject: Re: [PATCH] Documentation (arm64):Advanced SIMD and floating point support condition
Date: Tue, 29 Apr 2025 14:11:19 +0100 [thread overview]
Message-ID: <20250429131116.GA25912@willie-the-truck> (raw)
In-Reply-To: <20250408031309.2095-1-zhangxiquan@hisilicon.com>
On Tue, Apr 08, 2025 at 11:13:09AM +0800, Xiquan Zhang wrote:
> From: zhangyu <zhangyu550@huawei.com>
>
> Because the kernel code cannot be started from el1
> according to the booting.rst.
> It is found that CPTR_EL2.FPEN is not configured.
> After the configuration, the problem is solved.
>
> Signed-off-by: zhangyu <zhangyu550@huawei.com>
> Signed-off-by: zhangxiquan <zhangxiquan@hisilicon.com>
> ---
> Documentation/arch/arm64/booting.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/arch/arm64/booting.rst b/Documentation/arch/arm64/booting.rst
> index dee7b6de864f..ccefc42b51bc 100644
> --- a/Documentation/arch/arm64/booting.rst
> +++ b/Documentation/arch/arm64/booting.rst
> @@ -309,6 +309,7 @@ Before jumping into the kernel, the following conditions must be met:
> - If EL2 is present and the kernel is entered at EL1:
>
> - CPTR_EL2.TFP (bit 10) must be initialised to 0b0.
> + - CPTR_EL2.FPEN (bit 21:20) must be initialised to 0b11.
Sorry, but I don't quite understand this. CPTR_EL2 has a different format
depending on HCR_EL2.E2H and the FPEN field only exists when that bit is
set to 1. In that case, however, why would the kernel be entered at EL1?
Will
next prev parent reply other threads:[~2025-04-29 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 3:13 [PATCH] Documentation (arm64):Advanced SIMD and floating point support condition Xiquan Zhang
2025-04-29 13:11 ` Will Deacon [this message]
[not found] ` <0acdf18f6c2748919dcbeb943e4ced3e@hisilicon.com>
[not found] ` <a90e072198c344e3a4ae0ed0cb8bbe62@huawei.com>
2025-05-13 3:11 ` 答复: " Zhangxiquan
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=20250429131116.GA25912@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=zhangxiquan@hisilicon.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