diff options
| author | Collin Walling <walling@linux.ibm.com> | 2020-11-13 17:10:22 -0500 |
|---|---|---|
| committer | Cornelia Huck <cohuck@redhat.com> | 2020-11-18 16:57:48 +0100 |
| commit | e2c6cd567422bfa563be026b9741a1854aecdc06 (patch) | |
| tree | d7a10886fbbd0732ba14bb79ba56fc1ff2892d13 /target/s390x/cpu.c | |
| parent | b696f2c6ba8c92ffb5eca49b88a5c7276d0a3e1e (diff) | |
| download | qemu-e2c6cd567422bfa563be026b9741a1854aecdc06.zip qemu-e2c6cd567422bfa563be026b9741a1854aecdc06.tar.gz qemu-e2c6cd567422bfa563be026b9741a1854aecdc06.tar.bz2 | |
s390/kvm: fix diag318 propagation and reset functionality
The Control Program Name Code (CPNC) portion of the diag318
info must be set within the SIE block of each VCPU in the
configuration. The handler will iterate through each VCPU
and dirty the diag318_info reg to be synced with KVM on a
subsequent sync_regs call.
Additionally, the diag318 info resets must be handled via
userspace. As such, QEMU will reset this value for each
VCPU during a modified clear, load normal, and load clear
reset event.
Fixes: fabdada9357b ("s390: guest support for diagnose 0x318")
Signed-off-by: Collin Walling <walling@linux.ibm.com>
Message-Id: <20201113221022.257054-1-walling@linux.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Janosch Frank <frankja@de.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
Diffstat (limited to 'target/s390x/cpu.c')
| -rw-r--r-- | target/s390x/cpu.c | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/target/s390x/cpu.c b/target/s390x/cpu.c index 66f5942..7b66718 100644 --- a/target/s390x/cpu.c +++ b/target/s390x/cpu.c @@ -447,6 +447,13 @@ void s390_enable_css_support(S390CPU *cpu) kvm_s390_enable_css_support(cpu); } } + +void s390_do_cpu_set_diag318(CPUState *cs, run_on_cpu_data arg) +{ + if (kvm_enabled()) { + kvm_s390_set_diag318(cs, arg.host_ulong); + } +} #endif static gchar *s390_gdb_arch_name(CPUState *cs) |