s390x: Protected Virtualization support
v10 cover s390x: Protected Virtualization support
Most of the QEMU changes for PV are related to the new IPL type with subcodes 8 - 10 and the execution of the necessary Ultravisor calls to IPL secure guests. Note that we can only boot into secure mode from normal mode, i.e. stfle 161 is not active in secure mode.
The other changes related to data gathering for emulation and disabling addressing checks in secure mode, as well as CPU resets.
v10:
* Moved documentation into subfolder
* Added huge page fencing
* Cleared up IO questions that were remaining
* Added exits/abbort/assert for conditions where we can't recover
v9:
* Moved pv.h into include/hw/s390x/
* Replaced cmd strings with macro
* Moved s390_is_pv() to pv.h
* Added new copyright dates and authors
v8:
* Removed the iplb_valid changes as they are picked
* Checkpatch fixes
* Review fixes
* Replaced env/ms->pv with s390_is_pv()
v7:
* Merged the diag 308 subcode patches and the unpack
* Moved the SIDA memops into the sync patch
* Bailout for the none machien and fencing of CONFIG_USER_ONLY
* Changes due to review
v6:
* diag308 rc numbers were changed by architecture
* IPL pv block received one more reserved field by architecture
* Officially added the bios patch to the series
* Dropped picked constant rename patch
v5:
* Moved docs into docs/system
* Some more enable/disable changes
* Moved enablement/disablement of pv in separate functions
* Some review fixes
v4:
* Sync with KVM changes
* Review changes
V3:
* Use dedicated functions to access SIDA
* Smaller cleanups and segfault fixes
* Error reporting for Ultravisor calls
* Inject of RC of diag308 subcode 10 fails
V2:
* Split out cleanups
* Internal PV state tracking
* Review feedback
Christian Borntraeger (1):
s390x: Add unpack facility feature to GA1
Janosch Frank (15):
s390x: Move diagnose 308 subcodes and rcs into ipl.h Sync pv
s390x: protvirt: Support unpack facility
s390x: protvirt: Add migration blocker
s390x: protvirt: Inhibit balloon when switching to protected mode
s390x: protvirt: KVM intercept changes
s390x: Add SIDA memory ops
s390x: protvirt: Move STSI data over SIDAD
s390x: protvirt: SCLP interpretation
s390x: protvirt: Set guest IPL PSW
s390x: protvirt: Move diag 308 data over SIDA
s390x: protvirt: Disable address checks for PV guest IO emulation
s390x: protvirt: Move IO control structures over SIDA
s390x: protvirt: Handle SIGP store status correctly
docs: system: Add protvirt docs
docs/system/s390x/protvirt.rst | 59 +++++++++++ docs/system/target-s390x.rst | 5 + hw/s390x/Makefile.objs | 1 + hw/s390x/ipl.c | 59 ++++++++++- hw/s390x/ipl.h | 102 ++++++++++++++++++- hw/s390x/pv.c | 98 ++++++++++++++++++ hw/s390x/s390-virtio-ccw.c | 148 +++++++++++++++++++++++++++- hw/s390x/sclp.c | 65 +++++++++--- include/hw/s390x/pv.h | 55 +++++++++++ include/hw/s390x/s390-virtio-ccw.h | 1 + include/hw/s390x/sclp.h | 2 + linux-headers/linux/kvm.h | 45 ++++++++- target/s390x/cpu.c | 28 ++++-- target/s390x/cpu.h | 7 +- target/s390x/cpu_features_def.inc.h | 1 + target/s390x/diag.c | 77 +++++++++++---- target/s390x/gen-features.c | 1 + target/s390x/helper.c | 6 ++ target/s390x/ioinst.c | 96 +++++++++++++----- target/s390x/kvm-stub.c | 5 + target/s390x/kvm.c | 79 +++++++++++++-- target/s390x/kvm_s390x.h | 3 + target/s390x/mmu_helper.c | 14 +++ 23 files changed, 877 insertions(+), 80 deletions(-) create mode 100644 docs/system/s390x/protvirt.rst create mode 100644 hw/s390x/pv.c create mode 100644 include/hw/s390x/pv.h
Signature · 1 line
2.25.1
PATCH v10 1/16 s390x: Move diagnose 308 subcodes and rcs into ipl.h
They are part of the IPL process, so let's put them into the ipl header.
--- hw/s390x/ipl.h | 11 +++++++++++ target/s390x/diag.c | 11 ----------- 2 files changed, 11 insertions(+), 11 deletions(-)
hw/s390x/ipl.h +11 -0
@@ -159,6 +159,17 @@ struct S390IPLState {typedef struct S390IPLState S390IPLState ;QEMU_BUILD_BUG_MSG (offsetof(S390IPLState , iplb) &3 ,"alignment of iplb wrong" ); +#define DIAG_308_RC_OK 0x0001 +#define DIAG_308_RC_NO_CONF 0x0102 +#define DIAG_308_RC_INVALID 0x0402 + +#define DIAG308_RESET_MOD_CLR 0 +#define DIAG308_RESET_LOAD_NORM 1 +#define DIAG308_LOAD_CLEAR 3 +#define DIAG308_LOAD_NORMAL_DUMP 4 +#define DIAG308_SET 5 +#define DIAG308_STORE 6 +#define S390_IPL_TYPE_FCP 0x00#define S390_IPL_TYPE_CCW 0x02#define S390_IPL_TYPE_QEMU_SCSI 0xff
target/s390x/diag.c +0 -11
@@ -49,17 +49,6 @@ int handle_diag_288(CPUS390XState *env, uint64_t r1, uint64_t r3)return diag288_class->handle_timer (diag288, func, timeout); } -#define DIAG_308_RC_OK 0x0001 -#define DIAG_308_RC_NO_CONF 0x0102 -#define DIAG_308_RC_INVALID 0x0402 - -#define DIAG308_RESET_MOD_CLR 0 -#define DIAG308_RESET_LOAD_NORM 1 -#define DIAG308_LOAD_CLEAR 3 -#define DIAG308_LOAD_NORMAL_DUMP 4 -#define DIAG308_SET 5 -#define DIAG308_STORE 6 -static int diag308_parm_check (CPUS390XState *env,uint64_t r1,uint64_t addr,uintptr_t ra,bool write) {
Signature · 1 line
2.25.1
Re: [PATCH v10 01/16] s390x: Move diagnose 308 subcodes and rcs into ipl.h
Quoted 8 lines · On Wed, 18 Mar 2020 10:30:32 -0400 Janosch Frank <[email protected]> wrote:
They are part of the IPL process, so let's put them into the ipl header.
Signed-off-by Janosch Frank <[email protected]>--- hw/s390x/ipl.h | 11 +++++++++++ target/s390x/diag.c | 11 ----------- 2 files changed, 11 insertions(+), 11 deletions(-)
Re: [PATCH v10 01/16] s390x: Move diagnose 308 subcodes and rcs into ipl.h
In reply to Janosch FrankQuoted 4 lines · Janosch Frank
They are part of the IPL process, so let's put them into the ipl header.
Signed-off-by Janosch Frank <[email protected]>
Quoted 50 lines
--- hw/s390x/ipl.h | 11 +++++++++++ target/s390x/diag.c | 11 ----------- 2 files changed, 11 insertions(+), 11 deletions(-)hw/s390x/ipl.h +11
-0@@ -159,6 +159,17 @@ struct S390IPLState {typedef struct S390IPLState S390IPLState ;QEMU_BUILD_BUG_MSG (offsetof(S390IPLState , iplb) &3 ,"alignment of iplb wrong" ); +#define DIAG_308_RC_OK 0x0001 +#define DIAG_308_RC_NO_CONF 0x0102 +#define DIAG_308_RC_INVALID 0x0402 + +#define DIAG308_RESET_MOD_CLR 0 +#define DIAG308_RESET_LOAD_NORM 1 +#define DIAG308_LOAD_CLEAR 3 +#define DIAG308_LOAD_NORMAL_DUMP 4 +#define DIAG308_SET 5 +#define DIAG308_STORE 6 +#define S390_IPL_TYPE_FCP 0x00#define S390_IPL_TYPE_CCW 0x02#define S390_IPL_TYPE_QEMU_SCSI 0xfftarget/s390x/diag.c +0
-11@@ -49,17 +49,6 @@ int handle_diag_288(CPUS390XState *env, uint64_t r1, uint64_t r3)return diag288_class->handle_timer (diag288, func, timeout); } -#define DIAG_308_RC_OK 0x0001 -#define DIAG_308_RC_NO_CONF 0x0102 -#define DIAG_308_RC_INVALID 0x0402 - -#define DIAG308_RESET_MOD_CLR 0 -#define DIAG308_RESET_LOAD_NORM 1 -#define DIAG308_LOAD_CLEAR 3 -#define DIAG308_LOAD_NORMAL_DUMP 4 -#define DIAG308_SET 5 -#define DIAG308_STORE 6 -static int diag308_parm_check (CPUS390XState *env,uint64_t r1,uint64_t addr,uintptr_t ra,bool write) {
Re: [PATCH v10 01/16] s390x: Move diagnose 308 subcodes and rcs into ipl.h
In reply to Janosch FrankQuoted 4 lines · On Wed, 18 Mar 2020 10:30:32 -0400 Janosch Frank <[email protected]> wrote:
They are part of the IPL process, so let's put them into the ipl header.
Signed-off-by Janosch Frank <[email protected]>
Quoted 49 lines
--- hw/s390x/ipl.h | 11 +++++++++++ target/s390x/diag.c | 11 ----------- 2 files changed, 11 insertions(+), 11 deletions(-)hw/s390x/ipl.h +11
-0@@ -159,6 +159,17 @@ struct S390IPLState {typedef struct S390IPLState S390IPLState ; QEMU_BUILD_BUG_MSG(offsetof(S390IPLState, iplb) & 3, "alignment of iplb wrong"); +#define DIAG_308_RC_OK 0x0001 +#define DIAG_308_RC_NO_CONF 0x0102 +#define DIAG_308_RC_INVALID 0x0402 + +#define DIAG308_RESET_MOD_CLR 0 +#define DIAG308_RESET_LOAD_NORM 1 +#define DIAG308_LOAD_CLEAR 3 +#define DIAG308_LOAD_NORMAL_DUMP 4 +#define DIAG308_SET 5 +#define DIAG308_STORE 6 +#define S390_IPL_TYPE_FCP 0x00#define S390_IPL_TYPE_CCW 0x02#define S390_IPL_TYPE_QEMU_SCSI 0xfftarget/s390x/diag.c +0
-11@@ -49,17 +49,6 @@ int handle_diag_288(CPUS390XState *env, uint64_t r1, uint64_t r3) return diag288_class->handle_timer(diag288, func, timeout); } -#define DIAG_308_RC_OK 0x0001 -#define DIAG_308_RC_NO_CONF 0x0102 -#define DIAG_308_RC_INVALID 0x0402 - -#define DIAG308_RESET_MOD_CLR 0 -#define DIAG308_RESET_LOAD_NORM 1 -#define DIAG308_LOAD_CLEAR 3 -#define DIAG308_LOAD_NORMAL_DUMP 4 -#define DIAG308_SET 5 -#define DIAG308_STORE 6 -static int diag308_parm_check (CPUS390XState *env,uint64_t r1,uint64_t addr,uintptr_t ra,bool write) {
PATCH v10 2/16 Sync pv
In reply to Janosch Frank--- linux-headers/linux/kvm.h | 45 +++++++++++++++++++++++++++++++++++++-- 1 file changed, 43 insertions(+), 2 deletions(-)
linux-headers/linux/kvm.h +43 -2
@@ -474,12 +474,17 @@ struct kvm_s390_mem_op {__u32 size;/* amount of bytes */ __u32 op;/* type of operation */ __u64 buf;/* buffer in userspace */ -__u8 ar;/* the access register number */ -__u8 reserved[31 ];/* should be set to 0 */ +union { +__u8 ar;/* the access register number */ +__u32 sida_offset;/* offset into the sida */ +__u8 reserved[32 ];/* should be set to 0 */ + }; };/* types for kvm_s390_mem_op->op */ #define KVM_S390_MEMOP_LOGICAL_READ 0#define KVM_S390_MEMOP_LOGICAL_WRITE 1 +#define KVM_S390_MEMOP_SIDA_READ 2 +#define KVM_S390_MEMOP_SIDA_WRITE 3/* flags for kvm_s390_mem_op->flags */ #define KVM_S390_MEMOP_F_CHECK_ONLY (1ULL << 0)#define KVM_S390_MEMOP_F_INJECT_EXCEPTION (1ULL << 1)
@@ -1010,6 +1015,7 @@ struct kvm_ppc_resize_hpt {#define KVM_CAP_ARM_NISV_TO_USER 177#define KVM_CAP_ARM_INJECT_EXT_DABT 178#define KVM_CAP_S390_VCPU_RESETS 179 +#define KVM_CAP_S390_PROTECTED 180#ifdef KVM_CAP_IRQ_ROUTING
@@ -1478,6 +1484,41 @@ struct kvm_enc_region {#define KVM_S390_NORMAL_RESET _IO(KVMIO, 0xc3)#define KVM_S390_CLEAR_RESET _IO(KVMIO, 0xc4) +struct kvm_s390_pv_sec_parm { +__u64 origin; +__u64 length; +}; + +struct kvm_s390_pv_unp { +__u64 addr; +__u64 size; +__u64 tweak; +}; + +enum pv_cmd_id { +KVM_PV_ENABLE , +KVM_PV_DISABLE , +KVM_PV_VM_SET_SEC_PARMS , +KVM_PV_VM_UNPACK , +KVM_PV_VM_VERIFY , +KVM_PV_VM_PREP_RESET , +KVM_PV_VM_UNSHARE_ALL , +KVM_PV_VCPU_CREATE , +KVM_PV_VCPU_DESTROY , +}; + +struct kvm_pv_cmd { +__u32 cmd;/* Command to be executed */ +__u16 rc;/* Ultravisor return code */ +__u16 rrc;/* Ultravisor return reason code */ +__u64 data;/* Data or address */ +__u32 flags;/* flags for future extensions. Must be 0 for now */ +__u32 reserved[3 ]; +}; + +/* Available with KVM_CAP_S390_PROTECTED */ +#define KVM_S390_PV_COMMAND _IOWR(KVMIO, 0xc5, struct kvm_pv_cmd) +/* Secure Encrypted Virtualization command */ enum sev_cmd_id {/* Guest initialization commands */
Signature · 1 line
2.25.1
PATCH v10 3/16 s390x: protvirt: Support unpack facility
In reply to Janosch FrankThe unpack facility provides the means to setup a protected guest. A protected guest cannot be introspected by the hypervisor or any user/administrator of the machine it is running on.
Protected guests are encrypted at rest and need a special boot mechanism via diag308 subcode 8 and 10.
Code 8 sets the PV specific IPLB which is retained separately from those set via code 5.
Code 10 is used to unpack the VM into protected memory, verify its integrity and start it.
to machine]
--- hw/s390x/Makefile.objs | 1 + hw/s390x/ipl.c | 59 +++++++++++++- hw/s390x/ipl.h | 91 ++++++++++++++++++++- hw/s390x/pv.c | 98 +++++++++++++++++++++++ hw/s390x/s390-virtio-ccw.c | 119 +++++++++++++++++++++++++++- include/hw/s390x/pv.h | 55 +++++++++++++ include/hw/s390x/s390-virtio-ccw.h | 1 + target/s390x/cpu.c | 2 + target/s390x/cpu_features_def.inc.h | 1 + target/s390x/diag.c | 39 ++++++++- target/s390x/kvm-stub.c | 5 ++ target/s390x/kvm.c | 5 ++ target/s390x/kvm_s390x.h | 1 + 13 files changed, 467 insertions(+), 10 deletions(-) create mode 100644 hw/s390x/pv.c create mode 100644 include/hw/s390x/pv.h
hw/s390x/Makefile.objs +1 -0
@@ -31,6 +31,7 @@ obj-y += tod-qemu.o obj-$(CONFIG_KVM) += tod-kvm.o obj-$(CONFIG_KVM) += s390-skeys-kvm.o obj-$(CONFIG_KVM) += s390-stattrib-kvm.o +obj-$(CONFIG_KVM) += pv.o obj-y += s390-ccw.o obj-y += ap-device.o obj-y += ap-bridge.o
hw/s390x/ipl.c +56 -3
90 lines not on this page · raw message
hw/s390x/ipl.h +90 -1
160 lines not on this page · raw message
hw/s390x/pv.c new file +98 -0
98 lines not on this page · raw message
hw/s390x/s390-virtio-ccw.c +115 -4
171 lines not on this page · raw message
include/hw/s390x/pv.h new file +55 -0
55 lines not on this page · raw message
include/hw/s390x/s390-virtio-ccw.h +1 -0
@@ -28,6 +28,7 @@ typedef struct S390CcwMachineState {/*< public >*/ bool aes_key_wrap;bool dea_key_wrap; +bool pv;uint8_t loadparm[8 ]; } S390CcwMachineState;
target/s390x/cpu.c +2 -0
@@ -37,6 +37,8 @@#include "sysemu/hw_accel.h" #include "hw/qdev-properties.h" #ifndef CONFIG_USER_ONLY +#include "hw/s390x/s390-virtio-ccw.h" +#include "hw/s390x/pv.h" #include "hw/boards.h" #include "sysemu/arch_init.h" #include "sysemu/sysemu.h"
target/s390x/cpu_features_def.inc.h +1 -0
@@ -107,6 +107,7 @@ DEF_FEAT(DEFLATE_BASE, "deflate-base", STFL, 151, "Deflate-conversion facility ( DEF_FEAT(VECTOR_PACKED_DECIMAL_ENH, "vxpdeh", STFL, 152, "Vector-Packed-Decimal-Enhancement Facility") DEF_FEAT(MSA_EXT_9, "msa9-base", STFL, 155, "Message-security-assist-extension-9 facility (excluding subfunctions)") DEF_FEAT(ETOKEN, "etoken", STFL, 156, "Etoken facility") +DEF_FEAT (UNPACK ,"unpack" ,STFL ,161 ,"Unpack facility" ) /* Features exposed via SCLP SCCB Byte 80 - 98 (bit numbers relative to byte-80) */DEF_FEAT (SIE_GSLS ,"gsls" ,SCLP_CONF_CHAR ,40 ,"SIE: Guest-storage-limit-suppression facility" )
target/s390x/diag.c +37 -2
@@ -20,6 +20,8 @@#include "sysemu/cpus.h" #include "hw/s390x/ipl.h" #include "hw/s390x/s390-virtio-ccw.h" +#include "hw/s390x/pv.h" +#include "kvm_s390x.h" int handle_diag_288 (CPUS390XState *env,uint64_t r1,uint64_t r3) {
@@ -52,6 +54,10 @@ int handle_diag_288(CPUS390XState *env, uint64_t r1, uint64_t r3)static int diag308_parm_check (CPUS390XState *env,uint64_t r1,uint64_t addr,uintptr_t ra,bool write) { +/* Handled by the Ultravisor */ +if (s390_is_pv ()) { +return 0 ; + }if ((r1 &1 ) || (addr & ~TARGET_PAGE_MASK )) {s390_program_interrupt (env,PGM_SPECIFICATION , ra);return -1 ;
@@ -67,6 +73,7 @@ static int diag308_parm_check(CPUS390XState *env, uint64_t r1, uint64_t addr,void handle_diag_308 (CPUS390XState *env,uint64_t r1,uint64_t r3,uintptr_t ra) { +bool valid;CPUState *cs =env_cpu (env);uint64_t addr = env->regs[r1];uint64_t subcode = env->regs[r3];
@@ -82,6 +89,11 @@ void handle_diag_308(CPUS390XState *env, uint64_t r1, uint64_t r3, uintptr_t ra)return ; } +if (subcode >=DIAG308_PV_SET && !s390_has_feat (S390_FEAT_UNPACK )) { +s390_program_interrupt (env,PGM_SPECIFICATION , ra); +return ; + } +switch (subcode) {case DIAG308_RESET_MOD_CLR :s390_ipl_reset_request (cs,S390_RESET_MODIFIED_CLEAR );
@@ -94,6 +106,7 @@ void handle_diag_308(CPUS390XState *env, uint64_t r1, uint64_t r3, uintptr_t ra)s390_ipl_reset_request (cs,S390_RESET_REIPL );break ;case DIAG308_SET : +case DIAG308_PV_SET :if (diag308_parm_check (env, r1, addr, ra, false)) {return ; }
@@ -106,7 +119,8 @@ void handle_diag_308(CPUS390XState *env, uint64_t r1, uint64_t r3, uintptr_t ra)cpu_physical_memory_read (addr, iplb,be32_to_cpu (iplb->len)); -if (!iplb_valid (iplb)) { + valid = subcode ==DIAG308_PV_SET ?iplb_valid_pv (iplb) :iplb_valid (iplb); +if (!valid) { env->regs[r1 +1 ] =DIAG_308_RC_INVALID ; goto out; }
@@ -117,10 +131,15 @@ out:g_free (iplb);return ;case DIAG308_STORE : +case DIAG308_PV_STORE :if (diag308_parm_check (env, r1, addr, ra, true)) {return ; } - iplb =s390_ipl_get_iplb (); +if (subcode ==DIAG308_PV_STORE ) { + iplb =s390_ipl_get_iplb_pv (); + }else { + iplb =s390_ipl_get_iplb (); + }if (iplb) {cpu_physical_memory_write (addr, iplb,be32_to_cpu (iplb->len)); env->regs[r1 +1 ] =DIAG_308_RC_OK ;
@@ -128,6 +147,22 @@ out: env->regs[r1 +1 ] =DIAG_308_RC_NO_CONF ; }return ; +case DIAG308_PV_START : + iplb =s390_ipl_get_iplb_pv (); +if (!iplb) { + env->regs[r1 +1 ] =DIAG_308_RC_NO_PV_CONF ; +return ; + } + +if (kvm_s390_get_hpage_1m ()) { +error_report ("Protected VMs can currently not be backed with " +"huge pages" ); + env->regs[r1 +1 ] =DIAG_308_RC_INVAL_FOR_PV ; +return ; + } + +s390_ipl_reset_request (cs,S390_RESET_PV ); +break ;default :s390_program_interrupt (env,PGM_SPECIFICATION , ra);break ;
target/s390x/kvm-stub.c +5 -0
@@ -39,6 +39,11 @@ int kvm_s390_vcpu_interrupt_post_load(S390CPU *cpu)return 0 ; } +int kvm_s390_get_hpage_1m (void ) +{ +return 0 ; +} +int kvm_s390_get_ri (void ) {return 0 ;
target/s390x/kvm.c +5 -0
@@ -321,6 +321,11 @@ void kvm_s390_set_max_pagesize(uint64_t pagesize, Error **errp) cap_hpage_1m =1 ; } +int kvm_s390_get_hpage_1m (void ) +{ +return cap_hpage_1m; +} +static void ccw_machine_class_foreach (ObjectClass *oc,void *opaque) {MachineClass *mc =MACHINE_CLASS (oc);
target/s390x/kvm_s390x.h +1 -0
@@ -23,6 +23,7 @@ void kvm_s390_program_interrupt(S390CPU *cpu, uint16_t code);int kvm_s390_set_cpu_state (S390CPU *cpu,uint8_t cpu_state);void kvm_s390_vcpu_interrupt_pre_save (S390CPU *cpu);int kvm_s390_vcpu_interrupt_post_load (S390CPU *cpu); +int kvm_s390_get_hpage_1m (void );int kvm_s390_get_ri (void );int kvm_s390_get_gs (void );int kvm_s390_get_clock (uint8_t *tod_high,uint64_t *tod_clock);
Signature · 1 line
2.25.1
Re: [PATCH v10 03/16] s390x: protvirt: Support unpack facility
Quoted 15 lines · On Wed, 18 Mar 2020 10:30:34 -0400 Janosch Frank <[email protected]> wrote:
The unpack facility provides the means to setup a protected guest. A protected guest cannot be introspected by the hypervisor or any user/administrator of the machine it is running on.
Protected guests are encrypted at rest and need a special boot mechanism via diag308 subcode 8 and 10.
Code 8 sets the PV specific IPLB which is retained separately from those set via code 5.
Code 10 is used to unpack the VM into protected memory, verify its integrity and start it.
Signed-off-by Janosch Frank <[email protected]>Co-developed-by Christian Borntraeger <[email protected]> [Changes
Quoted 8 lines
to machine]
Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- hw/s390x/Makefile.objs | 1 + hw/s390x/ipl.c | 59 +++++++++++++- hw/s390x/ipl.h | 91 ++++++++++++++++++++- hw/s390x/pv.c | 98 +++++++++++++++++++++++
More of an aside: In MAINTAINERS, this new file will be covered by the general s390x section, the tcg section, and the s390-ccw-virtio machine section, but not by the kvm section. Do we want to tweak that?
Quoted 12 lines
hw/s390x/s390-virtio-ccw.c | 119 +++++++++++++++++++++++++++- include/hw/s390x/pv.h | 55 +++++++++++++ include/hw/s390x/s390-virtio-ccw.h | 1 + target/s390x/cpu.c | 2 + target/s390x/cpu_features_def.inc.h | 1 + target/s390x/diag.c | 39 ++++++++- target/s390x/kvm-stub.c | 5 ++ target/s390x/kvm.c | 5 ++ target/s390x/kvm_s390x.h | 1 + 13 files changed, 467 insertions(+), 10 deletions(-) create mode 100644 hw/s390x/pv.c create mode 100644 include/hw/s390x/pv.h
(...)
target/s390x/cpu.c line 41
Quoted 10 lines
target/s390x/cpu.c +2
-0@@ -37,6 +37,8 @@#include "sysemu/hw_accel.h" #include "hw/qdev-properties.h" #ifndef CONFIG_USER_ONLY +#include "hw/s390x/s390-virtio-ccw.h" +#include "hw/s390x/pv.h"
These are probably needed because of some inline stuff dragging definitions in?
target/s390x/cpu.c line 44
Quoted 3 lines
target/s390x/cpu.c +0
-0#include "hw/boards.h" #include "sysemu/arch_init.h" #include "sysemu/sysemu.h"
Re: [PATCH v10 03/16] s390x: protvirt: Support unpack facility
Quoted 27 lines · Cornelia Huck
Quoted 15 lines · On Wed, 18 Mar 2020 10:30:34 -0400 Janosch Frank <[email protected]> wrote:
The unpack facility provides the means to setup a protected guest. A protected guest cannot be introspected by the hypervisor or any user/administrator of the machine it is running on.
Protected guests are encrypted at rest and need a special boot mechanism via diag308 subcode 8 and 10.
Code 8 sets the PV specific IPLB which is retained separately from those set via code 5.
Code 10 is used to unpack the VM into protected memory, verify its integrity and start it.
Signed-off-by Janosch Frank <[email protected]>Co-developed-by Christian Borntraeger <[email protected]> [ChangesQuoted 8 lines
to machine]
Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- hw/s390x/Makefile.objs | 1 + hw/s390x/ipl.c | 59 +++++++++++++- hw/s390x/ipl.h | 91 ++++++++++++++++++++- hw/s390x/pv.c | 98 +++++++++++++++++++++++
Quoted 3 lines
More of an aside: In
MAINTAINERS, this new file will be covered by the general s390x section, the tcg section, and the s390-ccw-virtio machine section, but not by the kvm section. Do we want to tweak that?
@Christian?
Quoted 16 lines
Quoted 13 lines
hw/s390x/s390-virtio-ccw.c | 119 +++++++++++++++++++++++++++- include/hw/s390x/pv.h | 55 +++++++++++++ include/hw/s390x/s390-virtio-ccw.h | 1 + target/s390x/cpu.c | 2 + target/s390x/cpu_features_def.inc.h | 1 + target/s390x/diag.c | 39 ++++++++- target/s390x/kvm-stub.c | 5 ++ target/s390x/kvm.c | 5 ++ target/s390x/kvm_s390x.h | 1 + 13 files changed, 467 insertions(+), 10 deletions(-) create mode 100644 hw/s390x/pv.c create mode 100644 include/hw/s390x/pv.h(...)
Quoted 13 lines
target/s390x/cpu.c line 41
Quoted 10 lines
target/s390x/cpu.c +2
-0@@ -37,6 +37,8 @@#include "sysemu/hw_accel.h" #include "hw/qdev-properties.h" #ifndef CONFIG_USER_ONLY +#include "hw/s390x/s390-virtio-ccw.h" +#include "hw/s390x/pv.h" These are probably needed because of some inline stuff dragging definitions in?
Good catch.pv.h is needed for s390_is_pv()
But since pv.h includes s390-virtio-ccw.h I can remove it. I'll throw this through the CI to make sure it works on all s390x compile targets
Quoted 7 lines
target/s390x/cpu.c line 44
Quoted 4 lines
target/s390x/cpu.c +0
-0#include "hw/boards.h" #include "sysemu/arch_init.h" #include "sysemu/sysemu.h" Reviewed-by Cornelia Huck <[email protected]>
Thanks
Re: [PATCH v10 03/16] s390x: protvirt: Support unpack facility
Quoted 28 lines · Janosch Frank
Quoted 27 lines · Cornelia Huck
Quoted 23 lines · On Wed, 18 Mar 2020 10:30:34 -0400 Janosch Frank <[email protected]> wrote:
The unpack facility provides the means to setup a protected guest. A protected guest cannot be introspected by the hypervisor or any user/administrator of the machine it is running on.
Protected guests are encrypted at rest and need a special boot mechanism via diag308 subcode 8 and 10.
Code 8 sets the PV specific IPLB which is retained separately from those set via code 5.
Code 10 is used to unpack the VM into protected memory, verify its integrity and start it.
Signed-off-by Janosch Frank <[email protected]>Co-developed-by Christian Borntraeger <[email protected]> [Changesto machine]
Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- hw/s390x/Makefile.objs | 1 + hw/s390x/ipl.c | 59 +++++++++++++- hw/s390x/ipl.h | 91 ++++++++++++++++++++- hw/s390x/pv.c | 98 +++++++++++++++++++++++
Quoted 5 lines
Quoted 3 lines
More of an aside: In
MAINTAINERS, this new file will be covered by the general s390x section, the tcg section, and the s390-ccw-virtio machine section, but not by the kvm section. Do we want to tweak that?@Christian?
Yes, pv.c should be covered by the KVM section.
Re: [PATCH v10 03/16] s390x: protvirt: Support unpack facility
Quoted 31 lines · Christian Borntraeger
Quoted 28 lines · Janosch Frank
Quoted 27 lines · Cornelia Huck
Quoted 23 lines · On Wed, 18 Mar 2020 10:30:34 -0400 Janosch Frank <[email protected]> wrote:
The unpack facility provides the means to setup a protected guest. A protected guest cannot be introspected by the hypervisor or any user/administrator of the machine it is running on.
Protected guests are encrypted at rest and need a special boot mechanism via diag308 subcode 8 and 10.
Code 8 sets the PV specific IPLB which is retained separately from those set via code 5.
Code 10 is used to unpack the VM into protected memory, verify its integrity and start it.
Signed-off-by Janosch Frank <[email protected]>Co-developed-by Christian Borntraeger <[email protected]> [Changesto machine]
Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- hw/s390x/Makefile.objs | 1 + hw/s390x/ipl.c | 59 +++++++++++++- hw/s390x/ipl.h | 91 ++++++++++++++++++++- hw/s390x/pv.c | 98 +++++++++++++++++++++++
Quoted 9 lines
Quoted 5 lines
Quoted 3 lines
More of an aside: In
MAINTAINERS, this new file will be covered by the general s390x section, the tcg section, and the s390-ccw-virtio machine section, but not by the kvm section. Do we want to tweak that?@Christian?
Yes,
pv.cshould be covered by the KVM section.
Ok, I'll add it
PATCH v10 4/16 s390x: protvirt: Add migration blocker
In reply to Janosch FrankMigration is not yet supported.
--- hw/s390x/s390-virtio-ccw.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
hw/s390x/s390-virtio-ccw.c +18 -0
@@ -44,6 +44,9 @@#include "sysemu/sysemu.h" #include "hw/s390x/pv.h" #include <linux/kvm.h> +#include "migration/blocker.h" + +static Error *pv_mig_blocker;S390CPU *s390_cpu_addr2state (uint16_t cpu_addr) {
@@ -323,15 +326,30 @@ static void s390_machine_unprotect(S390CcwMachineState *ms) {s390_pv_vm_disable (); ms->pv = false; +migrate_del_blocker (pv_mig_blocker); +error_free_or_abort (&pv_mig_blocker); }static int s390_machine_protect (S390CcwMachineState *ms) { +Error *local_err =NULL ;int rc; +error_setg (&pv_mig_blocker, +"protected VMs are currently not migrateable." ); + rc =migrate_add_blocker (pv_mig_blocker, &local_err); +if (rc) { +error_report_err (local_err); +error_free_or_abort (&pv_mig_blocker); +return rc; + } +/* Create SE VM */ rc =s390_pv_vm_enable ();if (rc) { +error_report_err (local_err); +migrate_del_blocker (pv_mig_blocker); +error_free_or_abort (&pv_mig_blocker);return rc; }
Signature · 1 line
2.25.1
PATCH v10 5/16 s390x: protvirt: Inhibit balloon when switching to protected mode
In reply to Janosch FrankBallooning in protected VMs can only be done when the guest shares the pages it gives to the host. If pages are not shared, the integrity checks will fail once those pages have been altered and are given back to the guest.
As we currently do not yet have a solution for this we will continue like this:
1. We block ballooning now in QEMU (with this patch).
2. Later we will provide a change to virtio that removes the blocker and adds VIRTIO_F_IOMMU_PLATFORM automatically by QEMU when doing the protvirt switch. This is OK, as the balloon driver in Linux (the only supported guest) will refuse to work with the IOMMU_PLATFORM feature bit set.
3. Later, we can fix the guest balloon driver to accept the IOMMU feature bit and correctly exercise sharing and unsharing of balloon pages.
--- hw/s390x/s390-virtio-ccw.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
hw/s390x/s390-virtio-ccw.c +11 -0
@@ -42,6 +42,7 @@#include "hw/qdev-properties.h" #include "hw/s390x/tod.h" #include "sysemu/sysemu.h" +#include "sysemu/balloon.h" #include "hw/s390x/pv.h" #include <linux/kvm.h> #include "migration/blocker.h"
@@ -328,6 +329,7 @@ static void s390_machine_unprotect(S390CcwMachineState *ms) ms->pv = false;migrate_del_blocker (pv_mig_blocker);error_free_or_abort (&pv_mig_blocker); +qemu_balloon_inhibit (false); }static int s390_machine_protect (S390CcwMachineState *ms)
@@ -335,10 +337,18 @@ static int s390_machine_protect(S390CcwMachineState *ms)Error *local_err =NULL ;int rc; +/* +* Ballooning on protected VMs needs support in the guest for +* sharing and unsharing balloon pages. Block ballooning for +* now, until we have a solution to make at least Linux guests +* either support it or fail gracefully. +*/ +qemu_balloon_inhibit (true);error_setg (&pv_mig_blocker,"protected VMs are currently not migrateable." ); rc =migrate_add_blocker (pv_mig_blocker, &local_err);if (rc) { +qemu_balloon_inhibit (false);error_report_err (local_err);error_free_or_abort (&pv_mig_blocker);return rc;
@@ -347,6 +357,7 @@ static int s390_machine_protect(S390CcwMachineState *ms)/* Create SE VM */ rc =s390_pv_vm_enable ();if (rc) { +qemu_balloon_inhibit (false);error_report_err (local_err);migrate_del_blocker (pv_mig_blocker);error_free_or_abort (&pv_mig_blocker);
Signature · 1 line
2.25.1
Re: [PATCH v10 05/16] s390x: protvirt: Inhibit balloon when switching to protected mode
Quoted 20 lines · On Wed, 18 Mar 2020 10:30:36 -0400 Janosch Frank <[email protected]> wrote:
Ballooning in protected VMs can only be done when the guest shares the pages it gives to the host. If pages are not shared, the integrity checks will fail once those pages have been altered and are given back to the guest.
As we currently do not yet have a solution for this we will continue like this:
1. We block ballooning now in QEMU (with this patch).
2. Later we will provide a change to virtio that removes the blocker and adds
VIRTIO_F_IOMMU_PLATFORMautomatically by QEMU when doing the protvirt switch. This is OK, as the balloon driver in Linux (the only supported guest) will refuse to work with theIOMMU_PLATFORMfeature bit set.3. Later, we can fix the guest balloon driver to accept the IOMMU feature bit and correctly exercise sharing and unsharing of balloon pages.
Quoted 7 lines
Signed-off-by Janosch Frank <[email protected]>Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Christian Borntraeger <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- hw/s390x/s390-virtio-ccw.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
PATCH v10 6/16 s390x: protvirt: KVM intercept changes
In reply to Janosch FrankProtected VMs no longer intercept with code 4 for an instruction interception. Instead they have codes 104 and 108 for protected instruction interception and protected instruction notification respectively.
The 104 mirrors the 4 interception.
The 108 is a notification interception to let KVM and QEMU know that something changed and we need to update tracking information or perform specific tasks. It's currently taken for the following instructions:
* spx (To inform about the changed prefix location)
* sclp (On incorrect SCCB values, so we can inject a IRQ)
* sigp (All but "stop and store status")
* diag308 (Subcodes 0/1)
Of these exits only sclp errors, state changing sigps and diag308 will reach QEMU. QEMU will do its parts of the job, while the ultravisor has done the instruction part of the job.
--- target/s390x/kvm.c | 4 ++++ 1 file changed, 4 insertions(+)
target/s390x/kvm.c +4 -0
@@ -115,6 +115,8 @@#define ICPT_CPU_STOP 0x28#define ICPT_OPEREXC 0x2c#define ICPT_IO 0x40 +#define ICPT_PV_INSTR 0x68 +#define ICPT_PV_INSTR_NOTIFICATION 0x6c#define NR_LOCAL_IRQS 32/*
@@ -1698,6 +1700,8 @@ static int handle_intercept(S390CPU *cpu) (long)cs->kvm_run->psw_addr);switch (icpt_code) {case ICPT_INSTRUCTION : +case ICPT_PV_INSTR : +case ICPT_PV_INSTR_NOTIFICATION : r =handle_instruction (cpu, run);break ;case ICPT_PROGRAM :
Signature · 1 line
2.25.1
PATCH v10 7/16 s390x: Add SIDA memory ops
In reply to Janosch FrankProtected guests save the instruction control blocks in the SIDA instead of QEMU/KVM directly accessing the guest's memory.
Let's introduce new functions to access the SIDA.
The memops for doing so are available with KVM_CAP_S390_PROTECTED, so let's check for that.
--- target/s390x/cpu.h | 7 ++++++- target/s390x/kvm.c | 26 ++++++++++++++++++++++++++ target/s390x/kvm_s390x.h | 2 ++ target/s390x/mmu_helper.c | 14 ++++++++++++++ 4 files changed, 48 insertions(+), 1 deletion(-)
target/s390x/cpu.h +6 -1
@@ -823,7 +823,12 @@ int s390_cpu_virt_mem_rw(S390CPU *cpu, vaddr laddr, uint8_t ar, void *hostbuf,#define s390_cpu_virt_mem_check_write (cpu, laddr, ar, len) \ s390_cpu_virt_mem_rw(cpu, laddr, ar, NULL, len, true)void s390_cpu_virt_mem_handle_exc (S390CPU *cpu,uintptr_t ra); - +int s390_cpu_pv_mem_rw (S390CPU *cpu,unsigned int offset,void *hostbuf, +int len,bool is_write); +#define s390_cpu_pv_mem_read (cpu, offset, dest, len) \ + s390_cpu_pv_mem_rw(cpu, offset, dest, len, false) +#define s390_cpu_pv_mem_write (cpu, offset, dest, len) \ + s390_cpu_pv_mem_rw(cpu, offset, dest, len, true)/* sigp.c */ int s390_cpu_restart (S390CPU *cpu);
target/s390x/kvm.c +26 -0
@@ -154,6 +154,7 @@ static int cap_ri;static int cap_gs;static int cap_hpage_1m;static int cap_vcpu_resets; +static int cap_protected;static int active_cmma;
@@ -351,6 +352,7 @@ int kvm_arch_init(MachineState *ms, KVMState *s) cap_mem_op =kvm_check_extension (s,KVM_CAP_S390_MEM_OP ); cap_s390_irq =kvm_check_extension (s,KVM_CAP_S390_INJECT_IRQ ); cap_vcpu_resets =kvm_check_extension (s,KVM_CAP_S390_VCPU_RESETS ); + cap_protected =kvm_check_extension (s,KVM_CAP_S390_PROTECTED );if (!kvm_check_extension (s,KVM_CAP_S390_GMAP ) || !kvm_check_extension (s,KVM_CAP_S390_COW )) {
@@ -851,6 +853,30 @@ int kvm_s390_mem_op(S390CPU *cpu, vaddr addr, uint8_t ar, void *hostbuf,return ret; } +int kvm_s390_mem_op_pv (S390CPU *cpu,uint64_t offset,void *hostbuf, +int len,bool is_write) +{ +struct kvm_s390_mem_op mem_op = { + .sida_offset = offset, + .size = len, + .op = is_write ?KVM_S390_MEMOP_SIDA_WRITE + :KVM_S390_MEMOP_SIDA_READ , + .buf = (uint64_t )hostbuf, + }; +int ret; + +if (!cap_mem_op || !cap_protected) { +return -ENOSYS ; + } + + ret =kvm_vcpu_ioctl (CPU (cpu),KVM_S390_MEM_OP , &mem_op); +if (ret <0 ) { +error_report ("KVM_S390_MEM_OP failed: %s" ,strerror (-ret)); +abort (); + } +return ret; +} +/* * Legacy layout for s390: * Older S390 KVM requires the topmost vma of the RAM to be
target/s390x/kvm_s390x.h +2 -0
@@ -19,6 +19,8 @@ void kvm_s390_vcpu_interrupt(S390CPU *cpu, struct kvm_s390_irq *irq);void kvm_s390_access_exception (S390CPU *cpu,uint16_t code,uint64_t te_code);int kvm_s390_mem_op (S390CPU *cpu,vaddr addr,uint8_t ar,void *hostbuf,int len,bool is_write); +int kvm_s390_mem_op_pv (S390CPU *cpu,vaddr addr,void *hostbuf,int len, +bool is_write);void kvm_s390_program_interrupt (S390CPU *cpu,uint16_t code);int kvm_s390_set_cpu_state (S390CPU *cpu,uint8_t cpu_state);void kvm_s390_vcpu_interrupt_pre_save (S390CPU *cpu);
target/s390x/mmu_helper.c +14 -0
@@ -474,6 +474,20 @@ static int translate_pages(S390CPU *cpu, vaddr addr, int nr_pages,return 0 ; } +int s390_cpu_pv_mem_rw (S390CPU *cpu,unsigned int offset,void *hostbuf, +int len,bool is_write) +{ +int ret; + +if (kvm_enabled ()) { + ret =kvm_s390_mem_op_pv (cpu, offset, hostbuf, len, is_write); + }else { +/* Protected Virtualization is a KVM/Hardware only feature */ +g_assert_not_reached (); + } +return ret; +} +/** * s390_cpu_virt_mem_rw: * @laddr: the logical start address
Signature · 1 line
2.25.1
PATCH v10 8/16 s390x: protvirt: Move STSI data over SIDAD
In reply to Janosch FrankFor protected guests, we need to put the STSI emulation results into the SIDA, so SIE will write them into the guest at the next entry.
--- target/s390x/kvm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)
target/s390x/kvm.c +9 -2
@@ -50,6 +50,7 @@#include "exec/memattrs.h" #include "hw/s390x/s390-virtio-ccw.h" #include "hw/s390x/s390-virtio-hcall.h" +#include "hw/s390x/pv.h" #ifndef DEBUG_KVM #define DEBUG_KVM 0
@@ -1806,7 +1807,9 @@ static void insert_stsi_3_2_2(S390CPU *cpu, __u64 addr, uint8_t ar)SysIB_322 sysib;int del; -if (s390_cpu_virt_mem_read (cpu, addr, ar, &sysib,sizeof (sysib))) { +if (s390_is_pv ()) { +s390_cpu_pv_mem_read (cpu,0 , &sysib,sizeof (sysib)); + }else if (s390_cpu_virt_mem_read (cpu, addr, ar, &sysib,sizeof (sysib))) {return ; }/* Shift the stack of Extended Names to prepare for our own data */
@@ -1846,7 +1849,11 @@ static void insert_stsi_3_2_2(S390CPU *cpu, __u64 addr, uint8_t ar)/* Insert UUID */ memcpy (sysib.vm[0 ].uuid, &qemu_uuid,sizeof (sysib.vm[0 ].uuid)); -s390_cpu_virt_mem_write (cpu, addr, ar, &sysib,sizeof (sysib)); +if (s390_is_pv ()) { +s390_cpu_pv_mem_write (cpu,0 , &sysib,sizeof (sysib)); + }else { +s390_cpu_virt_mem_write (cpu, addr, ar, &sysib,sizeof (sysib)); + } }static int handle_stsi (S390CPU *cpu)
Signature · 1 line
2.25.1
Re: [PATCH v10 08/16] s390x: protvirt: Move STSI data over SIDAD
Quoted 23 lines · On Wed, 18 Mar 2020 10:30:39 -0400 Janosch Frank <[email protected]> wrote:
For protected guests, we need to put the STSI emulation results into the SIDA, so SIE will write them into the guest at the next entry.
Signed-off-by Janosch Frank <[email protected]>Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- target/s390x/kvm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)target/s390x/kvm.c +1
-0@@ -50,6 +50,7 @@#include "exec/memattrs.h" #include "hw/s390x/s390-virtio-ccw.h" #include "hw/s390x/s390-virtio-hcall.h" +#include "hw/s390x/pv.h" #ifndef DEBUG_KVM #define DEBUG_KVM 0
target/s390x/kvm.c static void insert_stsi_3_2_2(S390CPU *cpu, __u64 addr, uint8_t ar) · line 1811
Quoted 6 lines
target/s390x/kvm.c +2
-1@@ -1806,7 +1807,9 @@ static void insert_stsi_3_2_2(S390CPU *cpu, __u64 addr, uint8_t ar)SysIB_322 sysib;int del; -if (s390_cpu_virt_mem_read (cpu, addr, ar, &sysib,sizeof (sysib))) { +if (s390_is_pv ()) { +s390_cpu_pv_mem_read (cpu,0 , &sysib,sizeof (sysib));
The only minor issue I have here is that it is not obvious that this function either succeeds or aborts, as we only call it in the pv case. But it probably does not make that much sense to sprinkle comments everywhere, either.
Quoted 7 lines
target/s390x/kvm.c +1
-0+ }else if (s390_cpu_virt_mem_read (cpu, addr, ar, &sysib,sizeof (sysib))) {return ; }/* Shift the stack of Extended Names to prepare for our own data */ @@ -1846,7 +1849,11 @@ static void insert_stsi_3_2_2(S390CPU *cpu, __u64 addr, uint8_t ar)/* Insert UUID */ memcpy (sysib.vm[0 ].uuid, &qemu_uuid,sizeof (sysib.vm[0 ].uuid));
target/s390x/kvm.c static void insert_stsi_3_2_2(S390CPU *cpu, __u64 addr, uint8_t ar) · line 1859
Quoted 10 lines
target/s390x/kvm.c +5
-1-s390_cpu_virt_mem_write (cpu, addr, ar, &sysib,sizeof (sysib)); +if (s390_is_pv ()) { +s390_cpu_pv_mem_write (cpu,0 , &sysib,sizeof (sysib)); + }else { +s390_cpu_virt_mem_write (cpu, addr, ar, &sysib,sizeof (sysib)); + } }static int handle_stsi (S390CPU *cpu)
PATCH v10 9/16 s390x: protvirt: SCLP interpretation
In reply to Janosch FrankSCLP for a protected guest is done over the SIDAD, so we need to use the s390_cpu_pv_mem_* functions to access the SIDAD instead of guest memory when reading/writing SCBs.
To not confuse the sclp emulation, we set 0x4000 as the SCCB address, since the function that injects the sclp external interrupt would reject a zero sccb address.
--- hw/s390x/sclp.c | 65 ++++++++++++++++++++++++++++++++++------- include/hw/s390x/sclp.h | 2 ++ target/s390x/kvm.c | 25 ++++++++++++---- 3 files changed, 76 insertions(+), 16 deletions(-)
hw/s390x/sclp.c +54 -11
@@ -33,6 +33,22 @@ static inline SCLPDevice *get_sclp_device(void)return sclp; } +static inline bool sclp_command_code_valid (uint32_t code) +{ +switch (code &SCLP_CMD_CODE_MASK ) { +case SCLP_CMDW_READ_SCP_INFO : +case SCLP_CMDW_READ_SCP_INFO_FORCED : +case SCLP_CMDW_READ_CPU_INFO : +case SCLP_CMDW_CONFIGURE_IOA : +case SCLP_CMDW_DECONFIGURE_IOA : +case SCLP_CMD_READ_EVENT_DATA : +case SCLP_CMD_WRITE_EVENT_DATA : +case SCLP_CMD_WRITE_EVENT_MASK : +return true; + } +return false; +} +static void prepare_cpu_entries (SCLPDevice *sclp,CPUEntry *entry,int *count) {MachineState *ms =MACHINE (qdev_get_machine ());
@@ -193,6 +209,43 @@ static void sclp_execute(SCLPDevice *sclp, SCCB *sccb, uint32_t code) } } +/* +* We only need the address to have something valid for the +* service_interrupt call. +*/ +#define SCLP_PV_DUMMY_ADDR 0x4000 +int sclp_service_call_protected (CPUS390XState *env,uint64_t sccb, +uint32_t code) +{ +SCLPDevice *sclp =get_sclp_device (); +SCLPDeviceClass *sclp_c =SCLP_GET_CLASS (sclp); +SCCB work_sccb; +hwaddr sccb_len =sizeof (SCCB ); + +/* +* Only a very limited number of calls is permitted by the +* Ultravisor and we support all of them, so we don't check for +* them. All other specification exceptions are also interpreted +* by the Ultravisor and hence never cause an exit we need to +* handle. +* +* Setting the CC is also done by the Ultravisor. +*/ +s390_cpu_pv_mem_read (env_archcpu (env),0 , &work_sccb, sccb_len); + +if (!sclp_command_code_valid (code)) { + work_sccb.h.response_code =cpu_to_be16 (SCLP_RC_INVALID_SCLP_COMMAND ); + goto out_write; + } + + sclp_c->execute (sclp, &work_sccb, code); +out_write: +s390_cpu_pv_mem_write (env_archcpu (env),0 , &work_sccb, +be16_to_cpu (work_sccb.h.length)); + sclp_c->service_interrupt (sclp,SCLP_PV_DUMMY_ADDR ); +return 0 ; +} +int sclp_service_call (CPUS390XState *env,uint64_t sccb,uint32_t code) {SCLPDevice *sclp =get_sclp_device ();
@@ -225,17 +278,7 @@ int sclp_service_call(CPUS390XState *env, uint64_t sccb, uint32_t code)return -PGM_SPECIFICATION ; } -switch (code &SCLP_CMD_CODE_MASK ) { -case SCLP_CMDW_READ_SCP_INFO : -case SCLP_CMDW_READ_SCP_INFO_FORCED : -case SCLP_CMDW_READ_CPU_INFO : -case SCLP_CMDW_CONFIGURE_IOA : -case SCLP_CMDW_DECONFIGURE_IOA : -case SCLP_CMD_READ_EVENT_DATA : -case SCLP_CMD_WRITE_EVENT_DATA : -case SCLP_CMD_WRITE_EVENT_MASK : -break ; -default : +if (!sclp_command_code_valid (code)) { work_sccb.h.response_code =cpu_to_be16 (SCLP_RC_INVALID_SCLP_COMMAND ); goto out_write; }
include/hw/s390x/sclp.h +2 -0
@@ -217,5 +217,7 @@ void s390_sclp_init(void);void sclp_service_interrupt (uint32_t sccb);void raise_irq_cpu_hotplug (void );int sclp_service_call (CPUS390XState *env,uint64_t sccb,uint32_t code); +int sclp_service_call_protected (CPUS390XState *env,uint64_t sccb, +uint32_t code);#endif
target/s390x/kvm.c +20 -5
@@ -1233,12 +1233,27 @@ static void kvm_sclp_service_call(S390CPU *cpu, struct kvm_run *run, sccb = env->regs[ipbh0 &0xf ]; code = env->regs[(ipbh0 &0xf0 ) >>4 ]; - r =sclp_service_call (env, sccb, code); -if (r <0 ) { -kvm_s390_program_interrupt (cpu, -r); -return ; +switch (run->s390_sieic.icptcode) { +case ICPT_PV_INSTR_NOTIFICATION : +g_assert (s390_is_pv ()); +/* The notification intercepts are currently handled by KVM */ +error_report ("unexpected SCLP PV notification" ); +exit (1 ); +break ; +case ICPT_PV_INSTR : +g_assert (s390_is_pv ()); +sclp_service_call_protected (env, sccb, code); +/* Setting the CC is done by the Ultravisor. */ +break ; +case ICPT_INSTRUCTION : +g_assert (!s390_is_pv ()); + r =sclp_service_call (env, sccb, code); +if (r <0 ) { +kvm_s390_program_interrupt (cpu, -r); +return ; + } +setcc (cpu, r); } -setcc (cpu, r); }static int handle_b2 (S390CPU *cpu,struct kvm_run *run,uint8_t ipa1)
Signature · 1 line
2.25.1
Re: [PATCH v10 09/16] s390x: protvirt: SCLP interpretation
Quoted 54 lines · On Wed, 18 Mar 2020 10:30:40 -0400 Janosch Frank <[email protected]> wrote:
SCLP for a protected guest is done over the SIDAD, so we need to use the s390_cpu_pv_mem_* functions to access the SIDAD instead of guest memory when reading/writing SCBs.
To not confuse the sclp emulation, we set
0x4000as the SCCB address, since the function that injects the sclp external interrupt would reject a zero sccb address.Signed-off-by Janosch Frank <[email protected]>Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- hw/s390x/sclp.c | 65 ++++++++++++++++++++++++++++++++++------- include/hw/s390x/sclp.h | 2 ++ target/s390x/kvm.c | 25 ++++++++++++---- 3 files changed, 76 insertions(+), 16 deletions(-)hw/s390x/sclp.c +22
-0@@ -33,6 +33,22 @@ static inline SCLPDevice *get_sclp_device(void)return sclp; } +static inline bool sclp_command_code_valid (uint32_t code) +{ +switch (code &SCLP_CMD_CODE_MASK ) { +case SCLP_CMDW_READ_SCP_INFO : +case SCLP_CMDW_READ_SCP_INFO_FORCED : +case SCLP_CMDW_READ_CPU_INFO : +case SCLP_CMDW_CONFIGURE_IOA : +case SCLP_CMDW_DECONFIGURE_IOA : +case SCLP_CMD_READ_EVENT_DATA : +case SCLP_CMD_WRITE_EVENT_DATA : +case SCLP_CMD_WRITE_EVENT_MASK : +return true; + } +return false; +} +static void prepare_cpu_entries (SCLPDevice *sclp,CPUEntry *entry,int *count) {MachineState *ms =MACHINE (qdev_get_machine ());@@ -193,6 +209,43 @@ static void sclp_execute(SCLPDevice *sclp, SCCB *sccb, uint32_t code) } } +/* +* We only need the address to have something valid for the +* service_interrupt call. +*/ +#define SCLP_PV_DUMMY_ADDR 0x4000 +int sclp_service_call_protected(CPUS390XState *env, uint64_t sccb,
hw/s390x/sclp.c static void sclp_execute(SCLPDevice *sclp, SCCB *sccb, uint32_t code) · line 227
Quoted 10 lines
hw/s390x/sclp.c +10
-0+ uint32_t code) +{ +SCLPDevice *sclp =get_sclp_device (); +SCLPDeviceClass *sclp_c =SCLP_GET_CLASS (sclp); +SCCB work_sccb; +hwaddr sccb_len =sizeof (SCCB ); + +/* +* Only a very limited number of calls is permitted by the +* Ultravisor and we support all of them, so we don't check for
This is no longer true, no?
Quoted 24 lines
hw/s390x/sclp.c +21
-0+* them. All other specification exceptions are also interpreted +* by the Ultravisor and hence never cause an exit we need to +* handle. +* +* Setting the CC is also done by the Ultravisor. +*/ +s390_cpu_pv_mem_read (env_archcpu (env),0 , &work_sccb, sccb_len); + +if (!sclp_command_code_valid (code)) { + work_sccb.h.response_code =cpu_to_be16 (SCLP_RC_INVALID_SCLP_COMMAND ); + goto out_write; + } + + sclp_c->execute (sclp, &work_sccb, code); +out_write: +s390_cpu_pv_mem_write (env_archcpu (env),0 , &work_sccb, +be16_to_cpu (work_sccb.h.length)); + sclp_c->service_interrupt (sclp,SCLP_PV_DUMMY_ADDR ); +return 0 ; +} +int sclp_service_call (CPUS390XState *env,uint64_t sccb,uint32_t code) {SCLPDevice *sclp =get_sclp_device ();
Re: [PATCH v10 09/16] s390x: protvirt: SCLP interpretation
Quoted 61 lines · Cornelia Huck
Quoted 58 lines · On Wed, 18 Mar 2020 10:30:40 -0400 Janosch Frank <[email protected]> wrote:
SCLP for a protected guest is done over the SIDAD, so we need to use the s390_cpu_pv_mem_* functions to access the SIDAD instead of guest memory when reading/writing SCBs.
To not confuse the sclp emulation, we set
0x4000as the SCCB address, since the function that injects the sclp external interrupt would reject a zero sccb address.Signed-off-by Janosch Frank <[email protected]>Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- hw/s390x/sclp.c | 65 ++++++++++++++++++++++++++++++++++------- include/hw/s390x/sclp.h | 2 ++ target/s390x/kvm.c | 25 ++++++++++++---- 3 files changed, 76 insertions(+), 16 deletions(-)hw/s390x/sclp.c +26
-0@@ -33,6 +33,22 @@ static inline SCLPDevice *get_sclp_device(void)return sclp; } +static inline bool sclp_command_code_valid (uint32_t code) +{ +switch (code &SCLP_CMD_CODE_MASK ) { +case SCLP_CMDW_READ_SCP_INFO : +case SCLP_CMDW_READ_SCP_INFO_FORCED : +case SCLP_CMDW_READ_CPU_INFO : +case SCLP_CMDW_CONFIGURE_IOA : +case SCLP_CMDW_DECONFIGURE_IOA : +case SCLP_CMD_READ_EVENT_DATA : +case SCLP_CMD_WRITE_EVENT_DATA : +case SCLP_CMD_WRITE_EVENT_MASK : +return true; + } +return false; +} +static void prepare_cpu_entries (SCLPDevice *sclp,CPUEntry *entry,int *count) {MachineState *ms =MACHINE (qdev_get_machine ());@@ -193,6 +209,43 @@ static void sclp_execute(SCLPDevice *sclp, SCCB *sccb, uint32_t code) } } +/* +* We only need the address to have something valid for the +* service_interrupt call. +*/ +#define SCLP_PV_DUMMY_ADDR 0x4000 +int sclp_service_call_protected (CPUS390XState *env,uint64_t sccb, +uint32_t code) +{ +SCLPDevice *sclp =get_sclp_device (); +SCLPDeviceClass *sclp_c =SCLP_GET_CLASS (sclp);
Quoted 8 lines
hw/s390x/sclp.c static void sclp_execute(SCLPDevice *sclp, SCCB *sccb, uint32_t code) · line 227
Quoted 6 lines
hw/s390x/sclp.c +6
-0+SCCB work_sccb; +hwaddr sccb_len =sizeof (SCCB ); + +/* +* Only a very limited number of calls is permitted by the +* Ultravisor and we support all of them, so we don't check for This is no longer true, no?
Right, I just removed the comment.
Quoted 26 lines
Quoted 25 lines
hw/s390x/sclp.c +21
-0+* them. All other specification exceptions are also interpreted +* by the Ultravisor and hence never cause an exit we need to +* handle. +* +* Setting the CC is also done by the Ultravisor. +*/ +s390_cpu_pv_mem_read (env_archcpu (env),0 , &work_sccb, sccb_len); + +if (!sclp_command_code_valid (code)) { + work_sccb.h.response_code =cpu_to_be16 (SCLP_RC_INVALID_SCLP_COMMAND ); + goto out_write; + } + + sclp_c->execute (sclp, &work_sccb, code); +out_write: +s390_cpu_pv_mem_write (env_archcpu (env),0 , &work_sccb, +be16_to_cpu (work_sccb.h.length)); + sclp_c->service_interrupt (sclp,SCLP_PV_DUMMY_ADDR ); +return 0 ; +} +int sclp_service_call (CPUS390XState *env,uint64_t sccb,uint32_t code) {SCLPDevice *sclp =get_sclp_device ();
Cornelia Huck
Reviewed-byRe: [PATCH v10 09/16] s390x: protvirt: SCLP interpretation
Quoted 71 lines · On Thu, 19 Mar 2020 13:46:46 +0100 Janosch Frank <[email protected]> wrote:
Quoted 61 lines · Cornelia Huck
Quoted 58 lines · On Wed, 18 Mar 2020 10:30:40 -0400 Janosch Frank <[email protected]> wrote:
SCLP for a protected guest is done over the SIDAD, so we need to use the s390_cpu_pv_mem_* functions to access the SIDAD instead of guest memory when reading/writing SCBs.
To not confuse the sclp emulation, we set
0x4000as the SCCB address, since the function that injects the sclp external interrupt would reject a zero sccb address.Signed-off-by Janosch Frank <[email protected]>Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- hw/s390x/sclp.c | 65 ++++++++++++++++++++++++++++++++++------- include/hw/s390x/sclp.h | 2 ++ target/s390x/kvm.c | 25 ++++++++++++---- 3 files changed, 76 insertions(+), 16 deletions(-)hw/s390x/sclp.c +26
-0@@ -33,6 +33,22 @@ static inline SCLPDevice *get_sclp_device(void)return sclp; } +static inline bool sclp_command_code_valid (uint32_t code) +{ +switch (code &SCLP_CMD_CODE_MASK ) { +case SCLP_CMDW_READ_SCP_INFO : +case SCLP_CMDW_READ_SCP_INFO_FORCED : +case SCLP_CMDW_READ_CPU_INFO : +case SCLP_CMDW_CONFIGURE_IOA : +case SCLP_CMDW_DECONFIGURE_IOA : +case SCLP_CMD_READ_EVENT_DATA : +case SCLP_CMD_WRITE_EVENT_DATA : +case SCLP_CMD_WRITE_EVENT_MASK : +return true; + } +return false; +} +static void prepare_cpu_entries (SCLPDevice *sclp,CPUEntry *entry,int *count) {MachineState *ms =MACHINE (qdev_get_machine ());@@ -193,6 +209,43 @@ static void sclp_execute(SCLPDevice *sclp, SCCB *sccb, uint32_t code) } } +/* +* We only need the address to have something valid for the +* service_interrupt call. +*/ +#define SCLP_PV_DUMMY_ADDR 0x4000 +int sclp_service_call_protected (CPUS390XState *env,uint64_t sccb, +uint32_t code) +{ +SCLPDevice *sclp =get_sclp_device (); +SCLPDeviceClass *sclp_c =SCLP_GET_CLASS (sclp);Quoted 8 lines
hw/s390x/sclp.c static void sclp_execute(SCLPDevice *sclp, SCCB *sccb, uint32_t code) · line 227
Quoted 6 lines
hw/s390x/sclp.c +6
-0+SCCB work_sccb; +hwaddr sccb_len =sizeof (SCCB ); + +/* +* Only a very limited number of calls is permitted by the +* Ultravisor and we support all of them, so we don't check for This is no longer true, no?
Quoted 1 line
Right, I just removed the comment.
With that,
PATCH v10 10/16 s390x: protvirt: Set guest IPL PSW
In reply to Janosch FrankHandling of CPU reset and setting of the IPL psw from guest storage at offset 0 is done by a Ultravisor call. Let's only fetch it if necessary.
--- target/s390x/cpu.c | 26 +++++++++++++++++--------- 1 file changed, 17 insertions(+), 9 deletions(-)
target/s390x/cpu.c +17 -9
@@ -78,16 +78,24 @@ static bool s390_cpu_has_work(CPUState *cs)static void s390_cpu_load_normal (CPUState *s) {S390CPU *cpu =S390_CPU (s); -uint64_t spsw =ldq_phys (s->as,0 ); - - cpu->env.psw.mask = spsw &PSW_MASK_SHORT_CTRL ; -/* -* Invert short psw indication, so SIE will report a specification -* exception if it was not set. -*/ - cpu->env.psw.mask ^=PSW_MASK_SHORTPSW ; - cpu->env.psw.addr = spsw &PSW_MASK_SHORT_ADDR ; +uint64_t spsw; +if (!s390_is_pv ()) { + spsw =ldq_phys (s->as,0 ); + cpu->env.psw.mask = spsw &PSW_MASK_SHORT_CTRL ; +/* +* Invert short psw indication, so SIE will report a specification +* exception if it was not set. +*/ + cpu->env.psw.mask ^=PSW_MASK_SHORTPSW ; + cpu->env.psw.addr = spsw &PSW_MASK_SHORT_ADDR ; + }else { +/* +* Firmware requires us to set the load state before we set +* the cpu to operating on protected guests. +*/ +s390_cpu_set_state (S390_CPU_STATE_LOAD , cpu); + }s390_cpu_set_state (S390_CPU_STATE_OPERATING , cpu); }#endif
Signature · 1 line
2.25.1
Re: [PATCH v10 10/16] s390x: protvirt: Set guest IPL PSW
Quoted 37 lines · On Wed, 18 Mar 2020 10:30:41 -0400 Janosch Frank <[email protected]> wrote:
Handling of CPU reset and setting of the IPL psw from guest storage at offset 0 is done by a Ultravisor call. Let's only fetch it if necessary.
Signed-off-by Janosch Frank <[email protected]>Reviewed-by Thomas Huth <[email protected]>Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Christian Borntraeger <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- target/s390x/cpu.c | 26 +++++++++++++++++--------- 1 file changed, 17 insertions(+), 9 deletions(-)target/s390x/cpu.c +6
-9@@ -78,16 +78,24 @@ static bool s390_cpu_has_work(CPUState *cs)static void s390_cpu_load_normal (CPUState *s) {S390CPU *cpu =S390_CPU (s); -uint64_t spsw =ldq_phys (s->as,0 ); - - cpu->env.psw.mask = spsw &PSW_MASK_SHORT_CTRL ; -/* -* Invert short psw indication, so SIE will report a specification -* exception if it was not set. -*/ - cpu->env.psw.mask ^=PSW_MASK_SHORTPSW ; - cpu->env.psw.addr = spsw &PSW_MASK_SHORT_ADDR ; +uint64_t spsw; +if (!s390_is_pv ()) { + spsw =ldq_phys (s->as,0 ); + cpu->env.psw.mask = spsw &PSW_MASK_SHORT_CTRL ; +/* +* Invert short psw indication, so SIE will report a specification
target/s390x/cpu.c static bool s390_cpu_has_work(CPUState *cs) · line 97
Quoted 10 lines
target/s390x/cpu.c +10
-0+* exception if it was not set. +*/ + cpu->env.psw.mask ^=PSW_MASK_SHORTPSW ; + cpu->env.psw.addr = spsw &PSW_MASK_SHORT_ADDR ; + }else { +/* +* Firmware requires us to set the load state before we set +* the cpu to operating on protected guests. +*/ +s390_cpu_set_state (S390_CPU_STATE_LOAD , cpu);
We probably could do that unconditionally, but this is fine.
target/s390x/cpu.c static bool s390_cpu_has_work(CPUState *cs) · line 101
Quoted 4 lines
target/s390x/cpu.c +1
-0+ }s390_cpu_set_state (S390_CPU_STATE_OPERATING , cpu); }#endif
Re: [PATCH v10 10/16] s390x: protvirt: Set guest IPL PSW
Quoted 44 lines · Cornelia Huck
Quoted 41 lines · On Wed, 18 Mar 2020 10:30:41 -0400 Janosch Frank <[email protected]> wrote:
Handling of CPU reset and setting of the IPL psw from guest storage at offset 0 is done by a Ultravisor call. Let's only fetch it if necessary.
Signed-off-by Janosch Frank <[email protected]>Reviewed-by Thomas Huth <[email protected]>Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Christian Borntraeger <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- target/s390x/cpu.c | 26 +++++++++++++++++--------- 1 file changed, 17 insertions(+), 9 deletions(-)target/s390x/cpu.c +10
-9@@ -78,16 +78,24 @@ static bool s390_cpu_has_work(CPUState *cs)static void s390_cpu_load_normal (CPUState *s) {S390CPU *cpu =S390_CPU (s); -uint64_t spsw =ldq_phys (s->as,0 ); - - cpu->env.psw.mask = spsw &PSW_MASK_SHORT_CTRL ; -/* -* Invert short psw indication, so SIE will report a specification -* exception if it was not set. -*/ - cpu->env.psw.mask ^=PSW_MASK_SHORTPSW ; - cpu->env.psw.addr = spsw &PSW_MASK_SHORT_ADDR ; +uint64_t spsw; +if (!s390_is_pv ()) { + spsw =ldq_phys (s->as,0 ); + cpu->env.psw.mask = spsw &PSW_MASK_SHORT_CTRL ; +/* +* Invert short psw indication, so SIE will report a specification +* exception if it was not set. +*/ + cpu->env.psw.mask ^=PSW_MASK_SHORTPSW ; + cpu->env.psw.addr = spsw &PSW_MASK_SHORT_ADDR ;
Quoted 8 lines
target/s390x/cpu.c static bool s390_cpu_has_work(CPUState *cs) · line 97
Quoted 6 lines
target/s390x/cpu.c +6
-0+ }else { +/* +* Firmware requires us to set the load state before we set +* the cpu to operating on protected guests. +*/ +s390_cpu_set_state (S390_CPU_STATE_LOAD , cpu);We probably could do that unconditionally, but this is fine.
As far as I know the load state is only used by lpar and for a normal KVM guest it doesn't really make sense.
Specification for that state is however a bit sparse.
Quoted 7 lines
target/s390x/cpu.c static bool s390_cpu_has_work(CPUState *cs) · line 101
Quoted 5 lines
target/s390x/cpu.c +1
-0+ }s390_cpu_set_state (S390_CPU_STATE_OPERATING , cpu); }#endif Reviewed-by Cornelia Huck <[email protected]>
Thanks!
PATCH v10 11/16 s390x: protvirt: Move diag 308 data over SIDA
In reply to Janosch FrankFor protected guests the IPIB is written/read to/from the SIDA, so we need those accesses to go through s390_cpu_pv_mem_read/write().
--- target/s390x/diag.c | 27 +++++++++++++++++++++------ 1 file changed, 21 insertions(+), 6 deletions(-)
target/s390x/diag.c +21 -6
@@ -75,6 +75,7 @@ void handle_diag_308(CPUS390XState *env, uint64_t r1, uint64_t r3, uintptr_t ra) {bool valid;CPUState *cs =env_cpu (env); +S390CPU *cpu =S390_CPU (cs);uint64_t addr = env->regs[r1];uint64_t subcode = env->regs[r3];IplParameterBlock *iplb;
@@ -111,13 +112,22 @@ void handle_diag_308(CPUS390XState *env, uint64_t r1, uint64_t r3, uintptr_t ra)return ; } iplb =g_new0 (IplParameterBlock,1 ); -cpu_physical_memory_read (addr, iplb,sizeof (iplb->len)); +if (!s390_is_pv ()) { +cpu_physical_memory_read (addr, iplb,sizeof (iplb->len)); + }else { +s390_cpu_pv_mem_read (cpu,0 , iplb,sizeof (iplb->len)); + } +if (!iplb_valid_len (iplb)) { env->regs[r1 +1 ] =DIAG_308_RC_INVALID ; goto out; } -cpu_physical_memory_read (addr, iplb,be32_to_cpu (iplb->len)); +if (!s390_is_pv ()) { +cpu_physical_memory_read (addr, iplb,be32_to_cpu (iplb->len)); + }else { +s390_cpu_pv_mem_read (cpu,0 , iplb,be32_to_cpu (iplb->len)); + } valid = subcode ==DIAG308_PV_SET ?iplb_valid_pv (iplb) :iplb_valid (iplb);if (!valid) {
@@ -140,12 +150,17 @@ out: }else { iplb =s390_ipl_get_iplb (); } -if (iplb) { -cpu_physical_memory_write (addr, iplb,be32_to_cpu (iplb->len)); - env->regs[r1 +1 ] =DIAG_308_RC_OK ; - }else { +if (!iplb) { env->regs[r1 +1 ] =DIAG_308_RC_NO_CONF ; +return ; } + +if (!s390_is_pv ()) { +cpu_physical_memory_write (addr, iplb,be32_to_cpu (iplb->len)); + }else { +s390_cpu_pv_mem_write (cpu,0 , iplb,be32_to_cpu (iplb->len)); + } + env->regs[r1 +1 ] =DIAG_308_RC_OK ;return ;case DIAG308_PV_START : iplb =s390_ipl_get_iplb_pv ();
Signature · 1 line
2.25.1
Re: [PATCH v10 11/16] s390x: protvirt: Move diag 308 data over SIDA
Quoted 10 lines · On Wed, 18 Mar 2020 10:30:42 -0400 Janosch Frank <[email protected]> wrote:
For protected guests the IPIB is written/read to/from the SIDA, so we need those accesses to go through s390_cpu_pv_mem_read/write().
Signed-off-by Janosch Frank <[email protected]>Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Christian Borntraeger <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- target/s390x/diag.c | 27 +++++++++++++++++++++------ 1 file changed, 21 insertions(+), 6 deletions(-)
PATCH v10 12/16 s390x: protvirt: Disable address checks for PV guest IO emulation
In reply to Janosch FrankIO instruction data is routed through SIDAD for protected guests, so adresses do not need to be checked, as this is kernel memory which is always available.
Also the instruction data always starts at offset 0 of the SIDAD.
--- target/s390x/ioinst.c | 35 ++++++++++++++++++++++++++++------- 1 file changed, 28 insertions(+), 7 deletions(-)
target/s390x/ioinst.c +28 -7
@@ -16,6 +16,25 @@#include "hw/s390x/ioinst.h" #include "trace.h" #include "hw/s390x/s390-pci-bus.h" +#include "hw/s390x/pv.h" + +/* All I/O instructions but chsc use the s format */ +static uint64_t get_address_from_regs (CPUS390XState *env,uint32_t ipb, +uint8_t *ar) +{ +/* +* Addresses for protected guests are all offsets into the +* satellite block which holds the IO control structures. Those +* control structures are always starting at offset 0 and are +* always aligned and accessible. So we can return 0 here which +* will pass the following address checks. +*/ +if (s390_is_pv ()) { + *ar =0 ; +return 0 ; + } +return decode_basedisp_s (env, ipb, ar); +}int ioinst_disassemble_sch_ident (uint32_t value,int *m,int *cssid,int *ssid,int *schid)
@@ -114,7 +133,7 @@ void ioinst_handle_msch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, uintptr_t ra)CPUS390XState *env = &cpu->env;uint8_t ar; - addr =decode_basedisp_s (env, ipb, &ar); + addr =get_address_from_regs (env, ipb, &ar);if (addr &3 ) {s390_program_interrupt (env,PGM_SPECIFICATION , ra);return ;
@@ -171,7 +190,7 @@ void ioinst_handle_ssch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, uintptr_t ra)CPUS390XState *env = &cpu->env;uint8_t ar; - addr =decode_basedisp_s (env, ipb, &ar); + addr =get_address_from_regs (env, ipb, &ar);if (addr &3 ) {s390_program_interrupt (env,PGM_SPECIFICATION , ra);return ;
@@ -203,7 +222,7 @@ void ioinst_handle_stcrw(S390CPU *cpu, uint32_t ipb, uintptr_t ra)CPUS390XState *env = &cpu->env;uint8_t ar; - addr =decode_basedisp_s (env, ipb, &ar); + addr =get_address_from_regs (env, ipb, &ar);if (addr &3 ) {s390_program_interrupt (env,PGM_SPECIFICATION , ra);return ;
@@ -234,7 +253,7 @@ void ioinst_handle_stsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb,CPUS390XState *env = &cpu->env;uint8_t ar; - addr =decode_basedisp_s (env, ipb, &ar); + addr =get_address_from_regs (env, ipb, &ar);if (addr &3 ) {s390_program_interrupt (env,PGM_SPECIFICATION , ra);return ;
@@ -303,7 +322,7 @@ int ioinst_handle_tsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, uintptr_t ra)return -EIO ; }trace_ioinst_sch_id ("tsch" , cssid, ssid, schid); - addr =decode_basedisp_s (env, ipb, &ar); + addr =get_address_from_regs (env, ipb, &ar);if (addr &3 ) {s390_program_interrupt (env,PGM_SPECIFICATION , ra);return -EIO ;
@@ -601,7 +620,7 @@ void ioinst_handle_chsc(S390CPU *cpu, uint32_t ipb, uintptr_t ra) {ChscReq *req;ChscResp *res; -uint64_t addr; +uint64_t addr =0 ;int reg;uint16_t len;uint16_t command;
@@ -610,7 +629,9 @@ void ioinst_handle_chsc(S390CPU *cpu, uint32_t ipb, uintptr_t ra)trace_ioinst ("chsc" ); reg = (ipb >>20 ) &0x00f ; - addr = env->regs[reg]; +if (!s390_is_pv ()) { + addr = env->regs[reg]; + }/* Page boundary? */ if (addr &0xfff ) {s390_program_interrupt (env,PGM_SPECIFICATION , ra);
Signature · 1 line
2.25.1
PATCH v10 13/16 s390x: protvirt: Move IO control structures over SIDA
In reply to Janosch FrankFor protected guests, we need to put the IO emulation results into the SIDA, so SIE will write them into the guest at the next entry.
--- target/s390x/ioinst.c | 61 +++++++++++++++++++++++++++++++------------ 1 file changed, 45 insertions(+), 16 deletions(-)
target/s390x/ioinst.c +45 -16
@@ -138,7 +138,9 @@ void ioinst_handle_msch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, uintptr_t ra)s390_program_interrupt (env,PGM_SPECIFICATION , ra);return ; } -if (s390_cpu_virt_mem_read (cpu, addr, ar, &schib,sizeof (schib))) { +if (s390_is_pv ()) { +s390_cpu_pv_mem_read (cpu, addr, &schib,sizeof (schib)); + }else if (s390_cpu_virt_mem_read (cpu, addr, ar, &schib,sizeof (schib))) {s390_cpu_virt_mem_handle_exc (cpu, ra);return ; }
@@ -195,7 +197,9 @@ void ioinst_handle_ssch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, uintptr_t ra)s390_program_interrupt (env,PGM_SPECIFICATION , ra);return ; } -if (s390_cpu_virt_mem_read (cpu, addr, ar, &orig_orb,sizeof (orb))) { +if (s390_is_pv ()) { +s390_cpu_pv_mem_read (cpu, addr, &orig_orb,sizeof (orb)); + }else if (s390_cpu_virt_mem_read (cpu, addr, ar, &orig_orb,sizeof (orb))) {s390_cpu_virt_mem_handle_exc (cpu, ra);return ; }
@@ -231,14 +235,19 @@ void ioinst_handle_stcrw(S390CPU *cpu, uint32_t ipb, uintptr_t ra) cc =css_do_stcrw (&crw);/* 0 - crw stored, 1 - zeroes stored */ -if (s390_cpu_virt_mem_write (cpu, addr, ar, &crw,sizeof (crw)) ==0 ) { +if (s390_is_pv ()) { +s390_cpu_pv_mem_write (cpu, addr, &crw,sizeof (crw));setcc (cpu, cc); }else { -if (cc ==0 ) { -/* Write failed: requeue CRW since STCRW is suppressing */ -css_undo_stcrw (&crw); +if (s390_cpu_virt_mem_write (cpu, addr, ar, &crw,sizeof (crw)) ==0 ) { +setcc (cpu, cc); + }else { +if (cc ==0 ) { +/* Write failed: requeue CRW since STCRW is suppressing */ +css_undo_stcrw (&crw); + } +s390_cpu_virt_mem_handle_exc (cpu, ra); } -s390_cpu_virt_mem_handle_exc (cpu, ra); } }
@@ -260,6 +269,13 @@ void ioinst_handle_stsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, }if (ioinst_disassemble_sch_ident (reg1, &m, &cssid, &ssid, &schid)) { +/* +* The Ultravisor checks schid bit 16 to be one and bits 0-12 +* to be 0 and injects a operand exception itself. +* +* Hence we should never end up here. +*/ +g_assert (!s390_is_pv ());/* * As operand exceptions have a lower priority than access exceptions, * we check whether the memory area is writeable (injecting the
@@ -292,14 +308,17 @@ void ioinst_handle_stsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, } }if (cc !=3 ) { -if (s390_cpu_virt_mem_write (cpu, addr, ar, &schib, -sizeof (schib)) !=0 ) { +if (s390_is_pv ()) { +s390_cpu_pv_mem_write (cpu, addr, &schib,sizeof (schib)); + }else if (s390_cpu_virt_mem_write (cpu, addr, ar, &schib, +sizeof (schib)) !=0 ) {s390_cpu_virt_mem_handle_exc (cpu, ra);return ; } }else {/* Access exceptions have a higher priority than cc3 */ -if (s390_cpu_virt_mem_check_write (cpu, addr, ar,sizeof (schib)) !=0 ) { +if (!s390_is_pv () && +s390_cpu_virt_mem_check_write (cpu, addr, ar,sizeof (schib)) !=0 ) {s390_cpu_virt_mem_handle_exc (cpu, ra);return ; }
@@ -336,7 +355,9 @@ int ioinst_handle_tsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, uintptr_t ra) }/* 0 - status pending, 1 - not status pending, 3 - not operational */ if (cc !=3 ) { -if (s390_cpu_virt_mem_write (cpu, addr, ar, &irb, irb_len) !=0 ) { +if (s390_is_pv ()) { +s390_cpu_pv_mem_write (cpu, addr, &irb, irb_len); + }else if (s390_cpu_virt_mem_write (cpu, addr, ar, &irb, irb_len) !=0 ) {s390_cpu_virt_mem_handle_exc (cpu, ra);return -EFAULT ; }
@@ -344,7 +365,8 @@ int ioinst_handle_tsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, uintptr_t ra) }else { irb_len =sizeof (irb) -sizeof (irb.emw);/* Access exceptions have a higher priority than cc3 */ -if (s390_cpu_virt_mem_check_write (cpu, addr, ar, irb_len) !=0 ) { +if (!s390_is_pv () && +s390_cpu_virt_mem_check_write (cpu, addr, ar, irb_len) !=0 ) {s390_cpu_virt_mem_handle_exc (cpu, ra);return -EFAULT ; }
@@ -642,7 +664,9 @@ void ioinst_handle_chsc(S390CPU *cpu, uint32_t ipb, uintptr_t ra)* present CHSC sub-handlers ... if we ever need more, we should take * care of req->len here first. */ -if (s390_cpu_virt_mem_read (cpu, addr, reg, buf,sizeof (ChscReq))) { +if (s390_is_pv ()) { +s390_cpu_pv_mem_read (cpu, addr, buf,sizeof (ChscReq)); + }else if (s390_cpu_virt_mem_read (cpu, addr, reg, buf,sizeof (ChscReq))) {s390_cpu_virt_mem_handle_exc (cpu, ra);return ; }
@@ -675,11 +699,16 @@ void ioinst_handle_chsc(S390CPU *cpu, uint32_t ipb, uintptr_t ra)break ; } -if (!s390_cpu_virt_mem_write (cpu, addr + len, reg, res, -be16_to_cpu (res->len))) { +if (s390_is_pv ()) { +s390_cpu_pv_mem_write (cpu, addr + len, res,be16_to_cpu (res->len));setcc (cpu,0 );/* Command execution complete */ }else { -s390_cpu_virt_mem_handle_exc (cpu, ra); +if (!s390_cpu_virt_mem_write (cpu, addr + len, reg, res, +be16_to_cpu (res->len))) { +setcc (cpu,0 );/* Command execution complete */ + }else { +s390_cpu_virt_mem_handle_exc (cpu, ra); + } } }
Signature · 1 line
2.25.1
Re: [PATCH v10 13/16] s390x: protvirt: Move IO control structures over SIDA
Quoted 11 lines · On Wed, 18 Mar 2020 10:30:44 -0400 Janosch Frank <[email protected]> wrote:
For protected guests, we need to put the IO emulation results into the SIDA, so SIE will write them into the guest at the next entry.
Signed-off-by Janosch Frank <[email protected]>Reviewed-by David Hildenbrand <[email protected]>--- target/s390x/ioinst.c | 61 +++++++++++++++++++++++++++++++------------ 1 file changed, 45 insertions(+), 16 deletions(-)
target/s390x/ioinst.c void ioinst_handle_stsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, · line 274
Quoted 6 lines
target/s390x/ioinst.c +3
-0@@ -260,6 +269,13 @@ void ioinst_handle_stsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, }if (ioinst_disassemble_sch_ident (reg1, &m, &cssid, &ssid, &schid)) { +/* +* The Ultravisor checks schid bit 16 to be one and bits 0-12 +* to be 0 and injects a operand exception itself.
As a side remark, that also implies that the ultravisor doesn't support MCSS-E, which is highly unsurprising :)
Do we want to fence off enabling MCSS-E in the sda chsc for pv guests? Probably not really needed, as Linux does not support it anyway.
target/s390x/ioinst.c void ioinst_handle_stsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, · line 281
Quoted 7 lines
target/s390x/ioinst.c +4
-0+* +* Hence we should never end up here. +*/ +g_assert (!s390_is_pv ());/* * As operand exceptions have a lower priority than access exceptions, * we check whether the memory area is writeable (injecting the
Re: [PATCH v10 13/16] s390x: protvirt: Move IO control structures over SIDA
Quoted 16 lines · Cornelia Huck
Quoted 13 lines · On Wed, 18 Mar 2020 10:30:44 -0400 Janosch Frank <[email protected]> wrote:
For protected guests, we need to put the IO emulation results into the SIDA, so SIE will write them into the guest at the next entry.
Signed-off-by Janosch Frank <[email protected]>Reviewed-by David Hildenbrand <[email protected]>--- target/s390x/ioinst.c | 61 +++++++++++++++++++++++++++++++------------ 1 file changed, 45 insertions(+), 16 deletions(-)(quoted diff) +0
-0@@ -260,6 +269,13 @@ void ioinst_handle_stsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, }
Quoted 7 lines
target/s390x/ioinst.c void ioinst_handle_stsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, · line 274
Quoted 4 lines
target/s390x/ioinst.c +3
-0if (ioinst_disassemble_sch_ident (reg1, &m, &cssid, &ssid, &schid)) { +/* +* The Ultravisor checks schid bit 16 to be one and bits 0-12 +* to be 0 and injects a operand exception itself. As a side remark, that also implies that the ultravisor doesn't support MCSS-E, which is highly unsurprising :)
Yup
Quoted 3 lines
Do we want to fence off enabling MCSS-E in the sda chsc for pv guests? Probably not really needed, as Linux does not support it anyway.
If possible I'd leave that to Halil or you.
IO is currently not my stronghold.
Quoted 11 lines
target/s390x/ioinst.c void ioinst_handle_stsch(S390CPU *cpu, uint64_t reg1, uint32_t ipb, · line 281
Quoted 8 lines
target/s390x/ioinst.c +4
-0+* +* Hence we should never end up here. +*/ +g_assert (!s390_is_pv ());/* * As operand exceptions have a lower priority than access exceptions, * we check whether the memory area is writeable (injecting the Reviewed-by Cornelia Huck <[email protected]>
Thanks!
PATCH v10 14/16 s390x: protvirt: Handle SIGP store status correctly
In reply to Janosch FrankFor protected VMs status storing is not done by QEMU anymore.
--- target/s390x/helper.c | 6 ++++++ 1 file changed, 6 insertions(+)
target/s390x/helper.c +6 -0
@@ -25,6 +25,7 @@#include "qemu/timer.h" #include "qemu/qemu-print.h" #include "hw/s390x/ioinst.h" +#include "hw/s390x/pv.h" #include "sysemu/hw_accel.h" #include "sysemu/runstate.h" #ifndef CONFIG_USER_ONLY
@@ -246,6 +247,11 @@ int s390_store_status(S390CPU *cpu, hwaddr addr, bool store_arch)hwaddr len =sizeof (*sa);int i; +/* For PVMs storing will occur when this cpu enters SIE again */ +if (s390_is_pv ()) { +return 0 ; + } + sa =cpu_physical_memory_map (addr, &len, true);if (!sa) {return -EFAULT ;
Signature · 1 line
2.25.1
PATCH v10 15/16 docs: system: Add protvirt docs
In reply to Janosch FrankLet's add some documentation for the Protected VM functionality.
--- docs/system/s390x/protvirt.rst | 59 ++++++++++++++++++++++++++++++++++ docs/system/target-s390x.rst | 5 +++ 2 files changed, 64 insertions(+) create mode 100644 docs/system/s390x/protvirt.rst
docs/system/s390x/protvirt.rst new file +59 -0
@@ -0,0 +1,59 @@ +Protected Virtualization on s390x +================================= + +The memory and most of the registers of Protected Virtual Machines +(PVMs) are encrypted or inaccessible to the hypervisor, effectively +prohibiting VM introspection when the VM is running. At rest, PVMs are +encrypted and can only be decrypted by the firmware, represented by an +entity called Ultravisor, of specific IBM Z machines. + + +Prerequisites +------------- + +To run PVMs, a machine with the Protected Virtualization feature, as +indicated by the Ultravisor Call facility (stfle bit 158), is +required. The Ultravisor needs to be initialized at boot by setting +`prot_virt=1` on the host's kernel command line. + +Running PVMs requires using the KVM hypervisor. + +If those requirements are met, the capability `KVM_CAP_S390_PROTECTED` +will indicate that KVM can support PVMs on that LPAR. + + +QEMU Settings +------------- + +To indicate to the VM that it can transition into protected mode, the +`Unpack facility` (stfle bit 161 represented by the feature +`unpack`/`S390_FEAT_UNPACK`) needs to be part of the cpu model of +the VM. + +All I/O devices need to use the IOMMU. +Passthrough (vfio) devices are currently not supported. + +Host huge page backings are not supported. However guests can use huge +pages as indicated by its facilities. + + +Boot Process +------------ + +A secure guest image can either be loaded from disk or supplied on the +QEMU command line. Booting from disk is done by the unmodified +s390-ccw BIOS. I.e., the bootmap is interpreted, multiple components +are read into memory and control is transferred to one of the +components (zipl stage3). Stage3 does some fixups and then transfers +control to some program residing in guest memory, which is normally +the OS kernel. The secure image has another component prepended +(stage3a) that uses the new diag308 subcodes 8 and 10 to trigger the +transition into secure mode. + +Booting from the image supplied on the QEMU command line requires that +the file passed via -kernel has the same memory layout as would result +from the disk boot. This memory layout includes the encrypted +components (kernel, initrd, cmdline), the stage3a loader and +metadata. In case this boot method is used, the command line +options -initrd and -cmdline are ineffective. The preparation of a PVM +image is done via the `genprotimg` tool from the s390-tools package.
docs/system/target-s390x.rst +5 -0
@@ -24,3 +24,8 @@ or vfio-ap is also available. .. toctree:: s390x/vfio-ap +Architectural features +~~~~~~~~ + +.. toctree:: + s390x/protvirt
Signature · 1 line
2.25.1
Re: [PATCH v10 15/16] docs: system: Add protvirt docs
Quoted 10 lines · On Wed, 18 Mar 2020 10:30:46 -0400 Janosch Frank <[email protected]> wrote:
Let's add some documentation for the Protected VM functionality.
Signed-off-by Janosch Frank <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- docs/system/s390x/protvirt.rst | 59 ++++++++++++++++++++++++++++++++++ docs/system/target-s390x.rst | 5 +++ 2 files changed, 64 insertions(+) create mode 100644 docs/system/s390x/protvirt.rst
(...)
docs/system/s390x/protvirt.rst line 59
Quoted 7 lines
docs/system/s390x/protvirt.rst new file +7
-0+Booting from the image supplied on the QEMU command line requires that +the file passed via -kernel has the same memory layout as would result +from the disk boot. This memory layout includes the encrypted +components (kernel, initrd, cmdline), the stage3a loader and +metadata. In case this boot method is used, the command line +options -initrd and -cmdline are ineffective. The preparation of a PVM +image is done via the `genprotimg` tool from the s390-tools package.
I still think 'package' is not a good name (yes, I realize that s390-tools' README uses that term as well :) I'd prefer 'collection' or something like that, so it doesn't get confused with distro packages, which may use a different name. But no strong opinion.
docs/system/target-s390x.rst or vfio-ap is also available. · line 28
Quoted 10 lines
docs/system/target-s390x.rst +2
-0@@ -24,3 +24,8 @@ or vfio-ap is also available. .. toctree:: s390x/vfio-ap +Architectural features +~~~~~~~~
Architecture features
=====================
?
docs/system/target-s390x.rst or vfio-ap is also available. · line 31
Quoted 3 lines
docs/system/target-s390x.rst +3
-0+ +.. toctree:: + s390x/protvirt
Otherwise, looks good to me.
Re: [PATCH v10 15/16] docs: system: Add protvirt docs
Quoted 16 lines · Cornelia Huck
Quoted 10 lines · On Wed, 18 Mar 2020 10:30:46 -0400 Janosch Frank <[email protected]> wrote:
Let's add some documentation for the Protected VM functionality.
Signed-off-by Janosch Frank <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- docs/system/s390x/protvirt.rst | 59 ++++++++++++++++++++++++++++++++++ docs/system/target-s390x.rst | 5 +++ 2 files changed, 64 insertions(+) create mode 100644 docs/system/s390x/protvirt.rst(...)
Quoted 12 lines
docs/system/s390x/protvirt.rst line 59
Quoted 7 lines
docs/system/s390x/protvirt.rst new file +7
-0+Booting from the image supplied on the QEMU command line requires that +the file passed via -kernel has the same memory layout as would result +from the disk boot. This memory layout includes the encrypted +components (kernel, initrd, cmdline), the stage3a loader and +metadata. In case this boot method is used, the command line +options -initrd and -cmdline are ineffective. The preparation of a PVM +image is done via the `genprotimg` tool from the s390-tools package.I still think 'package' is not a good name (yes, I realize that s390-tools' README uses that term as well :) I'd prefer 'collection' or something like that, so it doesn't get confused with distro packages, which may use a different name. But no strong opinion.
collection it is
Quoted 9 lines
Quoted 9 lines
docs/system/target-s390x.rst +0
-0@@ -24,3 +24,8 @@ or vfio-ap is also available. .. toctree:: s390x/vfio-ap
Quoted 7 lines
docs/system/target-s390x.rst or vfio-ap is also available. · line 28
Quoted 2 lines
docs/system/target-s390x.rst +2
-0+Architectural features +~~~~~~~~Architecture features
=====================?
Ack
Quoted 8 lines
docs/system/target-s390x.rst or vfio-ap is also available. · line 31
Quoted 4 lines
docs/system/target-s390x.rst +3
-0+ +.. toctree:: + s390x/protvirtOtherwise, looks good to me.
Cornelia Huck
Reviewed-byRe: [PATCH v10 15/16] docs: system: Add protvirt docs
Quoted 47 lines · On Thu, 19 Mar 2020 10:04:38 +0100 Janosch Frank <[email protected]> wrote:
Quoted 16 lines · Cornelia Huck
Quoted 10 lines · On Wed, 18 Mar 2020 10:30:46 -0400 Janosch Frank <[email protected]> wrote:
Let's add some documentation for the Protected VM functionality.
Signed-off-by Janosch Frank <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>--- docs/system/s390x/protvirt.rst | 59 ++++++++++++++++++++++++++++++++++ docs/system/target-s390x.rst | 5 +++ 2 files changed, 64 insertions(+) create mode 100644 docs/system/s390x/protvirt.rst(...)
Quoted 12 lines
docs/system/s390x/protvirt.rst line 59
Quoted 7 lines
docs/system/s390x/protvirt.rst new file +7
-0+Booting from the image supplied on the QEMU command line requires that +the file passed via -kernel has the same memory layout as would result +from the disk boot. This memory layout includes the encrypted +components (kernel, initrd, cmdline), the stage3a loader and +metadata. In case this boot method is used, the command line +options -initrd and -cmdline are ineffective. The preparation of a PVM +image is done via the `genprotimg` tool from the s390-tools package.I still think 'package' is not a good name (yes, I realize that s390-tools' README uses that term as well :) I'd prefer 'collection' or something like that, so it doesn't get confused with distro packages, which may use a different name. But no strong opinion.
collection it is
Quoted 15 lines
docs/system/target-s390x.rst or vfio-ap is also available. · line 28
Quoted 11 lines
docs/system/target-s390x.rst +2
-0@@ -24,3 +24,8 @@ or vfio-ap is also available. .. toctree:: s390x/vfio-ap +Architectural features +~~~~~~~~Architecture features
=====================
Quoted 14 lines
Quoted 1 line
?
Ack
Quoted 8 lines
docs/system/target-s390x.rst or vfio-ap is also available. · line 31
Quoted 4 lines
docs/system/target-s390x.rst +3
-0+ +.. toctree:: + s390x/protvirtOtherwise, looks good to me.
With those changes,
Re: [PATCH v10 15/16] docs: system: Add protvirt docs
In reply to Janosch FrankQuoted 5 lines · Janosch Frank
Let's add some documentation for the Protected VM functionality.
Signed-off-by Janosch Frank <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>
Quoted 85 lines
--- docs/system/s390x/protvirt.rst | 59 ++++++++++++++++++++++++++++++++++ docs/system/target-s390x.rst | 5 +++ 2 files changed, 64 insertions(+) create mode 100644 docs/system/s390x/protvirt.rstdocs/system/s390x/protvirt.rst new file +59
-0@@ -0,0 +1,59 @@ +Protected Virtualization on s390x +================================= + +The memory and most of the registers of Protected Virtual Machines +(PVMs) are encrypted or inaccessible to the hypervisor, effectively +prohibiting VM introspection when the VM is running. At rest, PVMs are +encrypted and can only be decrypted by the firmware, represented by an +entity called Ultravisor, of specific IBM Z machines. + + +Prerequisites +------------- + +To run PVMs, a machine with the Protected Virtualization feature, as +indicated by the Ultravisor Call facility (stfle bit 158), is +required. The Ultravisor needs to be initialized at boot by setting +`prot_virt=1` on the host's kernel command line. + +Running PVMs requires using the KVM hypervisor. + +If those requirements are met, the capability `KVM_CAP_S390_PROTECTED` +will indicate that KVM can support PVMs on that LPAR. + + +QEMU Settings +------------- + +To indicate to the VM that it can transition into protected mode, the +`Unpack facility` (stfle bit 161 represented by the feature +`unpack`/`S390_FEAT_UNPACK`) needs to be part of the cpu model of +the VM. + +All I/O devices need to use the IOMMU. +Passthrough (vfio) devices are currently not supported. + +Host huge page backings are not supported. However guests can use huge +pages as indicated by its facilities. + + +Boot Process +------------ + +A secure guest image can either be loaded from disk or supplied on the +QEMU command line. Booting from disk is done by the unmodified +s390-ccw BIOS. I.e., the bootmap is interpreted, multiple components +are read into memory and control is transferred to one of the +components (zipl stage3). Stage3 does some fixups and then transfers +control to some program residing in guest memory, which is normally +the OS kernel. The secure image has another component prepended +(stage3a) that uses the new diag308 subcodes 8 and 10 to trigger the +transition into secure mode. + +Booting from the image supplied on the QEMU command line requires that +the file passed via -kernel has the same memory layout as would result +from the disk boot. This memory layout includes the encrypted +components (kernel, initrd, cmdline), the stage3a loader and +metadata. In case this boot method is used, the command line +options -initrd and -cmdline are ineffective. The preparation of a PVM +image is done via the `genprotimg` tool from the s390-tools package.docs/system/target-s390x.rst +5
-0@@ -24,3 +24,8 @@ or vfio-ap is also available. .. toctree:: s390x/vfio-ap +Architectural features +~~~~~~~~ + +.. toctree:: + s390x/protvirt
PATCH v10 16/16 s390x: Add unpack facility feature to GA1
In reply to Janosch FrankFrom: Christian Borntraeger <[email protected]>
The unpack facility is an indication that diagnose 308 subcodes 8-10 are available to the guest. That means, that the guest can put itself into protected mode.
Once it is in protected mode, the hardware stops any attempt of VM introspection by the hypervisor.
Some features are currently not supported in protected mode:
* vfio devices
* Migration
* Huge page backings
--- target/s390x/gen-features.c | 1 + target/s390x/kvm.c | 8 ++++++++ 2 files changed, 9 insertions(+)
target/s390x/gen-features.c +1 -0
@@ -562,6 +562,7 @@ static uint16_t full_GEN15_GA1[] = {S390_FEAT_GROUP_MSA_EXT_9 ,S390_FEAT_GROUP_MSA_EXT_9_PCKMO ,S390_FEAT_ETOKEN , + S390_FEAT_UNPACK, };/* Default features (in order of release)
target/s390x/kvm.c +8 -0
@@ -2410,6 +2410,14 @@ void kvm_s390_get_host_cpu_model(S390CPUModel *model, Error **errp)clear_bit (S390_FEAT_BPB , model->features); } +/* +* If we have support for protected virtualization, indicate +* the protected virtualization IPL unpack facility. +*/ +if (cap_protected) { +set_bit (S390_FEAT_UNPACK , model->features); + } +/* We emulate a zPCI bus and AEN, therefore we don't need HW support */ set_bit (S390_FEAT_ZPCI , model->features);set_bit (S390_FEAT_ADAPTER_EVENT_NOTIFICATION , model->features);
Signature · 1 line
2.25.1
Re: [PATCH v10 16/16] s390x: Add unpack facility feature to GA1
Quoted 14 lines · On Wed, 18 Mar 2020 10:30:47 -0400 Janosch Frank <[email protected]> wrote:
From: Christian Borntraeger <[email protected]>
The unpack facility is an indication that diagnose 308 subcodes 8-10 are available to the guest. That means, that the guest can put itself into protected mode.
Once it is in protected mode, the hardware stops any attempt of VM introspection by the hypervisor.
Some features are currently not supported in protected mode:
* vfio devices
* Migration
* Huge page backings
Quoted 8 lines
Signed-off-by Christian Borntraeger <[email protected]>Reviewed-by David Hildenbrand <[email protected]>Reviewed-by Claudio Imbrenda <[email protected]>Signed-off-by Janosch Frank <[email protected]>--- target/s390x/gen-features.c | 1 + target/s390x/kvm.c | 8 ++++++++ 2 files changed, 9 insertions(+)