[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[xen master] SUPPORT.md: explicitly mention EFI (secure) boot status



commit d9dcd45c56baa2140857ec290962a1f9d71af73c
Author:     Jan Beulich <jbeulich@xxxxxxxx>
AuthorDate: Fri May 12 09:35:14 2023 +0200
Commit:     Jan Beulich <jbeulich@xxxxxxxx>
CommitDate: Fri May 12 09:35:14 2023 +0200

    SUPPORT.md: explicitly mention EFI (secure) boot status
    
    While normal booting is properly supported on both x86 and Arm64, secure
    boot reportedly requires quite a bit more work to be actually usable
    (and providing the intended guarantees). The mere use of the shim
    protocol for verifying the Dom0 kernel image isn't enough.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Julien Grall <jgrall@xxxxxxxxxx>
---
 SUPPORT.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/SUPPORT.md b/SUPPORT.md
index aa1940e55f..6dbed9d5d0 100644
--- a/SUPPORT.md
+++ b/SUPPORT.md
@@ -63,6 +63,16 @@ For the Cortex A57 r0p0 - r1p1, see Errata 832075.
     Status, x86 PV: Supported
     Status, ARM: Experimental
 
+### Host EFI Boot
+
+    Status, x86: Supported
+    Status, Arm64: Supported
+
+### Host EFI Secure Boot
+
+    Status, x86: Experimental
+    Status, Arm64: Experimental
+
 ### x86/Intel Platform QoS Technologies
 
     Status: Tech Preview
--
generated by git-patchbot for /home/xen/git/xen.git#master



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.