s390x: Increase architectural compliance
v2 cover s390x: Increase architectural compliance
On a cpu reset normal, we need to clear local cpus. Unfortunately we need a new API for that, since KVM only exposes one of the three resets.
Also we need to clear the riccb and the PSW ri mask on a normal reset.
Patches are also in my cleanup branch.
Janosch Frank (3):
Header sync
s390x: Add missing vcpu reset functions
s390x: Fix cpu normal reset ri clearing
linux-headers/linux/kvm.h | 4 ++++ target/s390x/cpu.c | 19 ++++++++++++++++-- target/s390x/cpu.h | 7 ++++++- target/s390x/kvm-stub.c | 10 +++++++++- target/s390x/kvm.c | 42 +++++++++++++++++++++++++++++++-------- target/s390x/kvm_s390x.h | 4 +++- 6 files changed, 73 insertions(+), 13 deletions(-)
Signature · 1 line
2.20.1
PATCH v2 1/3 Header sync
Sync in the new vcpu resets.
--- linux-headers/linux/kvm.h | 4 ++++ 1 file changed, 4 insertions(+)
linux-headers/linux/kvm.h +4 -0
@@ -1000,6 +1000,7 @@ struct kvm_ppc_resize_hpt {#define KVM_CAP_PMU_EVENT_FILTER 173#define KVM_CAP_ARM_IRQ_LINE_LAYOUT_2 174#define KVM_CAP_HYPERV_DIRECT_TLBFLUSH 175 +#define KVM_CAP_S390_VCPU_RESETS 176#ifdef KVM_CAP_IRQ_ROUTING
@@ -1461,6 +1462,9 @@ struct kvm_enc_region {/* Available with KVM_CAP_ARM_SVE */ #define KVM_ARM_VCPU_FINALIZE _IOW(KVMIO, 0xc2, int) +#define KVM_S390_NORMAL_RESET _IO(KVMIO, 0xc3) +#define KVM_S390_CLEAR_RESET _IO(KVMIO, 0xc4) +/* Secure Encrypted Virtualization command */ enum sev_cmd_id {/* Guest initialization commands */
Signature · 1 line
2.20.1
PATCH v2 2/3 s390x: Add missing vcpu reset functions
In reply to Janosch FrankUp to now we only had an ioctl to reset vcpu data QEMU couldn't reach for the initial reset, which was also called for the clear reset. To be architecture compliant, we also need to clear local interrupts on a normal reset.
Because of this and the upcoming protvirt support we need to add ioctls for the missing clear and normal resets.
--- target/s390x/cpu.c | 14 ++++++++++++-- target/s390x/kvm-stub.c | 10 +++++++++- target/s390x/kvm.c | 42 ++++++++++++++++++++++++++++++++-------- target/s390x/kvm_s390x.h | 4 +++- 4 files changed, 58 insertions(+), 12 deletions(-)
target/s390x/cpu.c +12 -2
@@ -139,8 +139,18 @@ static void s390_cpu_reset(CPUState *s, cpu_reset_type type) }/* Reset state inside the kernel that we cannot access yet from QEMU. */ -if (kvm_enabled () && type !=S390_CPU_RESET_NORMAL ) { -kvm_s390_reset_vcpu (cpu); +if (kvm_enabled ()) { +switch (type) { +case S390_CPU_RESET_CLEAR : +kvm_s390_reset_vcpu_clear (cpu); +break ; +case S390_CPU_RESET_INITIAL : +kvm_s390_reset_vcpu_initial (cpu); +break ; +case S390_CPU_RESET_NORMAL : +kvm_s390_reset_vcpu_normal (cpu); +break ; + } } }
target/s390x/kvm-stub.c +9 -1
@@ -83,7 +83,15 @@ void kvm_s390_cmma_reset(void) { } -void kvm_s390_reset_vcpu (S390CPU *cpu) +void kvm_s390_reset_vcpu_initial (S390CPU *cpu) +{ +} + +void kvm_s390_reset_vcpu_clear (S390CPU *cpu) +{ +} + +void kvm_s390_reset_vcpu_normal (S390CPU *cpu) { }
target/s390x/kvm.c +34 -8
66 lines not on this page · raw message
target/s390x/kvm_s390x.h +3 -1
@@ -34,7 +34,9 @@ int kvm_s390_assign_subch_ioeventfd(EventNotifier *notifier, uint32_t sch, int vq, bool assign);int kvm_s390_cmma_active (void );void kvm_s390_cmma_reset (void ); -void kvm_s390_reset_vcpu (S390CPU *cpu); +void kvm_s390_reset_vcpu_clear (S390CPU *cpu); +void kvm_s390_reset_vcpu_normal (S390CPU *cpu); +void kvm_s390_reset_vcpu_initial (S390CPU *cpu);int kvm_s390_set_mem_limit (uint64_t new_limit,uint64_t *hw_limit);void kvm_s390_set_max_pagesize (uint64_t pagesize,Error **errp);void kvm_s390_crypto_reset (void );
Signature · 1 line
2.20.1
Re: [PATCH v2 2/3] s390x: Add missing vcpu reset functions
Quoted 120 lines · Janosch Frank
Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach for the initial reset, which was also called for the clear reset. To be architecture compliant, we also need to clear local interrupts on a normal reset.
Because of this and the upcoming protvirt support we need to add ioctls for the missing clear and normal resets.
Signed-off-by Janosch Frank <[email protected]>--- target/s390x/cpu.c | 14 ++++++++++++-- target/s390x/kvm-stub.c | 10 +++++++++- target/s390x/kvm.c | 42 ++++++++++++++++++++++++++++++++-------- target/s390x/kvm_s390x.h | 4 +++- 4 files changed, 58 insertions(+), 12 deletions(-)target/s390x/cpu.c +12
-2@@ -139,8 +139,18 @@ static void s390_cpu_reset(CPUState *s, cpu_reset_type type) }/* Reset state inside the kernel that we cannot access yet from QEMU. */ -if (kvm_enabled () && type !=S390_CPU_RESET_NORMAL ) { -kvm_s390_reset_vcpu (cpu); +if (kvm_enabled ()) { +switch (type) { +case S390_CPU_RESET_CLEAR : +kvm_s390_reset_vcpu_clear (cpu); +break ; +case S390_CPU_RESET_INITIAL : +kvm_s390_reset_vcpu_initial (cpu); +break ; +case S390_CPU_RESET_NORMAL : +kvm_s390_reset_vcpu_normal (cpu); +break ; + } } }target/s390x/kvm-stub.c +9
-1@@ -83,7 +83,15 @@ void kvm_s390_cmma_reset(void) { } -void kvm_s390_reset_vcpu (S390CPU *cpu) +void kvm_s390_reset_vcpu_initial (S390CPU *cpu) +{ +} + +void kvm_s390_reset_vcpu_clear (S390CPU *cpu) +{ +} + +void kvm_s390_reset_vcpu_normal (S390CPU *cpu) { }target/s390x/kvm.c +22
-8@@ -151,6 +151,7 @@ static int cap_s390_irq;static int cap_ri;static int cap_gs;static int cap_hpage_1m; +static int cap_vcpu_resets;static int active_cmma;@@ -342,6 +343,7 @@ int kvm_arch_init(MachineState *ms, KVMState *s) cap_async_pf =kvm_check_extension (s,KVM_CAP_ASYNC_PF ); 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 );if (!kvm_check_extension (s,KVM_CAP_S390_GMAP ) || !kvm_check_extension (s,KVM_CAP_S390_COW )) {@@ -403,20 +405,44 @@ int kvm_arch_destroy_vcpu(CPUState *cs)return 0 ; } -void kvm_s390_reset_vcpu (S390CPU *cpu) +static void kvm_s390_reset_vcpu (S390CPU *cpu,unsigned long type) {CPUState *cs =CPU (cpu); -/* The initial reset call is needed here to reset in-kernel -* vcpu data that we can't access directly from QEMU -* (i.e. with older kernels which don't support sync_regs/ONE_REG). -* Before this ioctl cpu_synchronize_state() is called in common kvm -* code (kvm-all) */ -if (kvm_vcpu_ioctl (cs,KVM_S390_INITIAL_RESET ,NULL )) { -error_report ("Initial CPU reset failed on CPU %i" , cs->cpu_index); +/* +* The reset call is needed here to reset in-kernel vcpu data that +* we can't access directly from QEMU (i.e. with older kernels +* which don't support sync_regs/ONE_REG). Before this ioctl +* cpu_synchronize_state() is called in common kvm code +* (kvm-all). +*/ +if (kvm_vcpu_ioctl (cs, type)) { +error_report ("CPU reset failed on CPU %i" , cs->cpu_index); } } +void kvm_s390_reset_vcpu_initial (S390CPU *cpu) +{ +kvm_s390_reset_vcpu (cpu,KVM_S390_INITIAL_RESET ); +} + +void kvm_s390_reset_vcpu_clear (S390CPU *cpu) +{ +if (!cap_vcpu_resets) { +kvm_s390_reset_vcpu (cpu,KVM_S390_INITIAL_RESET ); + }else {
target/s390x/kvm.c int kvm_arch_destroy_vcpu(CPUState *cs) · line 443
Quoted 10 lines
target/s390x/kvm.c +10
-0+kvm_s390_reset_vcpu (cpu,KVM_S390_CLEAR_RESET ); + } +} + +void kvm_s390_reset_vcpu_normal (S390CPU *cpu) +{ +if (!cap_vcpu_resets) { +return ; + } +kvm_s390_reset_vcpu (cpu,KVM_S390_NORMAL_RESET );
if (cap_vcpu_resets) {
kvm_s390_reset_vcpu(cpu, KVM_S390_NORMAL_RESET);
}saves one LOC ;)
Signature · 3 lines
Thanks, David / dhildenb
Re: [PATCH v2 2/3] s390x: Add missing vcpu reset functions
In reply to Janosch FrankQuoted 10 lines · Janosch Frank
Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach for the initial reset, which was also called for the clear reset. To be architecture compliant, we also need to clear local interrupts on a normal reset.
Because of this and the upcoming protvirt support we need to add ioctls for the missing clear and normal resets.
Signed-off-by Janosch Frank <[email protected]>---
[...]
Quoted 15 lines
target/s390x/kvm.c +1
-7@@ -403,20 +405,44 @@ int kvm_arch_destroy_vcpu(CPUState *cs)return 0 ; } -void kvm_s390_reset_vcpu (S390CPU *cpu) +static void kvm_s390_reset_vcpu (S390CPU *cpu,unsigned long type) {CPUState *cs =CPU (cpu); -/* The initial reset call is needed here to reset in-kernel -* vcpu data that we can't access directly from QEMU -* (i.e. with older kernels which don't support sync_regs/ONE_REG). -* Before this ioctl cpu_synchronize_state() is called in common kvm -* code (kvm-all) */ -if (kvm_vcpu_ioctl (cs,KVM_S390_INITIAL_RESET ,NULL )) {
target/s390x/kvm.c int kvm_arch_destroy_vcpu(CPUState *cs) · line 420
Quoted 10 lines
target/s390x/kvm.c +9
-1-error_report ("Initial CPU reset failed on CPU %i" , cs->cpu_index); +/* +* The reset call is needed here to reset in-kernel vcpu data that +* we can't access directly from QEMU (i.e. with older kernels +* which don't support sync_regs/ONE_REG). Before this ioctl +* cpu_synchronize_state() is called in common kvm code +* (kvm-all). +*/ +if (kvm_vcpu_ioctl (cs, type)) { +error_report ("CPU reset failed on CPU %i" , cs->cpu_index);
In case you respin, maybe also print the "type" variable here?
Quoted 5 lines
target/s390x/kvm.c +2
-0} } +void kvm_s390_reset_vcpu_initial (S390CPU *cpu) +{
target/s390x/kvm.c int kvm_arch_destroy_vcpu(CPUState *cs) · line 435
Quoted 10 lines
target/s390x/kvm.c +10
-0+kvm_s390_reset_vcpu (cpu,KVM_S390_INITIAL_RESET ); +} + +void kvm_s390_reset_vcpu_clear (S390CPU *cpu) +{ +if (!cap_vcpu_resets) { +kvm_s390_reset_vcpu (cpu,KVM_S390_INITIAL_RESET ); + }else { +kvm_s390_reset_vcpu (cpu,KVM_S390_CLEAR_RESET ); + }
Cosmetic nit: It's a tiny bit nicer the other way round:
if (cap_vcpu_resets) {
kvm_s390_reset_vcpu(cpu, KVM_S390_CLEAR_RESET);
} else {
kvm_s390_reset_vcpu(cpu, KVM_S390_INITIAL_RESET);
}Anyway,
PATCH v3 1/1 s390x: Add missing vcpu reset functions
In reply to Janosch FrankUp to now we only had an ioctl to reset vcpu data QEMU couldn't reach for the initial reset, which was also called for the clear reset. To be architecture compliant, we also need to clear local interrupts on a normal reset.
Because of this and the upcoming protvirt support we need to add ioctls for the missing clear and normal resets.
--- target/s390x/cpu.c | 14 ++++++++++++-- target/s390x/kvm-stub.c | 10 +++++++++- target/s390x/kvm.c | 42 ++++++++++++++++++++++++++++++++-------- target/s390x/kvm_s390x.h | 4 +++- 4 files changed, 58 insertions(+), 12 deletions(-)
target/s390x/cpu.c +12 -2
@@ -139,8 +139,18 @@ static void s390_cpu_reset(CPUState *s, cpu_reset_type type) }/* Reset state inside the kernel that we cannot access yet from QEMU. */ -if (kvm_enabled () && type !=S390_CPU_RESET_NORMAL ) { -kvm_s390_reset_vcpu (cpu); +if (kvm_enabled ()) { +switch (type) { +case S390_CPU_RESET_CLEAR : +kvm_s390_reset_vcpu_clear (cpu); +break ; +case S390_CPU_RESET_INITIAL : +kvm_s390_reset_vcpu_initial (cpu); +break ; +case S390_CPU_RESET_NORMAL : +kvm_s390_reset_vcpu_normal (cpu); +break ; + } } }
target/s390x/kvm-stub.c +9 -1
@@ -83,7 +83,15 @@ void kvm_s390_cmma_reset(void) { } -void kvm_s390_reset_vcpu (S390CPU *cpu) +void kvm_s390_reset_vcpu_initial (S390CPU *cpu) +{ +} + +void kvm_s390_reset_vcpu_clear (S390CPU *cpu) +{ +} + +void kvm_s390_reset_vcpu_normal (S390CPU *cpu) { }
target/s390x/kvm.c +34 -8
63 lines not on this page · raw message
target/s390x/kvm_s390x.h +3 -1
@@ -34,7 +34,9 @@ int kvm_s390_assign_subch_ioeventfd(EventNotifier *notifier, uint32_t sch, int vq, bool assign);int kvm_s390_cmma_active (void );void kvm_s390_cmma_reset (void ); -void kvm_s390_reset_vcpu (S390CPU *cpu); +void kvm_s390_reset_vcpu_clear (S390CPU *cpu); +void kvm_s390_reset_vcpu_normal (S390CPU *cpu); +void kvm_s390_reset_vcpu_initial (S390CPU *cpu);int kvm_s390_set_mem_limit (uint64_t new_limit,uint64_t *hw_limit);void kvm_s390_set_max_pagesize (uint64_t pagesize,Error **errp);void kvm_s390_crypto_reset (void );
Signature · 1 line
2.20.1
Re: [PATCH v2 2/3] s390x: Add missing vcpu reset functions
In reply to Janosch FrankQuoted 2 lines · On Mon, 2 Dec 2019 09:01:45 -0500 Janosch Frank <[email protected]> wrote:
Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach for the initial reset, which was also called for the clear reset. To
s/which/and that/ ?
Quoted 19 lines
be architecture compliant, we also need to clear local interrupts on a normal reset.
Because of this and the upcoming protvirt support we need to add ioctls for the missing clear and normal resets.
Signed-off-by Janosch Frank <[email protected]>--- target/s390x/cpu.c | 14 ++++++++++++-- target/s390x/kvm-stub.c | 10 +++++++++- target/s390x/kvm.c | 42 ++++++++++++++++++++++++++++++++-------- target/s390x/kvm_s390x.h | 4 +++- 4 files changed, 58 insertions(+), 12 deletions(-)target/s390x/cpu.c +0
-0
target/s390x/cpu.c static void s390_cpu_reset(CPUState *s, cpu_reset_type type) · line 141
Quoted 3 lines
target/s390x/cpu.c +0
-0@@ -139,8 +139,18 @@ static void s390_cpu_reset(CPUState *s, cpu_reset_type type) }/* Reset state inside the kernel that we cannot access yet from QEMU. */
Hm, why does this comment talk about 'yet'? Did we have any plans to change that?
target/s390x/cpu.c static void s390_cpu_reset(CPUState *s, cpu_reset_type type) · line 152
Quoted 13 lines
target/s390x/cpu.c +11
-2-if (kvm_enabled () && type !=S390_CPU_RESET_NORMAL ) { -kvm_s390_reset_vcpu (cpu); +if (kvm_enabled ()) { +switch (type) { +case S390_CPU_RESET_CLEAR : +kvm_s390_reset_vcpu_clear (cpu); +break ; +case S390_CPU_RESET_INITIAL : +kvm_s390_reset_vcpu_initial (cpu); +break ; +case S390_CPU_RESET_NORMAL : +kvm_s390_reset_vcpu_normal (cpu); +break ;
Add a default case to catch errors?
Quoted 4 lines
target/s390x/cpu.c +1
-0+ } } }
(...)
Quoted 30 lines
target/s390x/kvm.c +3
-2@@ -151,6 +151,7 @@ static int cap_s390_irq;static int cap_ri;static int cap_gs;static int cap_hpage_1m; +static int cap_vcpu_resets;static int active_cmma;@@ -342,6 +343,7 @@ int kvm_arch_init(MachineState *ms, KVMState *s) cap_async_pf =kvm_check_extension (s,KVM_CAP_ASYNC_PF ); 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 );if (!kvm_check_extension (s,KVM_CAP_S390_GMAP ) || !kvm_check_extension (s,KVM_CAP_S390_COW )) {@@ -403,20 +405,44 @@ int kvm_arch_destroy_vcpu(CPUState *cs)return 0 ; } -void kvm_s390_reset_vcpu (S390CPU *cpu) +static void kvm_s390_reset_vcpu (S390CPU *cpu,unsigned long type) {CPUState *cs =CPU (cpu); -/* The initial reset call is needed here to reset in-kernel
target/s390x/kvm.c int kvm_arch_destroy_vcpu(CPUState *cs) · line 415
Quoted 10 lines
target/s390x/kvm.c +4
-6-* vcpu data that we can't access directly from QEMU -* (i.e. with older kernels which don't support sync_regs/ONE_REG). -* Before this ioctl cpu_synchronize_state() is called in common kvm -* code (kvm-all) */ -if (kvm_vcpu_ioctl (cs,KVM_S390_INITIAL_RESET ,NULL )) { -error_report ("Initial CPU reset failed on CPU %i" , cs->cpu_index); +/* +* The reset call is needed here to reset in-kernel vcpu data that +* we can't access directly from QEMU (i.e. with older kernels +* which don't support sync_regs/ONE_REG). Before this ioctl
Is the reference to sync_regs/ONE_REG still relevant? I'm a bit confused here, especially with regard to what we'll need for protected virt.
Quoted 10 lines
target/s390x/kvm.c +7
-0+* cpu_synchronize_state() is called in common kvm code +* (kvm-all). +*/ +if (kvm_vcpu_ioctl (cs, type)) { +error_report ("CPU reset failed on CPU %i" , cs->cpu_index); } } +void kvm_s390_reset_vcpu_initial (S390CPU *cpu) +{
target/s390x/kvm.c int kvm_arch_destroy_vcpu(CPUState *cs) · line 435
Quoted 10 lines
target/s390x/kvm.c +10
-0+kvm_s390_reset_vcpu (cpu,KVM_S390_INITIAL_RESET ); +} + +void kvm_s390_reset_vcpu_clear (S390CPU *cpu) +{ +if (!cap_vcpu_resets) { +kvm_s390_reset_vcpu (cpu,KVM_S390_INITIAL_RESET ); + }else { +kvm_s390_reset_vcpu (cpu,KVM_S390_CLEAR_RESET ); + }
kvm_s390_reset_vcpu(cpu, cap_vcpu_resets ? KVM_S390_CLEAR_RESET : KVM_S390_INITIAL_RESET);
One line, but maybe the conventional if is still better :)
Quoted 28 lines
target/s390x/kvm.c +10
-0+} + +void kvm_s390_reset_vcpu_normal (S390CPU *cpu) +{ +if (!cap_vcpu_resets) { +return ; + } +kvm_s390_reset_vcpu (cpu,KVM_S390_NORMAL_RESET ); +} +static int can_sync_regs (CPUState *cs,int regs) {return cap_sync_regs && (cs->kvm_run->kvm_valid_regs & regs) == regs;target/s390x/kvm_s390x.h +3
-1@@ -34,7 +34,9 @@ int kvm_s390_assign_subch_ioeventfd(EventNotifier *notifier, uint32_t sch, int vq, bool assign);int kvm_s390_cmma_active (void );void kvm_s390_cmma_reset (void ); -void kvm_s390_reset_vcpu (S390CPU *cpu); +void kvm_s390_reset_vcpu_clear (S390CPU *cpu); +void kvm_s390_reset_vcpu_normal (S390CPU *cpu); +void kvm_s390_reset_vcpu_initial (S390CPU *cpu);int kvm_s390_set_mem_limit (uint64_t new_limit,uint64_t *hw_limit);void kvm_s390_set_max_pagesize (uint64_t pagesize,Error **errp);void kvm_s390_crypto_reset (void );
Re: [PATCH v2 2/3] s390x: Add missing vcpu reset functions
Quoted 7 lines · Cornelia Huck
Quoted 2 lines · On Mon, 2 Dec 2019 09:01:45 -0500 Janosch Frank <[email protected]> wrote:
Up to now we only had an ioctl to reset vcpu data QEMU couldn't reach for the initial reset, which was also called for the clear reset. To
s/which/and that/ ?
Ok
Quoted 22 lines
Quoted 22 lines
be architecture compliant, we also need to clear local interrupts on a normal reset.
Because of this and the upcoming protvirt support we need to add ioctls for the missing clear and normal resets.
Signed-off-by Janosch Frank <[email protected]>--- target/s390x/cpu.c | 14 ++++++++++++-- target/s390x/kvm-stub.c | 10 +++++++++- target/s390x/kvm.c | 42 ++++++++++++++++++++++++++++++++-------- target/s390x/kvm_s390x.h | 4 +++- 4 files changed, 58 insertions(+), 12 deletions(-)target/s390x/cpu.c +0
-0@@ -139,8 +139,18 @@ static void s390_cpu_reset(CPUState *s, cpu_reset_type type) }
Quoted 4 lines
target/s390x/cpu.c static void s390_cpu_reset(CPUState *s, cpu_reset_type type) · line 141
Quoted 1 line
target/s390x/cpu.c +0
-0/* Reset state inside the kernel that we cannot access yet from QEMU. */ Hm, why does this comment talk about 'yet'? Did we have any plans to change that?
You're asking the wrong person :)
Quoted 15 lines
Quoted 4 lines
target/s390x/cpu.c +1
-2-if (kvm_enabled () && type !=S390_CPU_RESET_NORMAL ) { -kvm_s390_reset_vcpu (cpu); +if (kvm_enabled ()) {target/s390x/cpu.c static void s390_cpu_reset(CPUState *s, cpu_reset_type type) · line 152
Quoted 10 lines
target/s390x/cpu.c +10
-0+switch (type) { +case S390_CPU_RESET_CLEAR : +kvm_s390_reset_vcpu_clear (cpu); +break ; +case S390_CPU_RESET_INITIAL : +kvm_s390_reset_vcpu_initial (cpu); +break ; +case S390_CPU_RESET_NORMAL : +kvm_s390_reset_vcpu_normal (cpu); +break ;
Quoted 1 line
Add a default case to catch errors?
Sure, just did
Quoted 37 lines
Quoted 5 lines
target/s390x/cpu.c +1
-0+ } } }(...)
Quoted 29 lines
target/s390x/kvm.c +3
-1@@ -151,6 +151,7 @@ static int cap_s390_irq;static int cap_ri;static int cap_gs;static int cap_hpage_1m; +static int cap_vcpu_resets;static int active_cmma;@@ -342,6 +343,7 @@ int kvm_arch_init(MachineState *ms, KVMState *s) cap_async_pf =kvm_check_extension (s,KVM_CAP_ASYNC_PF ); 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 );if (!kvm_check_extension (s,KVM_CAP_S390_GMAP ) || !kvm_check_extension (s,KVM_CAP_S390_COW )) {@@ -403,20 +405,44 @@ int kvm_arch_destroy_vcpu(CPUState *cs)return 0 ; } -void kvm_s390_reset_vcpu (S390CPU *cpu) +static void kvm_s390_reset_vcpu (S390CPU *cpu,unsigned long type) {CPUState *cs =CPU (cpu);
Quoted 15 lines
target/s390x/kvm.c int kvm_arch_destroy_vcpu(CPUState *cs) · line 415
Quoted 11 lines
target/s390x/kvm.c +4
-7-/* The initial reset call is needed here to reset in-kernel -* vcpu data that we can't access directly from QEMU -* (i.e. with older kernels which don't support sync_regs/ONE_REG). -* Before this ioctl cpu_synchronize_state() is called in common kvm -* code (kvm-all) */ -if (kvm_vcpu_ioctl (cs,KVM_S390_INITIAL_RESET ,NULL )) { -error_report ("Initial CPU reset failed on CPU %i" , cs->cpu_index); +/* +* The reset call is needed here to reset in-kernel vcpu data that +* we can't access directly from QEMU (i.e. with older kernels +* which don't support sync_regs/ONE_REG). Before this ioctl Is the reference to sync_regs/ONE_REG still relevant? I'm a bit confused here, especially with regard to what we'll need for protected virt.
I just didn't want to move/remove stuff
Even with kvm_run we do a lot of stuff for the initial reset.
Quoted 24 lines
Quoted 11 lines
target/s390x/kvm.c +7
-0+* cpu_synchronize_state() is called in common kvm code +* (kvm-all). +*/ +if (kvm_vcpu_ioctl (cs, type)) { +error_report ("CPU reset failed on CPU %i" , cs->cpu_index); } } +void kvm_s390_reset_vcpu_initial (S390CPU *cpu) +{target/s390x/kvm.c int kvm_arch_destroy_vcpu(CPUState *cs) · line 435
Quoted 10 lines
target/s390x/kvm.c +10
-0+kvm_s390_reset_vcpu (cpu,KVM_S390_INITIAL_RESET ); +} + +void kvm_s390_reset_vcpu_clear (S390CPU *cpu) +{ +if (!cap_vcpu_resets) { +kvm_s390_reset_vcpu (cpu,KVM_S390_INITIAL_RESET ); + }else { +kvm_s390_reset_vcpu (cpu,KVM_S390_CLEAR_RESET ); + }
kvm_s390_reset_vcpu(cpu, cap_vcpu_resets ? KVM_S390_CLEAR_RESET : KVM_S390_INITIAL_RESET);
Quoted 1 line
One line, but maybe the conventional if is still better :)
I'd like to keep it as is.
Quoted 31 lines
Quoted 29 lines
target/s390x/kvm.c +10
-0+} + +void kvm_s390_reset_vcpu_normal (S390CPU *cpu) +{ +if (!cap_vcpu_resets) { +return ; + } +kvm_s390_reset_vcpu (cpu,KVM_S390_NORMAL_RESET ); +} +static int can_sync_regs (CPUState *cs,int regs) {return cap_sync_regs && (cs->kvm_run->kvm_valid_regs & regs) == regs;target/s390x/kvm_s390x.h +3
-1@@ -34,7 +34,9 @@ int kvm_s390_assign_subch_ioeventfd(EventNotifier *notifier, uint32_t sch, int vq, bool assign);int kvm_s390_cmma_active (void );void kvm_s390_cmma_reset (void ); -void kvm_s390_reset_vcpu (S390CPU *cpu); +void kvm_s390_reset_vcpu_clear (S390CPU *cpu); +void kvm_s390_reset_vcpu_normal (S390CPU *cpu); +void kvm_s390_reset_vcpu_initial (S390CPU *cpu);int kvm_s390_set_mem_limit (uint64_t new_limit,uint64_t *hw_limit);void kvm_s390_set_max_pagesize (uint64_t pagesize,Error **errp);void kvm_s390_crypto_reset (void );
PATCH v2 3/3 s390x: Fix cpu normal reset ri clearing
In reply to Janosch FrankAs it turns out we need to clear the ri controls and PSW enablement bit to be architecture compliant.
--- target/s390x/cpu.c | 5 +++++ target/s390x/cpu.h | 7 ++++++- 2 files changed, 11 insertions(+), 1 deletion(-)
target/s390x/cpu.c +5 -0
@@ -131,6 +131,11 @@ static void s390_cpu_reset(CPUState *s, cpu_reset_type type) &env->fpu_status);/* fall through */ case S390_CPU_RESET_NORMAL : + env->psw.mask &= ~PSW_MASK_RI ; +memset (&env->start_normal_reset_fields,0 , + offsetof(CPUS390XState , end_reset_fields) - + offsetof(CPUS390XState , start_normal_reset_fields)); + env->pfault_token =-1UL ; env->bpbc = false;break ;
target/s390x/cpu.h +6 -1
@@ -58,7 +58,6 @@ struct CPUS390XState {*/ uint64_t vregs[32][2] QEMU_ALIGNED(16); /* vector registers */uint32_t aregs[16 ];/* access registers */ -uint8_t riccb[64 ];/* runtime instrumentation control */ uint64_t gscb[4 ];/* guarded storage control */ uint64_t etoken;/* etoken */ uint64_t etoken_extension;/* etoken extension */
@@ -114,6 +113,10 @@ struct CPUS390XState {uint64_t gbea;uint64_t pp; +/* Fields up to this point are not cleared by normal CPU reset */ +struct {} start_normal_reset_fields; +uint8_t riccb[64 ];/* runtime instrumentation control */ +/* Fields up to this point are cleared by a CPU reset */ struct {} end_reset_fields;
@@ -252,6 +255,7 @@ extern const VMStateDescription vmstate_s390_cpu;#undef PSW_SHIFT_ASC#undef PSW_MASK_CC#undef PSW_MASK_PM +#undef PSW_MASK_RI#undef PSW_SHIFT_MASK_PM#undef PSW_MASK_64#undef PSW_MASK_32
@@ -274,6 +278,7 @@ extern const VMStateDescription vmstate_s390_cpu;#define PSW_MASK_CC 0x0000300000000000ULL#define PSW_MASK_PM 0x00000F0000000000ULL#define PSW_SHIFT_MASK_PM 40 +#define PSW_MASK_RI 0x0000008000000000ULL#define PSW_MASK_64 0x0000000100000000ULL#define PSW_MASK_32 0x0000000080000000ULL#define PSW_MASK_ESA_ADDR 0x000000007fffffffULL
Signature · 1 line
2.20.1
Re: [PATCH v2 3/3] s390x: Fix cpu normal reset ri clearing
Quoted 14 lines · Janosch Frank
As it turns out we need to clear the ri controls and PSW enablement bit to be architecture compliant.
Signed-off-by Janosch Frank <[email protected]>--- target/s390x/cpu.c | 5 +++++ target/s390x/cpu.h | 7 ++++++- 2 files changed, 11 insertions(+), 1 deletion(-)target/s390x/cpu.c +0
-0
target/s390x/cpu.c static void s390_cpu_reset(CPUState *s, cpu_reset_type type) · line 132
Quoted 2 lines
target/s390x/cpu.c +0
-0@@ -131,6 +131,11 @@ static void s390_cpu_reset(CPUState *s, cpu_reset_type type) &env->fpu_status);/* fall through */
As this is a fall through, do we want to change the INITIAL RESET to only clear up to start_normal_reset_fields, e.g. something like this on top
target/s390x/cpu.c +1 -1
@@ -108,7 +108,7 @@ static void s390_cpu_reset(CPUState *s, cpu_reset_type type)case S390_CPU_RESET_INITIAL :/* initial reset does not clear everything! */ memset (&env->start_initial_reset_fields,0 , - offsetof(CPUS390XState , end_reset_fields) - + offsetof(CPUS390XState , start_normal_reset_fields) - offsetof(CPUS390XState , start_initial_reset_fields));/* architectured initial value for Breaking-Event-Address register */
to avoid double memsetting.
Other than this question
Quoted 49 lines
target/s390x/cpu.c +5
-0case S390_CPU_RESET_NORMAL : + env->psw.mask &= ~PSW_MASK_RI ; +memset (&env->start_normal_reset_fields,0 , + offsetof(CPUS390XState , end_reset_fields) - + offsetof(CPUS390XState , start_normal_reset_fields)); + env->pfault_token =-1UL ; env->bpbc = false;break ;target/s390x/cpu.h +6
-1@@ -58,7 +58,6 @@ struct CPUS390XState {*/ uint64_t vregs[32][2] QEMU_ALIGNED(16); /* vector registers */uint32_t aregs[16 ];/* access registers */ -uint8_t riccb[64 ];/* runtime instrumentation control */ uint64_t gscb[4 ];/* guarded storage control */ uint64_t etoken;/* etoken */ uint64_t etoken_extension;/* etoken extension */ @@ -114,6 +113,10 @@ struct CPUS390XState {uint64_t gbea;uint64_t pp; +/* Fields up to this point are not cleared by normal CPU reset */ +struct {} start_normal_reset_fields; +uint8_t riccb[64 ];/* runtime instrumentation control */ +/* Fields up to this point are cleared by a CPU reset */ struct {} end_reset_fields;@@ -252,6 +255,7 @@ extern const VMStateDescription vmstate_s390_cpu;#undef PSW_SHIFT_ASC#undef PSW_MASK_CC#undef PSW_MASK_PM +#undef PSW_MASK_RI#undef PSW_SHIFT_MASK_PM#undef PSW_MASK_64#undef PSW_MASK_32@@ -274,6 +278,7 @@ extern const VMStateDescription vmstate_s390_cpu;#define PSW_MASK_CC 0x0000300000000000ULL#define PSW_MASK_PM 0x00000F0000000000ULL#define PSW_SHIFT_MASK_PM 40 +#define PSW_MASK_RI 0x0000008000000000ULL#define PSW_MASK_64 0x0000000100000000ULL#define PSW_MASK_32 0x0000000080000000ULL#define PSW_MASK_ESA_ADDR 0x000000007fffffffULL
Re: [PATCH v2 3/3] s390x: Fix cpu normal reset ri clearing
In reply to Janosch FrankQuoted 58 lines · Janosch Frank
As it turns out we need to clear the ri controls and PSW enablement bit to be architecture compliant.
Signed-off-by Janosch Frank <[email protected]>--- target/s390x/cpu.c | 5 +++++ target/s390x/cpu.h | 7 ++++++- 2 files changed, 11 insertions(+), 1 deletion(-)target/s390x/cpu.c +5
-0@@ -131,6 +131,11 @@ static void s390_cpu_reset(CPUState *s, cpu_reset_type type) &env->fpu_status);/* fall through */ case S390_CPU_RESET_NORMAL : + env->psw.mask &= ~PSW_MASK_RI ; +memset (&env->start_normal_reset_fields,0 , + offsetof(CPUS390XState , end_reset_fields) - + offsetof(CPUS390XState , start_normal_reset_fields)); + env->pfault_token =-1UL ; env->bpbc = false;break ;target/s390x/cpu.h +5
-1@@ -58,7 +58,6 @@ struct CPUS390XState {*/ uint64_t vregs[32][2] QEMU_ALIGNED(16); /* vector registers */uint32_t aregs[16 ];/* access registers */ -uint8_t riccb[64 ];/* runtime instrumentation control */ uint64_t gscb[4 ];/* guarded storage control */ uint64_t etoken;/* etoken */ uint64_t etoken_extension;/* etoken extension */ @@ -114,6 +113,10 @@ struct CPUS390XState {uint64_t gbea;uint64_t pp; +/* Fields up to this point are not cleared by normal CPU reset */ +struct {} start_normal_reset_fields; +uint8_t riccb[64 ];/* runtime instrumentation control */ +/* Fields up to this point are cleared by a CPU reset */ struct {} end_reset_fields;@@ -252,6 +255,7 @@ extern const VMStateDescription vmstate_s390_cpu;#undef PSW_SHIFT_ASC#undef PSW_MASK_CC#undef PSW_MASK_PM +#undef PSW_MASK_RI#undef PSW_SHIFT_MASK_PM#undef PSW_MASK_64#undef PSW_MASK_32
target/s390x/cpu.h extern const VMStateDescription vmstate_s390_cpu; · line 284
Quoted 7 lines
target/s390x/cpu.h +1
-0@@ -274,6 +278,7 @@ extern const VMStateDescription vmstate_s390_cpu;#define PSW_MASK_CC 0x0000300000000000ULL#define PSW_MASK_PM 0x00000F0000000000ULL#define PSW_SHIFT_MASK_PM 40 +#define PSW_MASK_RI 0x0000008000000000ULL#define PSW_MASK_64 0x0000000100000000ULL#define PSW_MASK_32 0x0000000080000000ULL#define PSW_MASK_ESA_ADDR 0x000000007fffffffULL
I'm afraid I can't help because the documentation is confidential. It does look sane to me, at least.
Signature · 3 lines
Thanks, David / dhildenb