Our current strategy to deal with pending SErrors at boot is to panic. So let's mention in our boot protocol documentation that no SErrors should be pending when handing over to the kernel. Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> --- Documentation/arm64/booting.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/arm64/booting.txt b/Documentation/arm64/booting.txt index 8d0df62c3fe0..75dcfead1a0c 100644 --- a/Documentation/arm64/booting.txt +++ b/Documentation/arm64/booting.txt @@ -154,8 +154,9 @@ Before jumping into the kernel, the following conditions must be met: x3 = 0 (reserved for future use) - CPU mode - All forms of interrupts must be masked in PSTATE.DAIF (Debug, SError, - IRQ and FIQ). + All forms of exceptions must be masked in PSTATE.DAIF (Debug, SError, + IRQ and FIQ), and any pending SError exceptions must be taken by the + boot loader or firmware before handing over to the kernel. The CPU must be in either EL2 (RECOMMENDED in order to have access to the virtualisation extensions) or non-secure EL1. -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
