From: Zhuoying Cai <zycai@linux.ibm.com>
To: qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: jrossi@linux.ibm.com, cohuck@redhat.com, berrange@redhat.com,
richard.henderson@linaro.org, david@kernel.org,
walling@linux.ibm.com, jjherne@linux.ibm.com,
pasic@linux.ibm.com, borntraeger@linux.ibm.com,
farman@linux.ibm.com, mjrosato@linux.ibm.com, iii@linux.ibm.com,
eblake@redhat.com, armbru@redhat.com, zycai@linux.ibm.com,
alifm@linux.ibm.com, brueckner@linux.ibm.com,
pierrick.bouvier@oss.qualcomm.com, jdaley@linux.ibm.com
Subject: [PATCH v17 25/34] s390x: Guest support for Secure-IPL Code Loading Attributes Facility (SCLAF)
Date: Thu, 30 Jul 2026 17:46:14 -0400 [thread overview]
Message-ID: <20260730214624.2328883-26-zycai@linux.ibm.com> (raw)
In-Reply-To: <20260730214624.2328883-1-zycai@linux.ibm.com>
The secure-IPL-code-loading-attributes facility (SCLAF)
provides additional security during secure IPL.
Availability of SCLAF is determined by byte 136 bit 3 of the
SCLP Read SCP Info.
This feature is available starting with the gen16 CPU model.
Signed-off-by: Zhuoying Cai <zycai@linux.ibm.com>
Reviewed-by: Collin Walling <walling@linux.ibm.com>
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
---
docs/specs/s390x-secure-ipl.rst | 18 ++++++++++++++++++
target/s390x/cpu_features.c | 2 ++
target/s390x/cpu_features_def.h.inc | 1 +
target/s390x/cpu_models.c | 3 +++
target/s390x/gen-features.c | 2 ++
target/s390x/kvm/kvm.c | 1 +
6 files changed, 27 insertions(+)
diff --git a/docs/specs/s390x-secure-ipl.rst b/docs/specs/s390x-secure-ipl.rst
index 113acbeda9..7a603eb956 100644
--- a/docs/specs/s390x-secure-ipl.rst
+++ b/docs/specs/s390x-secure-ipl.rst
@@ -122,3 +122,21 @@ 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.
+
+Secure Code Loading Attributes Facility
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The Secure Code Loading Attributes Facility (SCLAF) enhances system security
+during the IPL by enforcing additional verification rules.
+
+When SCLAF is available, its behavior depends on the IPL mode. It introduces
+verification of both signed and unsigned components to help ensure that only
+authorized code is loaded during the IPL process. Any errors detected by SCLAF
+are reported in the IIRB.
+
+Unsigned components are restricted to load addresses at or above absolute
+storage address ``0x2000``.
+
+Signed components must include a Secure Code Loading Attribute Block (SCLAB),
+which is appended at the very end of the component. The SCLAB defines security
+attributes for handling the signed code.
diff --git a/target/s390x/cpu_features.c b/target/s390x/cpu_features.c
index 27f38636a9..c634e74123 100644
--- a/target/s390x/cpu_features.c
+++ b/target/s390x/cpu_features.c
@@ -120,6 +120,7 @@ void s390_fill_feat_block(const S390FeatBitmap features, S390FeatType type,
* - All SIE facilities because SIE is not available
* - DIAG318
* - Secure IPL Facility
+ * - Secure IPL Code Loading Attributes Facility
*
* As VMs can move in and out of protected mode the CPU model
* doesn't protect us from that problem because it is only
@@ -152,6 +153,7 @@ void s390_fill_feat_block(const S390FeatBitmap features, S390FeatType type,
break;
case S390_FEAT_TYPE_SCLP_FAC_IPL:
clear_be_bit(s390_feat_def(S390_FEAT_SIPL)->bit, data);
+ clear_be_bit(s390_feat_def(S390_FEAT_SCLAF)->bit, data);
break;
case S390_FEAT_TYPE_SCLP_FAC139:
clear_be_bit(s390_feat_def(S390_FEAT_SIE_ASTFLEIE2)->bit, data);
diff --git a/target/s390x/cpu_features_def.h.inc b/target/s390x/cpu_features_def.h.inc
index 0153a6aa67..a5aa19112a 100644
--- a/target/s390x/cpu_features_def.h.inc
+++ b/target/s390x/cpu_features_def.h.inc
@@ -142,6 +142,7 @@ DEF_FEAT(CERT_STORE, "cstore", SCLP_FAC134, 5, "Certificate Store functions")
/* Features exposed via SCLP SCCB Facilities byte 136 - 137 (bit numbers relative to byte-136) */
DEF_FEAT(SIPL, "sipl", SCLP_FAC_IPL, 1, "Secure-IPL facility")
+DEF_FEAT(SCLAF, "sclaf", SCLP_FAC_IPL, 3, "Secure-IPL-code-loading-attributes facility")
/* Features exposed via SCLP SCCB Facilities byte 139 (bit numbers relative to byte-139) */
DEF_FEAT(SIE_ASTFLEIE2, "astfleie2", SCLP_FAC139, 1, "SIE: ASTFLE interpretation execution facility 2")
diff --git a/target/s390x/cpu_models.c b/target/s390x/cpu_models.c
index b22841c2bc..2e62559679 100644
--- a/target/s390x/cpu_models.c
+++ b/target/s390x/cpu_models.c
@@ -264,6 +264,7 @@ bool s390_has_feat(S390Feat feat)
case S390_FEAT_SIE_PFMFI:
case S390_FEAT_SIE_IBS:
case S390_FEAT_SIPL:
+ case S390_FEAT_SCLAF:
case S390_FEAT_CONFIGURATION_TOPOLOGY:
case S390_FEAT_SIE_ASTFLEIE2:
return false;
@@ -510,6 +511,8 @@ static void check_consistency(const S390CPUModel *model)
{ S390_FEAT_DIAG_318, S390_FEAT_EXTENDED_LENGTH_SCCB },
{ S390_FEAT_CERT_STORE, S390_FEAT_EXTENDED_LENGTH_SCCB },
{ S390_FEAT_SIPL, S390_FEAT_EXTENDED_LENGTH_SCCB },
+ { S390_FEAT_SCLAF, S390_FEAT_EXTENDED_LENGTH_SCCB },
+ { S390_FEAT_SCLAF, S390_FEAT_SIPL },
{ S390_FEAT_NNPA, S390_FEAT_VECTOR },
{ S390_FEAT_RDP, S390_FEAT_LOCAL_TLB_CLEARING },
{ S390_FEAT_UV_FEAT_AP, S390_FEAT_AP },
diff --git a/target/s390x/gen-features.c b/target/s390x/gen-features.c
index 6bf61447de..a99a75d14e 100644
--- a/target/s390x/gen-features.c
+++ b/target/s390x/gen-features.c
@@ -723,6 +723,7 @@ static uint16_t full_GEN16_GA1[] = {
S390_FEAT_SIE_ASTFLEIE2,
S390_FEAT_CERT_STORE,
S390_FEAT_SIPL,
+ S390_FEAT_SCLAF,
};
static uint16_t full_GEN17_GA1[] = {
@@ -925,6 +926,7 @@ static uint16_t qemu_MAX[] = {
S390_FEAT_EXTENDED_LENGTH_SCCB,
S390_FEAT_CERT_STORE,
S390_FEAT_SIPL,
+ S390_FEAT_SCLAF,
};
/****** END FEATURE DEFS ******/
diff --git a/target/s390x/kvm/kvm.c b/target/s390x/kvm/kvm.c
index 6060f4cc2c..ebab450b12 100644
--- a/target/s390x/kvm/kvm.c
+++ b/target/s390x/kvm/kvm.c
@@ -2506,6 +2506,7 @@ bool kvm_s390_get_host_cpu_model(S390CPUModel *model, Error **errp)
/* Some Secure IPL facilities are emulated by QEMU */
set_bit(S390_FEAT_SIPL, model->features);
+ set_bit(S390_FEAT_SCLAF, model->features);
/* Test for Ultravisor features that influence secure guest behavior */
query_uv_feat_guest(model->features);
--
2.55.0
next prev parent reply other threads:[~2026-07-30 21:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 21:45 [PATCH v17 00/34] Secure IPL Support for SCSI Scheme of virtio-blk/virtio-scsi Devices Zhuoying Cai
2026-07-30 21:45 ` [PATCH v17 01/34] Add boot-certs to s390-ccw-virtio machine type option Zhuoying Cai
2026-07-30 21:45 ` [PATCH v17 02/34] crypto/x509-utils: Refactor with GNUTLS fallback Zhuoying Cai
2026-07-30 21:45 ` [PATCH v17 03/34] crypto/x509-utils: Add helper functions for certificate store Zhuoying Cai
2026-07-30 21:45 ` [PATCH v17 04/34] hw/s390x/ipl: Create " Zhuoying Cai
2026-07-30 21:45 ` [PATCH v17 05/34] s390x/diag: Introduce DIAG 320 for Certificate Store Facility Zhuoying Cai
2026-07-30 21:45 ` [PATCH v17 06/34] s390x/diag: Refactor address validation check from diag308_parm_check Zhuoying Cai
2026-07-30 21:45 ` [PATCH v17 07/34] s390x/diag: Implement DIAG 320 subcode 1 Zhuoying Cai
2026-07-30 21:45 ` [PATCH v17 08/34] crypto/x509-utils: Add helper functions for DIAG 320 subcode 2 Zhuoying Cai
2026-07-30 21:45 ` [PATCH v17 09/34] s390x/diag: Implement " Zhuoying Cai
2026-07-30 21:45 ` [PATCH v17 10/34] hw/s390x: Define finite size for single entry VCEntry Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 11/34] s390x/diag: Introduce DIAG 508 for secure IPL operations Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 12/34] crypto/x509-utils: Add helper functions for DIAG 508 subcode 1 Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 13/34] s390x/diag: Generalize s390_ipl_read/write to accept void * Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 14/34] s390x/diag: Implement DIAG 508 subcode 1 for signature verification Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 15/34] s390x/ipl: Introduce IPL Information Report Block (IIRB) Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 16/34] pc-bios/s390-ccw: Define memory for IPLB and convert IPLB to pointers Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 17/34] hw/s390x/ipl: Add IPIB flags to IPL Parameter Block Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 18/34] hw/s390x/ipl: Rework s390_ipl_map_iplb_chain for certificate storage Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 19/34] s390x: Guest support for Secure-IPL Facility Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 20/34] pc-bios/s390-ccw: Refactor zipl_run() Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 21/34] pc-bios/s390-ccw: Rework zipl_load_segment function Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 22/34] pc-bios/s390-ccw: Introduce ZiplBootMode enum for IPL mode selection Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 23/34] pc-bios/s390-ccw: Add signature verification for secure IPL in audit mode Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 24/34] pc-bios/s390-ccw: Add signed component address overlap checks Zhuoying Cai
2026-07-30 21:46 ` Zhuoying Cai [this message]
2026-07-30 21:46 ` [PATCH v17 26/34] pc-bios/s390-ccw: Add additional security checks for secure boot Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 27/34] Add secure-boot to s390-ccw-virtio machine type option Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 28/34] hw/s390x/ipl: Set IPIB flags for secure IPL Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 29/34] pc-bios/s390-ccw: Handle true secure IPL mode Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 30/34] hw/s390x/ipl: Handle secure boot with multiple boot devices Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 31/34] tests/functional/s390x: Add secure IPL functional test Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 32/34] docs/specs: Add secure IPL documentation Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 33/34] docs/system/s390x: " Zhuoying Cai
2026-07-30 21:46 ` [PATCH v17 34/34] MAINTAINERS: Add secure IPL files to S390-ccw boot group Zhuoying Cai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260730214624.2328883-26-zycai@linux.ibm.com \
--to=zycai@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=brueckner@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@kernel.org \
--cc=eblake@redhat.com \
--cc=farman@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=jdaley@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=jrossi@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=walling@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.