From: Eric Auger <eauger@redhat.com>
To: Gavin Shan <gshan@redhat.com>, kvmarm@lists.cs.columbia.edu
Cc: maz@kernel.org, linux-kernel@vger.kernel.org,
Jonathan.Cameron@huawei.com, pbonzini@redhat.com,
will@kernel.org
Subject: Re: [PATCH v4 09/21] KVM: arm64: Support SDEI_EVENT_GET_INFO hypercall
Date: Thu, 27 Jan 2022 15:19:34 +0100 [thread overview]
Message-ID: <9764c112-733a-fae5-b198-c0b0b2370f2a@redhat.com> (raw)
In-Reply-To: <44039a09-344f-3ac9-0d58-c0c8c4562b60@redhat.com>
Hi Gavin,
On 1/12/22 3:46 AM, Gavin Shan wrote:
> Hi Eric,
>
> On 11/10/21 1:19 AM, Eric Auger wrote:
>> On 8/15/21 2:13 AM, Gavin Shan wrote:
>>> This supports SDEI_EVENT_GET_INFO hypercall. It's used by the guest
>>> to retrieve various information about the supported (exported) events,
>>> including type, signaled, route mode and affinity for the shared
>>> events.
>>>
>>> Signed-off-by: Gavin Shan <gshan@redhat.com>
>>> ---
>>> arch/arm64/kvm/sdei.c | 76 +++++++++++++++++++++++++++++++++++++++++++
>>> 1 file changed, 76 insertions(+)
>>>
>>> diff --git a/arch/arm64/kvm/sdei.c b/arch/arm64/kvm/sdei.c
>>> index b95b8c4455e1..5dfa74b093f1 100644
>>> --- a/arch/arm64/kvm/sdei.c
>>> +++ b/arch/arm64/kvm/sdei.c
>>> @@ -415,6 +415,80 @@ static unsigned long
>>> kvm_sdei_hypercall_status(struct kvm_vcpu *vcpu)
>>> return ret;
>>> }
>>> +static unsigned long kvm_sdei_hypercall_info(struct kvm_vcpu *vcpu)
>>> +{
>>> + struct kvm *kvm = vcpu->kvm;
>>> + struct kvm_sdei_kvm *ksdei = kvm->arch.sdei;
>>> + struct kvm_sdei_vcpu *vsdei = vcpu->arch.sdei;
>>> + struct kvm_sdei_event *kse = NULL;
>>> + struct kvm_sdei_kvm_event *kske = NULL;
>>> + unsigned long event_num = smccc_get_arg1(vcpu);
>>> + unsigned long event_info = smccc_get_arg2(vcpu);
>>> + unsigned long ret = SDEI_SUCCESS;
>>> +
>>> + /* Sanity check */
>>> + if (!(ksdei && vsdei)) {
>>> + ret = SDEI_NOT_SUPPORTED;
>>> + goto out;
>>> + }
>>> +
>>> + if (!kvm_sdei_is_valid_event_num(event_num)) {
>>> + ret = SDEI_INVALID_PARAMETERS;
>>> + goto out;
>>> + }
>>> +
>>> + /*
>>> + * Check if the KVM event exists. The event might have been
>>> + * registered, we need fetch the information from the registered
>> s/fetch/to fetch
>
> Ack.
>
>>> + * event in that case.
>>> + */
>>> + spin_lock(&ksdei->lock);
>>> + kske = kvm_sdei_find_kvm_event(kvm, event_num);
>>> + kse = kske ? kske->kse : NULL;
>>> + if (!kse) {
>>> + kse = kvm_sdei_find_event(kvm, event_num);
>>> + if (!kse) {
>>> + ret = SDEI_INVALID_PARAMETERS;
>> this should have already be covered by !kvm_sdei_is_valid_event_num I
>> think (although this latter only checks the since static event num with
>> KVM owner mask)
>
> Nope. Strictly speaking, kvm_sdei_find_event() covers the check carried
> by !kvm_sdei_is_valid_event_num(). All the defined (exposed) events should
> have virtual event number :)
you're right
>
>>> + goto unlock;
>>> + }
>>> + }
>>> +
>>> + /* Retrieve the requested information */
>>> + switch (event_info) {
>>> + case SDEI_EVENT_INFO_EV_TYPE:
>>> + ret = kse->state.type;
>>> + break;
>>> + case SDEI_EVENT_INFO_EV_SIGNALED:
>>> + ret = kse->state.signaled;
>>> + break;
>>> + case SDEI_EVENT_INFO_EV_PRIORITY:
>>> + ret = kse->state.priority;
>>> + break;
>>> + case SDEI_EVENT_INFO_EV_ROUTING_MODE:
>>> + case SDEI_EVENT_INFO_EV_ROUTING_AFF:
>>> + if (kse->state.type != SDEI_EVENT_TYPE_SHARED) {
>>> + ret = SDEI_INVALID_PARAMETERS;
>>> + break;
>>> + }
>>> +
>>> + if (event_info == SDEI_EVENT_INFO_EV_ROUTING_MODE) {
>>> + ret = kske ? kske->state.route_mode :
>>> + SDEI_EVENT_REGISTER_RM_ANY;
>> no, if event is not registered (!kske) DENIED should be returned
>
> I don't think so. According to the specification, there is no DENIED
> return value for STATUS hypercall. Either INVALID_PARAMETERS or
> NOT_SUPPORTED
> should be returned from this hypercall :)
Look at table 5.1.10.2 Parameter a,d Return Values. DENIED is returned
in some cases
Eric
>
>>> + } else {
>> same here
>>> + ret = kske ? kske->state.route_affinity : 0;
>>> + }
>>> +
>>> + break;
>>> + default:
>>> + ret = SDEI_INVALID_PARAMETERS;
>>> + }
>>> +
>>> +unlock:
>>> + spin_unlock(&ksdei->lock);
>>> +out:
>>> + return ret;
>>> +}
>>> +
>>> int kvm_sdei_hypercall(struct kvm_vcpu *vcpu)
>>> {
>>> u32 func = smccc_get_function(vcpu);
>>> @@ -446,6 +520,8 @@ int kvm_sdei_hypercall(struct kvm_vcpu *vcpu)
>>> ret = kvm_sdei_hypercall_status(vcpu);
>>> break;
>>> case SDEI_1_0_FN_SDEI_EVENT_GET_INFO:
>>> + ret = kvm_sdei_hypercall_info(vcpu);
>>> + break;
>>> case SDEI_1_0_FN_SDEI_EVENT_ROUTING_SET:
>>> case SDEI_1_0_FN_SDEI_PE_MASK:
>>> case SDEI_1_0_FN_SDEI_PE_UNMASK:
>>>
>
> Thanks,
> Gavin
>
next prev parent reply other threads:[~2022-01-27 14:19 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 0:13 [PATCH v4 00/21] Support SDEI Virtualization Gavin Shan
2021-08-15 0:13 ` [PATCH v4 01/21] KVM: arm64: Introduce template for inline functions Gavin Shan
2021-11-09 15:26 ` Eric Auger
2022-01-11 7:52 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 02/21] KVM: arm64: Add SDEI virtualization infrastructure Gavin Shan
2021-11-09 15:45 ` Eric Auger
2022-01-11 9:20 ` Gavin Shan
2022-01-27 13:17 ` Eric Auger
2022-01-11 9:40 ` Shannon Zhao
2022-01-13 7:09 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 03/21] KVM: arm64: Support SDEI_VERSION hypercall Gavin Shan
2021-11-09 15:26 ` Eric Auger
2022-01-11 9:25 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 04/21] KVM: arm64: Support SDEI_EVENT_REGISTER hypercall Gavin Shan
2021-11-09 15:50 ` Eric Auger
2022-01-12 2:19 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 05/21] KVM: arm64: Support SDEI_EVENT_{ENABLE, DISABLE} hypercall Gavin Shan
2021-11-09 16:02 ` Eric Auger
2022-01-12 2:29 ` Gavin Shan
2022-01-25 18:23 ` Eric Auger
2021-08-15 0:13 ` [PATCH v4 06/21] KVM: arm64: Support SDEI_EVENT_CONTEXT hypercall Gavin Shan
2021-11-10 11:16 ` Eric Auger
2022-01-12 2:33 ` Gavin Shan
2022-01-25 18:29 ` Eric Auger
2022-01-11 9:43 ` Shannon Zhao
2022-01-13 7:02 ` Gavin Shan
2022-01-13 7:13 ` Gavin Shan
2022-01-25 18:32 ` Eric Auger
2022-01-25 18:31 ` Eric Auger
2021-08-15 0:13 ` [PATCH v4 07/21] KVM: arm64: Support SDEI_EVENT_UNREGISTER hypercall Gavin Shan
2021-11-09 17:05 ` Eric Auger
2022-01-12 2:38 ` Gavin Shan
2022-01-25 18:42 ` Eric Auger
2021-08-15 0:13 ` [PATCH v4 08/21] KVM: arm64: Support SDEI_EVENT_STATUS hypercall Gavin Shan
2021-11-09 17:12 ` Eric Auger
2022-01-12 2:40 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 09/21] KVM: arm64: Support SDEI_EVENT_GET_INFO hypercall Gavin Shan
2021-11-09 17:19 ` Eric Auger
2022-01-12 2:46 ` Gavin Shan
2022-01-27 14:19 ` Eric Auger [this message]
2021-08-15 0:13 ` [PATCH v4 10/21] KVM: arm64: Support SDEI_EVENT_ROUTING_SET hypercall Gavin Shan
2021-11-09 18:47 ` Eric Auger
2022-01-12 2:54 ` Gavin Shan
2022-01-27 14:13 ` Eric Auger
2021-08-15 0:13 ` [PATCH v4 11/21] KVM: arm64: Support SDEI_PE_{MASK, UNMASK} hypercall Gavin Shan
2021-11-09 20:31 ` Eric Auger
2022-01-12 2:58 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 12/21] KVM: arm64: Support SDEI_{PRIVATE, SHARED}_RESET hypercall Gavin Shan
2021-11-09 20:37 ` Eric Auger
2022-01-12 3:01 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 13/21] KVM: arm64: Impment SDEI event delivery Gavin Shan
2021-11-10 10:58 ` Eric Auger
2022-01-12 6:34 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 14/21] KVM: arm64: Support SDEI_EVENT_{COMPLETE, COMPLETE_AND_RESUME} hypercall Gavin Shan
2021-11-10 10:58 ` Eric Auger
2022-01-12 6:43 ` Gavin Shan
2022-01-27 14:47 ` Eric Auger
2022-01-27 15:20 ` Eric Auger
2021-08-15 0:13 ` [PATCH v4 15/21] KVM: arm64: Support SDEI event notifier Gavin Shan
2021-11-10 11:35 ` Eric Auger
2022-01-12 6:48 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 16/21] KVM: arm64: Support SDEI ioctl commands on VM Gavin Shan
2021-11-10 13:48 ` Eric Auger
2022-01-12 7:03 ` Gavin Shan
2022-01-27 13:48 ` Eric Auger
2021-08-15 0:13 ` [PATCH v4 17/21] KVM: arm64: Support SDEI ioctl commands on vCPU Gavin Shan
2021-08-15 0:13 ` [PATCH v4 18/21] KVM: arm64: Support SDEI event injection Gavin Shan
2021-11-10 14:05 ` Eric Auger
2022-01-12 7:12 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 19/21] KVM: arm64: Support SDEI event cancellation Gavin Shan
2021-11-10 14:09 ` Eric Auger
2022-01-12 7:19 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 20/21] KVM: arm64: Export SDEI capability Gavin Shan
2021-11-10 13:55 ` Eric Auger
2022-01-12 7:20 ` Gavin Shan
2021-08-15 0:13 ` [PATCH v4 21/21] KVM: selftests: Add SDEI test case Gavin Shan
2021-08-15 0:19 ` [PATCH v4 00/21] Support SDEI Virtualization Gavin Shan
2021-11-10 14:29 ` Eric Auger
2022-01-12 7:24 ` Gavin Shan
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=9764c112-733a-fae5-b198-c0b0b2370f2a@redhat.com \
--to=eauger@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=gshan@redhat.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=will@kernel.org \
/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).