From: Rory Bolt <Rory.Bolt@kioxia.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"ardb@kernel.org" <ardb@kernel.org>,
"maz@kernel.org" <maz@kernel.org>,
"will@kernel.org" <will@kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>
Subject: RE: Big endian modifications
Date: Fri, 4 Feb 2022 17:59:18 +0000 [thread overview]
Message-ID: <266261a7f21945abbd24a2194e7d288d@kioxia.com> (raw)
In-Reply-To: <Yfw2tw50oMZvFu1y@FVFF77S0Q05N>
Mark,
I tested without my patch and the kernel does run big endian, however:
The reason I thought my patch was necessary in the first place was that upon kernel entry, before the call to init_kernel_el(), the first call is to preserve_boot_args() which writes the contents of x0..x3 to memory... which will be done in little endian format. Fortunately, no one currently uses the values stored in boot_args for anything other than a check to see that x1..x3 were set to zero since they are reserved for future use. This works now, since they are reserved and set to zero which is not endian sensitive, however in the future if any additional boot args are passed in x1..x3 they will not be stored in the correct byte order.
Should this be addressed now, or in the future?
-Rory
-----Original Message-----
From: Mark Rutland <mark.rutland@arm.com>
Sent: Thursday, February 3, 2022 12:11 PM
To: Rory Bolt <Rory.Bolt@kioxia.com>
Cc: linux-arm-kernel@lists.infradead.org; ardb@kernel.org; maz@kernel.org; will@kernel.org; catalin.marinas@arm.com
Subject: Re: Big endian modifications
Hi,
On Thu, Feb 03, 2022 at 06:48:43PM +0000, Rory Bolt wrote:
> Hello,
>
> I have been modifying GRUB on Das U-boot to allow it to boot
> aarch64_be big endian kernels on the RockPro64 board. Since the
> RockPro64 has a PCIe (albeit
> 2.0) slot, it provides a low cost/reasonable performance (vs QEMU)
> system to test our devices, drivers and software stack on a big endian
> system. I am in the process of publishing the required changes to
> GRUB, however there are two minor changes made to the kernel itself.
Kernel patches need to be submitted in a particular format, with a commit title, commit message, and DCO (Signed-off-by) lines. Please see:
https://docs.kernel.org/process/submitting-patches.html
https://docs.kernel.org/process/development-process.html
It's also worthwhile looking at the MAINTAINERS file to Cc relevant people. For example, Catalin and Will are the maintainers of the arm64 port, and Ard, Marc, and I have made various changes to this code.
> Arguably the modification to head.S could be moved to grub itself,
> however it is in the defensive spirit of not assuming the boot loader
> has set up everything correctly and is very similar to the startup of
> NetBSD which contains similar code in its startup.
Hmm... big-endian boot *should* already work. The kernel configures its endianness in init_kernel_el(), and from testing a BE v5.17-rc2 kernel just now with a FVP Base model and the boot-wrapper (which would leave the CPU in a little-endian state when jumping to the kernel) things seem to work.
Which kernel version are you testing with, and how *exactly* is the kernel being entered?
Is it being entered directly by the protocol defined at:
https://docs.kernel.org/arm64/booting.html
... or some other way (e.g. via the EFI application entry point?).
> The second change to Kconfig allows a EFI/PE/COFF header to be added
> to a big endian kernel (although unfortunately it also adds a useless
> big endian efistub to the kernel too). With the following two changes
> the modified GRUB can boot either big endian or little endian Arm64 images.
This implies that grub is trying to enter the EFI entry point, and a bunch of things aren't going to work thereafter.
What have you changed on the GRUB side? Because I don't understand why it would
*need* changes, if the PE/COFF header and EFI stub handled being entered in LE, then switching to BE. That and it should be possible to boot a BE kernel without neding a PE/COFF header, so something doesn't add up.
> Please consider the following two modifications for inclusion:
As above, we can't take this as-is, but if you've found a regression I'm more than happy to try to get that fixed. If we *really* need to be able to boot BE kernels from EFI, there might be things that we can do, but I don't think we can just remove the CONFIG_EFI dependency on !CPU_BIG_ENDIAN -- the runtime bits *certainly* won't work, at minimum the stub needs to be built LE, etc.
Also, have you considered running your kernel under KVM, with devices assigned to it? That might be significantly easier than having a BE kernel that handles EFI.
Thanks,
Mark.
> diff --git a/arch/arm64/kernel/head.S b/arch/arm64/kernel/head.S index
> 6a98f1a38c29..40a18d767d15 100644
> --- a/arch/arm64/kernel/head.S
> +++ b/arch/arm64/kernel/head.S
> @@ -89,6 +89,24 @@
> * x24 __primary_switch() .. relocate_kernel() current RELR displacement
> */
> SYM_CODE_START(primary_entry)
> +#ifdef CONFIG_CPU_BIG_ENDIAN
> + mrs x21, CurrentEL
> + lsr x21, x21, #2
> + cmp x21, #0x2
> + b.lo 1f
> +
> + mrs x21, sctlr_el2
> + orr x21, x21, #SCTLR_ELx_EE /* set: Big Endian */
> + msr sctlr_el2, x21
> + isb
> +
> +1:
> + mrs x21, sctlr_el1
> + orr x21, x21, #(SCTLR_ELx_EE | SCTLR_EL1_E0E) /* set: Big Endian */
> + msr sctlr_el1, x21
> + isb
> +
> +#endif
> bl preserve_boot_args
> bl init_kernel_el // w0=cpu_boot_mode
> adrp x23, __PHYS_OFFSET
>
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index
> c4207cf9bb17..a9ccbeb75ea7 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -1997,7 +1997,7 @@ config EFI_STUB
>
> config EFI
> bool "UEFI runtime support"
> - depends on OF && !CPU_BIG_ENDIAN
> + depends on OF
> depends on KERNEL_MODE_NEON
> select ARCH_SUPPORTS_ACPI
> select LIBFDT
>
> Rory Bolt
>
> KIOXIA America, Inc. | formerly Toshiba Memory America, Inc.
>
>
>
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
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:[~2022-02-04 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 18:48 Big endian modifications Rory Bolt
2022-02-03 20:10 ` Mark Rutland
2022-02-03 21:20 ` Robin Murphy
2022-02-03 21:36 ` Rory Bolt
2022-02-04 17:59 ` Rory Bolt [this message]
2022-02-04 18:48 ` Rory Bolt
2022-02-03 20:45 ` Robin Murphy
2022-02-03 21:41 ` Rory Bolt
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=266261a7f21945abbd24a2194e7d288d@kioxia.com \
--to=rory.bolt@kioxia.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--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