From 3398815aa337278fe4085f06f3586b2a1a98ab3d Mon Sep 17 00:00:00 2001 Message-Id: <3398815aa337278fe4085f06f3586b2a1a98ab3d@dist-git> From: Pavel Hrdina Date: Fri, 21 May 2021 14:16:04 +0200 Subject: [PATCH] docs: improve description of secure attribute for loader element The original text was not explaining what this attribute actually controls and could have been interpreted as a control switch for the Secure boot feature in firmwares. Signed-off-by: Pavel Hrdina Reviewed-by: Kashyap Chamarthy Reviewed-by: Michal Privoznik (cherry picked from commit f47d06260b9698f705ab2c079c573f89f832e376) Conflicts: docs/formatdomain.rst - we still have formatdomain.html.in in downstream Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1929357 Signed-off-by: Pavel Hrdina Message-Id: Reviewed-by: Michal Privoznik --- docs/formatdomain.html.in | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 7ac9523684..a40bed347b 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -197,7 +197,9 @@ path points to an UEFI image, type should be pflash. Moreover, some firmwares may implement the Secure boot feature. Attribute - secure can be used then to control it. + secure can be used to tell the hypervisor that the + firmware is capable of Secure Boot feature. It cannot be used to + enable or disable the feature itself in the firmware. Since 2.1.0
nvram
Some UEFI firmwares may want to use a non-volatile memory to store -- 2.31.1