efi_loader: QEMU CONFIG_EFI_GRUB_ARM32_WORKAROUND=n
PATCH 1/1 efi_loader: QEMU CONFIG_EFI_GRUB_ARM32_WORKAROUND=n
CONFIG_EFI_GRUB_ARM32 is only needed for architectures with caches that are not managed via CP15 (or for some outdated buggy versions of GRUB). It makes more sense to disable the setting per architecture than per defconfig.
Move QEMU's CONFIG_EFI_GRUB_ARM32_WORKAROUND=n from defconfig to Kconfig.
--- configs/qemu_arm_defconfig | 1 - lib/efi_loader/Kconfig | 1 + 2 files changed, 1 insertion(+), 1 deletion(-)
configs/qemu_arm_defconfig +0 -1
@@ -56,4 +56,3 @@ CONFIG_USB=y CONFIG_DM_USB=y CONFIG_USB_EHCI_HCD=y CONFIG_USB_EHCI_PCI=y -# CONFIG_EFI_GRUB_ARM32_WORKAROUND is not set
lib/efi_loader/Kconfig +1 -0
@@ -164,6 +164,7 @@ config EFI_HAVE_RUNTIME_RESET config EFI_GRUB_ARM32_WORKAROUND bool "Workaround for GRUB on 32bit ARM" + default n if ARCH_QEMU default y depends on ARM && !ARM64 help
--
2.28.0
PATCH 1/1 efi_loader: QEMU CONFIG_EFI_GRUB_ARM32_WORKAROUND=n
Quoted 11 lines · Heinrich Schuchardt
CONFIG_EFI_GRUB_ARM32is only needed for architectures with caches that are not managed via CP15 (or for some outdated buggy versions of GRUB). It makes more sense to disable the setting per architecture than per defconfig.Move QEMU's
CONFIG_EFI_GRUB_ARM32_WORKAROUND=nfrom defconfig toKconfig.Signed-off-by Heinrich Schuchardt <[email protected]>--- configs/qemu_arm_defconfig | 1 - lib/efi_loader/Kconfig | 1 + 2 files changed, 1 insertion(+), 1 deletion(-)
Why? Are we about to move this to be a short list of "default y if ..." instead? Otherwise no, this is the level of detail that should be in a defconfig I think and not Kconfig.
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200917/4d2a2240/attachment.sig>
PATCH 1/1 efi_loader: QEMU CONFIG_EFI_GRUB_ARM32_WORKAROUND=n
Quoted 14 lines · Tom Rini
Quoted 11 lines · Heinrich Schuchardt
CONFIG_EFI_GRUB_ARM32is only needed for architectures with caches that are not managed via CP15 (or for some outdated buggy versions of GRUB). It makes more sense to disable the setting per architecture than per defconfig.Move QEMU's
CONFIG_EFI_GRUB_ARM32_WORKAROUND=nfrom defconfig toKconfig.Signed-off-by Heinrich Schuchardt <[email protected]>--- configs/qemu_arm_defconfig | 1 - lib/efi_loader/Kconfig | 1 + 2 files changed, 1 insertion(+), 1 deletion(-)
Quoted 4 lines
Why? Are we about to move this to be a short list of "default y if ..." instead? Otherwise no, this is the level of detail that should be in a defconfig I think and not
Kconfig.
Hello Tom,
yes, in the long run I want to turn this into "default y if". But I first need to a list of all ARCH_* which have a cache which is not controlled via CP15.
Best regards
Heinrich
PATCH 1/1 efi_loader: QEMU CONFIG_EFI_GRUB_ARM32_WORKAROUND=n
Quoted 20 lines · Heinrich Schuchardt
Quoted 14 lines · Tom Rini
Quoted 11 lines · Heinrich Schuchardt
CONFIG_EFI_GRUB_ARM32is only needed for architectures with caches that are not managed via CP15 (or for some outdated buggy versions of GRUB). It makes more sense to disable the setting per architecture than per defconfig.Move QEMU's
CONFIG_EFI_GRUB_ARM32_WORKAROUND=nfrom defconfig toKconfig.Signed-off-by Heinrich Schuchardt <[email protected]>--- configs/qemu_arm_defconfig | 1 - lib/efi_loader/Kconfig | 1 + 2 files changed, 1 insertion(+), 1 deletion(-)Quoted 4 lines
Why? Are we about to move this to be a short list of "default y if ..." instead? Otherwise no, this is the level of detail that should be in a defconfig I think and not
Kconfig.
Quoted 5 lines
Hello Tom,
yes, in the long run I want to turn this into "default y if". But I first need to a list of all ARCH_* which have a cache which is not controlled via CP15.
Isn't the bigger problem / list "needs to support old / buggy GRUB" ?
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200917/b5893f57/attachment.sig>
PATCH 1/1 efi_loader: QEMU CONFIG_EFI_GRUB_ARM32_WORKAROUND=n
Am 17. September 2020 20:53:20 MESZ schrieb Tom Rini <[email protected]>:
Quoted 28 lines · Heinrich Schuchardt
Quoted 2 lines · Tom Rini
Quoted 1 line
On Thu, Sep 17, 2020 at 07:18:08PM +0200, Heinrich Schuchardt
Quoted 2 lines · wrote:
Quoted 2 lines
Quoted 2 lines
CONFIG_EFI_GRUB_ARM32is only needed for architectures with cachesthat are
Quoted 1 line
Quoted 1 line
Quoted 1 line
not managed via CP15 (or for some outdated buggy versions of
GRUB). It
Quoted 1 line
Quoted 1 line
Quoted 1 line
makes more sense to disable the setting per architecture than per
defconfig.
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Move QEMU's
CONFIG_EFI_GRUB_ARM32_WORKAROUND=nfrom defconfig to
Kconfig.Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
Signed-off-by Heinrich Schuchardt <[email protected]>--- configs/qemu_arm_defconfig | 1 - lib/efi_loader/Kconfig | 1 + 2 files changed, 1 insertion(+), 1 deletion(-)Why? Are we about to move this to be a short list of "default y if
..."
Quoted 1 line
Quoted 1 line
instead? Otherwise no, this is the level of detail that should be
in a
Quoted 3 lines
Quoted 2 lines
defconfig I think and not
Kconfig.
Quoted 7 lines
Quoted 5 lines
Hello Tom,
yes, in the long run I want to turn this into "default y if". But I first need to a list of all ARCH_* which have a cache which is not controlled via CP15.
Isn't the bigger problem / list "needs to support old / buggy GRUB" ?
There are no operating systems distributing 2021 U-Boot with 2018 GRUB.
Best regards
Heinrich
PATCH 1/1 efi_loader: QEMU CONFIG_EFI_GRUB_ARM32_WORKAROUND=n
Quoted 31 lines · Heinrich Schuchardt
Am 17. September 2020 20:53:20 MESZ schrieb Tom Rini <[email protected]>:
Quoted 30 lines · Heinrich Schuchardt
Quoted 2 lines · Tom Rini
Quoted 1 line
On Thu, Sep 17, 2020 at 07:18:08PM +0200, Heinrich Schuchardt
Quoted 2 lines · wrote:
Quoted 2 lines
Quoted 2 lines
CONFIG_EFI_GRUB_ARM32is only needed for architectures with cachesthat are
Quoted 1 line
Quoted 1 line
Quoted 1 line
not managed via CP15 (or for some outdated buggy versions of
GRUB). It
Quoted 1 line
Quoted 1 line
Quoted 1 line
makes more sense to disable the setting per architecture than per
defconfig.
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Move QEMU's
CONFIG_EFI_GRUB_ARM32_WORKAROUND=nfrom defconfig to
Kconfig.Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
Signed-off-by Heinrich Schuchardt <[email protected]>--- configs/qemu_arm_defconfig | 1 - lib/efi_loader/Kconfig | 1 + 2 files changed, 1 insertion(+), 1 deletion(-)Why? Are we about to move this to be a short list of "default y if
..."
Quoted 1 line
Quoted 1 line
instead? Otherwise no, this is the level of detail that should be
in a
Quoted 5 lines
Quoted 2 lines
defconfig I think and not
Kconfig.Hello Tom,
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
yes, in the long run I want to turn this into "default y if". But I first need to a list of all ARCH_* which have a cache which is not controlled via CP15.
Isn't the bigger problem / list "needs to support old / buggy GRUB" ?
There are no operating systems distributing 2021 U-Boot with 2018 GRUB.
Then we should remove default y there after v2020.10 I think, and get the distro folks to ack/review that. I don't think there's any cases of "SoC doesn't use CP15 for cache" and "SoC uses GRUB".
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200918/1a528e15/attachment.sig>
PATCH 1/1 efi_loader: QEMU CONFIG_EFI_GRUB_ARM32_WORKAROUND=n
Quoted 36 lines · Tom Rini
Quoted 35 lines · Heinrich Schuchardt
Am 17. September 2020 20:53:20 MESZ schrieb Tom Rini <[email protected]>:
Quoted 34 lines · Heinrich Schuchardt
Quoted 2 lines · Tom Rini
Quoted 1 line
On Thu, Sep 17, 2020 at 07:18:08PM +0200, Heinrich Schuchardt
Quoted 2 lines · wrote:
Quoted 2 lines
Quoted 2 lines
CONFIG_EFI_GRUB_ARM32is only needed for architectures with cachesthat are
Quoted 1 line
Quoted 1 line
Quoted 1 line
not managed via CP15 (or for some outdated buggy versions of
GRUB). It
Quoted 1 line
Quoted 1 line
Quoted 1 line
makes more sense to disable the setting per architecture than per
defconfig.
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Move QEMU's
CONFIG_EFI_GRUB_ARM32_WORKAROUND=nfrom defconfig to
Kconfig.Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
Signed-off-by Heinrich Schuchardt <[email protected]>--- configs/qemu_arm_defconfig | 1 - lib/efi_loader/Kconfig | 1 + 2 files changed, 1 insertion(+), 1 deletion(-)Why? Are we about to move this to be a short list of "default y if
..."
Quoted 1 line
Quoted 1 line
instead? Otherwise no, this is the level of detail that should be
in a
Quoted 8 lines
Quoted 2 lines
defconfig I think and not
Kconfig.Hello Tom,
yes, in the long run I want to turn this into "default y if". But I first need to a list of all ARCH_* which have a cache which is not controlled via CP15.
Quoted 8 lines
Quoted 3 lines
Quoted 1 line
Isn't the bigger problem / list "needs to support old / buggy GRUB" ?
There are no operating systems distributing 2021 U-Boot with 2018 GRUB.
Then we should remove default y there after v2020.10 I think, and get the distro folks to ack/review that. I don't think there's any cases of "SoC doesn't use CP15 for cache" and "SoC uses GRUB".
How about l2_cache_disable() in arch/arm/mach-kirkwood/cache.c?
Best regards
Heinrich
PATCH 1/1 efi_loader: QEMU CONFIG_EFI_GRUB_ARM32_WORKAROUND=n
Quoted 39 lines · Heinrich Schuchardt
Quoted 38 lines · Tom Rini
Quoted 37 lines · Heinrich Schuchardt
Am 17. September 2020 20:53:20 MESZ schrieb Tom Rini <[email protected]>:
Quoted 35 lines · Heinrich Schuchardt
Quoted 2 lines · Tom Rini
Quoted 1 line
On Thu, Sep 17, 2020 at 07:18:08PM +0200, Heinrich Schuchardt
Quoted 2 lines · wrote:
Quoted 2 lines
Quoted 2 lines
CONFIG_EFI_GRUB_ARM32is only needed for architectures with cachesthat are
Quoted 1 line
Quoted 1 line
Quoted 1 line
not managed via CP15 (or for some outdated buggy versions of
GRUB). It
Quoted 1 line
Quoted 1 line
Quoted 1 line
makes more sense to disable the setting per architecture than per
defconfig.
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Move QEMU's
CONFIG_EFI_GRUB_ARM32_WORKAROUND=nfrom defconfig to
Kconfig.Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
Signed-off-by Heinrich Schuchardt <[email protected]>--- configs/qemu_arm_defconfig | 1 - lib/efi_loader/Kconfig | 1 + 2 files changed, 1 insertion(+), 1 deletion(-)Why? Are we about to move this to be a short list of "default y if
..."
Quoted 1 line
Quoted 1 line
instead? Otherwise no, this is the level of detail that should be
in a
Quoted 8 lines
Quoted 2 lines
defconfig I think and not
Kconfig.Hello Tom,
yes, in the long run I want to turn this into "default y if". But I first need to a list of all ARCH_* which have a cache which is not controlled via CP15.
Isn't the bigger problem / list "needs to support old / buggy GRUB" ?
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
There are no operating systems distributing 2021 U-Boot with 2018 GRUB.
Then we should remove default y there after v2020.10 I think, and get the distro folks to ack/review that. I don't think there's any cases of "SoC doesn't use CP15 for cache" and "SoC uses GRUB".
How about
l2_cache_disable()inarch/arm/mach-kirkwood/cache.c?
What's the board that uses that and where "SoC uses GRUB" comes in to play. What are the board(s) there we're talking about?
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200918/04241995/attachment.sig>
PATCH 1/1 efi_loader: QEMU CONFIG_EFI_GRUB_ARM32_WORKAROUND=n
In reply to Heinrich SchuchardtQuoted 23 lines
From: Heinrich Schuchardt <[email protected]>
Date: Thu, 17 Sep 2020 20:03:24 +0200Quoted 14 lines · Tom Rini
Quoted 11 lines · Heinrich Schuchardt
CONFIG_EFI_GRUB_ARM32is only needed for architectures with caches that are not managed via CP15 (or for some outdated buggy versions of GRUB). It makes more sense to disable the setting per architecture than per defconfig.Move QEMU's
CONFIG_EFI_GRUB_ARM32_WORKAROUND=nfrom defconfig toKconfig.Signed-off-by Heinrich Schuchardt <[email protected]>--- configs/qemu_arm_defconfig | 1 - lib/efi_loader/Kconfig | 1 + 2 files changed, 1 insertion(+), 1 deletion(-)Quoted 4 lines
Why? Are we about to move this to be a short list of "default y if ..." instead? Otherwise no, this is the level of detail that should be in a defconfig I think and not
Kconfig.
Quoted 5 lines
Hello Tom,
yes, in the long run I want to turn this into "default y if". But I first need to a list of all ARCH_* which have a cache which is not controlled via CP15.
It is fairly standard for SoCs with Cortex-A9 cores. Maybe some SoCs with Cortex-A8 are affected as well. Probably the list of affected SoCs is those that implement v7_outer_cache_enable().
However, since other 32-bit ARM UEFI implementation are generally not unavailable, I'm not sure disabling this workaround on other SoCs is feasable since the code oath for booting OSes without the MMU enabled may not be very well tested.
PATCH 1/1 efi_loader: QEMU CONFIG_EFI_GRUB_ARM32_WORKAROUND=n
Quoted 25 lines · Mark Kettenis
Quoted 25 lines
From: Heinrich Schuchardt <[email protected]>
Date: Thu, 17 Sep 2020 20:03:24 +0200Quoted 14 lines · Tom Rini
Quoted 11 lines · Heinrich Schuchardt
CONFIG_EFI_GRUB_ARM32is only needed for architectures with caches that are not managed via CP15 (or for some outdated buggy versions of GRUB). It makes more sense to disable the setting per architecture than per defconfig.Move QEMU's
CONFIG_EFI_GRUB_ARM32_WORKAROUND=nfrom defconfig toKconfig.Signed-off-by Heinrich Schuchardt <[email protected]>--- configs/qemu_arm_defconfig | 1 - lib/efi_loader/Kconfig | 1 + 2 files changed, 1 insertion(+), 1 deletion(-)Quoted 4 lines
Why? Are we about to move this to be a short list of "default y if ..." instead? Otherwise no, this is the level of detail that should be in a defconfig I think and not
Kconfig.Hello Tom,
Quoted 8 lines
Quoted 3 lines
yes, in the long run I want to turn this into "default y if". But I first need to a list of all ARCH_* which have a cache which is not controlled via CP15.
It is fairly standard for SoCs with Cortex-A9 cores. Maybe some SoCs with Cortex-A8 are affected as well. Probably the list of affected SoCs is those that implement
v7_outer_cache_enable().
git grep -n v7_outer_cache_enable
yields
arch/arm/cpu/armv7/cache_v7.c:210:__weak void v7_outer_cache_enable(void) {} arch/arm/include/asm/armv7.h:128:void v7_outer_cache_enable(void); arch/arm/mach-imx/cache.c:83:void v7_outer_cache_enable(void) arch/arm/mach-mvebu/cpu.c:658:void v7_outer_cache_enable(void) arch/arm/mach-omap2/omap3/board.c:433:void v7_outer_cache_enable(void) arch/arm/mach-omap2/omap4/hwinit.c:166:void v7_outer_cache_enable(void) arch/arm/mach-s5pc1xx/cache.c:27:void v7_outer_cache_enable(void) arch/arm/mach-socfpga/misc.c:69:void v7_outer_cache_enable(void) arch/arm/mach-uniphier/arm32/cache-uniphier.c:277:void v7_outer_cache_enable(void)
arch/arm/mach-kirkwood/cache.c has an architecture specific implementation of l2_cache_disable().
Quoted 5 lines
However, since other 32-bit ARM UEFI implementation are generally not unavailable, I'm not sure disabling this workaround on other SoCs is feasable since the code oath for booting OSes without the MMU enabled may not be very well tested.
According to the UEFI spec we have to fulfill the following requirements when handing over to the OS on ARM 32bit:
- MMU enabled
- Instruction and data caches enabled
- Access flag disabled
- Translation remap disabled
- Fast Context Switch Extension (FCSE) must be disabled
- caches requiring platform information to manage or invoke non-architectural cache/TLB lockdown mechanisms disabled
With the GRUB workaround enabled we call cleanup_before_linux(). According to README.arm_caches this shall disable the MMU.
Mark, I do not understand your concerns regarding a disabled MMU when *not* calling cleanup_before_linux().
Best regards
Heinrich