mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-21 22:20:37 +07:00
0e7def5fb0
Right now, SET CLOCK called in the guest does not properly take care of
the epoch index, as the call goes via the old kvm_s390_set_tod_clock()
interface. So the epoch index is neither reset to 0, if required, nor
properly set to e.g. 0xff on negative values.
Fix this by providing a single kvm_s390_set_tod_clock() function. Move
Multiple-epoch facility handling into it.
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20180207114647.6220-3-david@redhat.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
Fixes:
|
||
---|---|---|
.. | ||
diag.c | ||
gaccess.c | ||
gaccess.h | ||
guestdbg.c | ||
intercept.c | ||
interrupt.c | ||
irq.h | ||
Kconfig | ||
kvm-s390.c | ||
kvm-s390.h | ||
Makefile | ||
priv.c | ||
sigp.c | ||
trace-s390.h | ||
trace.h | ||
vsie.c |