| commit | c35a79cbd7dc2ff3435355177290b7b31b589993 | |
| author | Thomas Huth <thuth@redhat.com> | |
| Wed, 11 Oct 2023 08:05:37 +0000 (11 10:05 +0200) | ||
| committer | Thomas Huth <thuth@redhat.com> | |
| Fri, 20 Oct 2023 05:16:53 +0000 (20 07:16 +0200) | ||
| tree | 15b23630130d856998f222b61d254438d13c72c1 | treesnapshot (tar.gz zip) |
| parent | 219922ef9b7af4b425c85a7c14c79c2f68f1a19b | commitdiff |
target/s390x/kvm: Turn KVM_CAP_SYNC_REGS into a hard requirement
Since we already require at least kernel 3.15 in the s390x KVM code,
we can assume that the KVM_CAP_SYNC_REGS capability is always there.
Thus turn this into a hard requirement now.
Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Message-ID: <20231011080538.796999-2-thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Since we already require at least kernel 3.15 in the s390x KVM code,
we can assume that the KVM_CAP_SYNC_REGS capability is always there.
Thus turn this into a hard requirement now.
Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Message-ID: <20231011080538.796999-2-thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
| target/s390x/kvm/kvm.c | diffblobblamehistory |