From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Halil Pasic <pasic@linux.ibm.com>
Cc: qemu-s390x@nongnu.org, "David Hildenbrand" <david@redhat.com>,
"Cédric Le Goater" <clegoate@redhat.com>
Subject: Re: [PATCH v2 1/2] target/s390x/kvm: Turn KVM_CAP_SYNC_REGS into a hard requirement
Date: Tue, 10 Oct 2023 13:36:37 +0200 [thread overview]
Message-ID: <a3dbcec6-e0ef-74e7-fa20-6846caf156a6@linux.ibm.com> (raw)
In-Reply-To: <2f6dcd26-9a53-390a-5acc-b8021b6190c5@redhat.com>
Am 10.10.23 um 13:12 schrieb Thomas Huth:
> On 10/10/2023 13.02, Christian Borntraeger wrote:
>>
>>
>> Am 09.10.23 um 19:07 schrieb Thomas Huth:
>>> 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.
>>>
>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>> ---
>>> target/s390x/kvm/kvm.c | 20 ++++++++++++++------
>>> 1 file changed, 14 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/target/s390x/kvm/kvm.c b/target/s390x/kvm/kvm.c
>>> index bc5c56a305..b3e2eaa2eb 100644
>>> --- a/target/s390x/kvm/kvm.c
>>> +++ b/target/s390x/kvm/kvm.c
>>> @@ -337,21 +337,29 @@ int kvm_arch_get_default_type(MachineState *ms)
>>> int kvm_arch_init(MachineState *ms, KVMState *s)
>>> {
>>> + int required_caps[] = {
>>> + KVM_CAP_DEVICE_CTRL,
>>> + KVM_CAP_SYNC_REGS,
>>> + };
>>> +
>>> + for (int i = 0; i < ARRAY_SIZE(required_caps); i++) {
>>> + if (!kvm_check_extension(s, required_caps[i])) {
>>> + error_report("KVM is missing capability #%d - "
>>> + "please use kernel 3.15 or newer", required_caps[i]);
>>> + return -1;
>>> + }
>>> + }
>>> +
>>> object_class_foreach(ccw_machine_class_foreach, TYPE_S390_CCW_MACHINE,
>>> false, NULL);
>>> - if (!kvm_check_extension(kvm_state, KVM_CAP_DEVICE_CTRL)) {
>>> - error_report("KVM is missing capability KVM_CAP_DEVICE_CTRL - "
>>> - "please use kernel 3.15 or newer");
>>> - return -1;
>>> - }
>>> if (!kvm_check_extension(s, KVM_CAP_S390_COW)) {
>>> error_report("KVM is missing capability KVM_CAP_S390_COW - "
>>> "unsupported environment");
>>> return -1;
>>> }
>>
>> Not sure if we also want to move KVM_CAP_S390_COW somehow. The message would be different.
>
> IIRC that error could happen when you ran KVM within an older version of z/VM, so the "please use kernel 3.15 or newer" message would be completely misleading there.
Yes, thats what I was trying to say, we would need a different message.
Lets go with this patch.
>
>> Aparch from that:
>> Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>
>
> Thanks,
> Thomas
>
>
next prev parent reply other threads:[~2023-10-10 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 17:07 [PATCH v2 0/2] target/s390x/kvm: Simplify the synchronization code Thomas Huth
2023-10-09 17:07 ` [PATCH v2 1/2] target/s390x/kvm: Turn KVM_CAP_SYNC_REGS into a hard requirement Thomas Huth
2023-10-10 11:02 ` Christian Borntraeger
2023-10-10 11:12 ` Thomas Huth
2023-10-10 11:36 ` Christian Borntraeger [this message]
2023-10-09 17:07 ` [PATCH v2 2/2] target/s390x/kvm: Simplify the GPRs, ACRs, CRs and prefix synchronization code Thomas Huth
2023-10-10 11:41 ` Christian Borntraeger
2023-10-10 11:46 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3dbcec6-e0ef-74e7-fa20-6846caf156a6@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=clegoate@redhat.com \
--cc=david@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).