From 08e4bf1fe0725a4579d993950306b6cb22b088b1 Mon Sep 17 00:00:00 2001 From: Andrei Warkentin Date: Mon, 8 Apr 2024 21:20:13 -0500 Subject: [PATCH] Fix https://github.com/riscv-non-isa/riscv-brs/issues/111 Signed-off-by: Andrei Warkentin --- non-normative/uefi.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/non-normative/uefi.adoc b/non-normative/uefi.adoc index 54417fc..e01f191 100644 --- a/non-normative/uefi.adoc +++ b/non-normative/uefi.adoc @@ -5,9 +5,9 @@ depending on whether virtualization is supported or used. Different portions of system firmware might target a specific privilege level. In contrast, UEFI drivers, OS loaders and -applications must not contain any assumptions of the privilege -level at boot time. This is because UEFI-compliant executable -images need to operate correctly in both (V)S-Mode or HS-Mode. +pre-boot applications need to operate in supervisor mode (either +(V)S-Mode or HS-Mode), because they are UEFI-compliant executable +images. As an implementation choice, a UEFI firmware implementation may start execution in M-Mode. However it must switch to supervisor