diff options
| author | Zhuoying Cai <zycai@linux.ibm.com> | 2026-07-30 17:46:04 -0400 |
|---|---|---|
| committer | Eric Farman <farman@linux.ibm.com> | 2026-08-26 06:52:20 -0400 |
| commit | e4a2805118af211087b99ca9f77016bb5e922fe5 (patch) | |
| tree | 7f098dc203d726669de2647a77371372fcdc5a7f /docs | |
| parent | f5faede1ea8f99bd61e4c30c3c473cf104fd2fc4 (diff) | |
| download | qemu-e4a2805118af211087b99ca9f77016bb5e922fe5.tar.gz qemu-e4a2805118af211087b99ca9f77016bb5e922fe5.zip | |
s390x/ipl: Introduce IPL Information Report Block (IIRB)
The IPL information report block (IIRB) contains information used
to locate IPL records and to report the results of signature verification
of one or more secure components of the load device.
IIRB is stored immediately following the IPL Parameter Block. Results on
component verification in any case (failure or success) are stored.
The IIRB data is reserved and protected by the guest kernel during early
boot to prevent it from being overwritten before the certificate data is
permanently saved.
Signed-off-by: Zhuoying Cai <zycai@linux.ibm.com>
Reviewed-by: Farhan Ali <alifm@linux.ibm.com>
Reviewed-by: Collin Walling <walling@linux.ibm.com>
Link: https://lore.kernel.org/qemu-devel/20260730214624.2328883-16-zycai@linux.ibm.com
Signed-off-by: Eric Farman <farman@linux.ibm.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/specs/s390x-secure-ipl.rst | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/docs/specs/s390x-secure-ipl.rst b/docs/specs/s390x-secure-ipl.rst index d8dcc77ba2..113acbeda9 100644 --- a/docs/specs/s390x-secure-ipl.rst +++ b/docs/specs/s390x-secure-ipl.rst @@ -101,3 +101,24 @@ Subcode 1 - perform signature verification * ``0x0302``: PKCS#7 format signature is invalid * ``0x0402``: signature-verification failed * ``0x0502``: length of Diag508SigVerifBlock is invalid + +IPL Information Report Block +^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +The IPL Parameter Block (IPLB), utilized for IPL operation, is extended with an +IPL Information Report Block (IIRB), which contains the results from secure IPL +operations such as: + +* component data +* verification results +* certificate data + +During early boot, the guest kernel reserves the memory region +containing the IIRB. This preserves the data while the guest kernel is +operating and during re-IPL. + +The guest kernel uses the contents in the IIRB for: + +* Boot logging: reports which components were loaded and verified. +* kexec operations: builds the next kernel’s IPL report from the existing one. +* Keying: installs IPL certificates into the platform trusted keyring. |