diff options
| author | David Hildenbrand <david@redhat.com> | 2018-02-07 12:46:43 +0100 |
|---|---|---|
| committer | Christian Borntraeger <borntraeger@de.ibm.com> | 2018-02-20 20:51:28 +0000 |
| commit | 0e7def5fb0dc53ddbb9f62a497d15f1e11ccdc36 (patch) | |
| tree | 0f79bbd4a0fc3e2c2cfc12fa494ce110e404bac0 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 1575767ef3cf5326701d2ae3075b7732cbc855e4 (diff) | |
| download | kernel-0e7def5fb0dc53ddbb9f62a497d15f1e11ccdc36.tar.gz | |
KVM: s390: provide only a single function for setting the tod (fix SCK)
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: 8fa1696ea781 ("KVM: s390: Multiple Epoch Facility support")
Cc: stable@vger.kernel.org
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions