From: Pierre Morel <pmorel@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
borntraeger@de.ibm.com, frankja@linux.ibm.com, cohuck@redhat.com,
thuth@redhat.com, imbrenda@linux.ibm.com, hca@linux.ibm.com,
gor@linux.ibm.com
Subject: Re: [PATCH v3 2/3] s390x: KVM: Implementation of Multiprocessor Topology-Change-Report
Date: Wed, 1 Sep 2021 11:46:02 +0200 [thread overview]
Message-ID: <98d3b4fb-f875-d833-2a75-5412cd426ec7@linux.ibm.com> (raw)
In-Reply-To: <4d462f11-2990-6799-75e5-add0c39f9563@redhat.com>
On 8/31/21 4:03 PM, David Hildenbrand wrote:
> On 03.08.21 10:26, Pierre Morel wrote:
...snip...
>> @@ -819,6 +820,23 @@ int kvm_vm_ioctl_enable_cap(struct kvm *kvm,
>> struct kvm_enable_cap *cap)
>> icpt_operexc_on_all_vcpus(kvm);
>> r = 0;
>> break;
>> + case KVM_CAP_S390_CPU_TOPOLOGY:
>> + mutex_lock(&kvm->lock);
>> + if (kvm->created_vcpus) {
>> + r = -EBUSY;
>> + } else {
>> + set_kvm_facility(kvm->arch.model.fac_mask, 11);
>> + set_kvm_facility(kvm->arch.model.fac_list, 11);
>> + r = 0;
>> + }
>> + mutex_unlock(&kvm->lock);
>> + VM_EVENT(kvm, 3, "ENABLE: CPU TOPOLOGY %s",
>> + r ? "(not available)" : "(success)");
>> + break;
>> +
>> + r = -EINVAL;
>> + break;
>> +
>> default:
>> r = -EINVAL;
>> break;
This above enables the facility 11.
...snip...
>> @@ -3198,6 +3239,11 @@ static int kvm_s390_vcpu_setup(struct kvm_vcpu
>> *vcpu)
>> vcpu->arch.sie_block->ecb |= ECB_HOSTPROTINT;
>> if (test_kvm_facility(vcpu->kvm, 9))
>> vcpu->arch.sie_block->ecb |= ECB_SRSI;
>> +
>> + /* PTF needs both host and guest facilities to enable
>> interpretation */
>> + if (test_kvm_facility(vcpu->kvm, 11) && test_facility(11))
>> + vcpu->arch.sie_block->ecb |= ECB_PTF;
>
>
> Again, doesn't test_kvm_facility(vcpu->kvm, 11) imply that we have host
> support by checking fac_mask?
>
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2021-09-01 9:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 8:26 [PATCH v3 0/3] s390x: KVM: CPU Topology Pierre Morel
2021-08-03 8:26 ` [PATCH v3 1/3] s390x: KVM: accept STSI for CPU topology information Pierre Morel
2021-08-31 13:59 ` David Hildenbrand
2021-09-01 9:43 ` Pierre Morel
2021-09-06 18:14 ` David Hildenbrand
2021-09-07 10:11 ` Pierre Morel
2021-08-03 8:26 ` [PATCH v3 2/3] s390x: KVM: Implementation of Multiprocessor Topology-Change-Report Pierre Morel
2021-08-31 14:03 ` David Hildenbrand
2021-09-01 9:46 ` Pierre Morel [this message]
2021-09-06 18:37 ` David Hildenbrand
2021-09-07 10:24 ` Pierre Morel
2021-09-08 7:04 ` Christian Borntraeger
2021-09-08 12:00 ` Pierre Morel
2021-09-08 12:01 ` Christian Borntraeger
2021-09-08 12:52 ` Pierre Morel
2021-09-07 12:28 ` Pierre Morel
2021-09-08 7:07 ` Christian Borntraeger
2021-09-08 13:09 ` Pierre Morel
2021-09-08 13:16 ` Christian Borntraeger
2021-09-08 14:17 ` Pierre Morel
2021-09-09 9:03 ` Pierre Morel
2021-08-03 8:26 ` [PATCH v3 3/3] s390x: optimization of the check for CPU topology change Pierre Morel
2021-08-03 8:42 ` Heiko Carstens
2021-08-03 8:57 ` Pierre Morel
2021-08-03 9:28 ` Pierre Morel
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=98d3b4fb-f875-d833-2a75-5412cd426ec7@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.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).