From: Gavin Shan <gshan@redhat.com> To: Eric Auger <eauger@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 12/21] KVM: arm64: Support SDEI_{PRIVATE, SHARED}_RESET hypercall Date: Wed, 12 Jan 2022 11:01:21 +0800 [thread overview] Message-ID: <d163631c-6e66-f7a1-6eea-3bc000e771ca@redhat.com> (raw) In-Reply-To: <a4b91fa5-12b0-afeb-4449-c2acb59e8cd7@redhat.com> Hi Eric, On 11/10/21 4:37 AM, Eric Auger wrote: > On 8/15/21 2:13 AM, Gavin Shan wrote: >> This supports SDEI_{PRIVATE, SHARED}_RESET. They are used by the >> guest to purge the private or shared SDEI events, which are registered > to reset all private SDEI event registrations of the calling PE (resp. > PRIVATE or SHARED) Ok. >> previously. >> >> Signed-off-by: Gavin Shan <gshan@redhat.com> >> --- >> arch/arm64/kvm/sdei.c | 29 +++++++++++++++++++++++++++++ >> 1 file changed, 29 insertions(+) >> >> diff --git a/arch/arm64/kvm/sdei.c b/arch/arm64/kvm/sdei.c >> index 3fb33258b494..62efee2b67b8 100644 >> --- a/arch/arm64/kvm/sdei.c >> +++ b/arch/arm64/kvm/sdei.c >> @@ -582,6 +582,29 @@ static unsigned long kvm_sdei_hypercall_mask(struct kvm_vcpu *vcpu, >> return ret; >> } >> >> +static unsigned long kvm_sdei_hypercall_reset(struct kvm_vcpu *vcpu, >> + bool private) >> +{ >> + struct kvm *kvm = vcpu->kvm; >> + struct kvm_sdei_kvm *ksdei = kvm->arch.sdei; >> + struct kvm_sdei_vcpu *vsdei = vcpu->arch.sdei; >> + unsigned int mask = private ? (1 << SDEI_EVENT_TYPE_PRIVATE) : >> + (1 << SDEI_EVENT_TYPE_SHARED); >> + unsigned long ret = SDEI_SUCCESS; >> + >> + /* Sanity check */ >> + if (!(ksdei && vsdei)) { >> + ret = SDEI_NOT_SUPPORTED; >> + goto out; >> + } >> + >> + spin_lock(&ksdei->lock); >> + kvm_sdei_remove_kvm_events(kvm, mask, false); > With kvm_sdei_remove_kvm_events() implementation, why do you make sure > that events which have a running handler get unregistered once the > handler completes? I just see the refcount check that prevents the "KVM > event object" from being removed. Good point. I think here we need enhancement to cancel the pending events prior to destroying them. I will think about it :) >> + spin_unlock(&ksdei->lock); >> +out: >> + return ret; >> +} >> + >> int kvm_sdei_hypercall(struct kvm_vcpu *vcpu) >> { >> u32 func = smccc_get_function(vcpu); >> @@ -626,8 +649,14 @@ int kvm_sdei_hypercall(struct kvm_vcpu *vcpu) >> break; >> case SDEI_1_0_FN_SDEI_INTERRUPT_BIND: >> case SDEI_1_0_FN_SDEI_INTERRUPT_RELEASE: >> + ret = SDEI_NOT_SUPPORTED; >> + break; >> case SDEI_1_0_FN_SDEI_PRIVATE_RESET: >> + ret = kvm_sdei_hypercall_reset(vcpu, true); >> + break; >> case SDEI_1_0_FN_SDEI_SHARED_RESET: >> + ret = kvm_sdei_hypercall_reset(vcpu, false); >> + break; >> default: >> ret = SDEI_NOT_SUPPORTED; >> } >> Thanks, Gavin
WARNING: multiple messages have this Message-ID (diff)
From: Gavin Shan <gshan@redhat.com> To: Eric Auger <eauger@redhat.com>, kvmarm@lists.cs.columbia.edu Cc: maz@kernel.org, pbonzini@redhat.com, will@kernel.org, linux-kernel@vger.kernel.org, Jonathan.Cameron@huawei.com Subject: Re: [PATCH v4 12/21] KVM: arm64: Support SDEI_{PRIVATE, SHARED}_RESET hypercall Date: Wed, 12 Jan 2022 11:01:21 +0800 [thread overview] Message-ID: <d163631c-6e66-f7a1-6eea-3bc000e771ca@redhat.com> (raw) In-Reply-To: <a4b91fa5-12b0-afeb-4449-c2acb59e8cd7@redhat.com> Hi Eric, On 11/10/21 4:37 AM, Eric Auger wrote: > On 8/15/21 2:13 AM, Gavin Shan wrote: >> This supports SDEI_{PRIVATE, SHARED}_RESET. They are used by the >> guest to purge the private or shared SDEI events, which are registered > to reset all private SDEI event registrations of the calling PE (resp. > PRIVATE or SHARED) Ok. >> previously. >> >> Signed-off-by: Gavin Shan <gshan@redhat.com> >> --- >> arch/arm64/kvm/sdei.c | 29 +++++++++++++++++++++++++++++ >> 1 file changed, 29 insertions(+) >> >> diff --git a/arch/arm64/kvm/sdei.c b/arch/arm64/kvm/sdei.c >> index 3fb33258b494..62efee2b67b8 100644 >> --- a/arch/arm64/kvm/sdei.c >> +++ b/arch/arm64/kvm/sdei.c >> @@ -582,6 +582,29 @@ static unsigned long kvm_sdei_hypercall_mask(struct kvm_vcpu *vcpu, >> return ret; >> } >> >> +static unsigned long kvm_sdei_hypercall_reset(struct kvm_vcpu *vcpu, >> + bool private) >> +{ >> + struct kvm *kvm = vcpu->kvm; >> + struct kvm_sdei_kvm *ksdei = kvm->arch.sdei; >> + struct kvm_sdei_vcpu *vsdei = vcpu->arch.sdei; >> + unsigned int mask = private ? (1 << SDEI_EVENT_TYPE_PRIVATE) : >> + (1 << SDEI_EVENT_TYPE_SHARED); >> + unsigned long ret = SDEI_SUCCESS; >> + >> + /* Sanity check */ >> + if (!(ksdei && vsdei)) { >> + ret = SDEI_NOT_SUPPORTED; >> + goto out; >> + } >> + >> + spin_lock(&ksdei->lock); >> + kvm_sdei_remove_kvm_events(kvm, mask, false); > With kvm_sdei_remove_kvm_events() implementation, why do you make sure > that events which have a running handler get unregistered once the > handler completes? I just see the refcount check that prevents the "KVM > event object" from being removed. Good point. I think here we need enhancement to cancel the pending events prior to destroying them. I will think about it :) >> + spin_unlock(&ksdei->lock); >> +out: >> + return ret; >> +} >> + >> int kvm_sdei_hypercall(struct kvm_vcpu *vcpu) >> { >> u32 func = smccc_get_function(vcpu); >> @@ -626,8 +649,14 @@ int kvm_sdei_hypercall(struct kvm_vcpu *vcpu) >> break; >> case SDEI_1_0_FN_SDEI_INTERRUPT_BIND: >> case SDEI_1_0_FN_SDEI_INTERRUPT_RELEASE: >> + ret = SDEI_NOT_SUPPORTED; >> + break; >> case SDEI_1_0_FN_SDEI_PRIVATE_RESET: >> + ret = kvm_sdei_hypercall_reset(vcpu, true); >> + break; >> case SDEI_1_0_FN_SDEI_SHARED_RESET: >> + ret = kvm_sdei_hypercall_reset(vcpu, false); >> + break; >> default: >> ret = SDEI_NOT_SUPPORTED; >> } >> Thanks, Gavin _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2022-01-12 3:01 UTC|newest] Thread overview: 158+ 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 ` Gavin Shan 2021-08-15 0:13 ` [PATCH v4 01/21] KVM: arm64: Introduce template for inline functions Gavin Shan 2021-08-15 0:13 ` Gavin Shan 2021-11-09 15:26 ` Eric Auger 2021-11-09 15:26 ` Eric Auger 2022-01-11 7:52 ` Gavin Shan 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-08-15 0:13 ` Gavin Shan 2021-11-09 15:45 ` Eric Auger 2021-11-09 15:45 ` Eric Auger 2022-01-11 9:20 ` Gavin Shan 2022-01-11 9:20 ` Gavin Shan 2022-01-27 13:17 ` Eric Auger 2022-01-27 13:17 ` Eric Auger 2022-01-11 9:40 ` Shannon Zhao 2022-01-11 9:40 ` Shannon Zhao 2022-01-13 7:09 ` Gavin Shan 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-08-15 0:13 ` Gavin Shan 2021-11-09 15:26 ` Eric Auger 2021-11-09 15:26 ` Eric Auger 2022-01-11 9:25 ` Gavin Shan 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-08-15 0:13 ` Gavin Shan 2021-11-09 15:50 ` Eric Auger 2021-11-09 15:50 ` Eric Auger 2022-01-12 2:19 ` Gavin Shan 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-08-15 0:13 ` Gavin Shan 2021-11-09 16:02 ` Eric Auger 2021-11-09 16:02 ` Eric Auger 2022-01-12 2:29 ` Gavin Shan 2022-01-12 2:29 ` Gavin Shan 2022-01-25 18:23 ` Eric Auger 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-08-15 0:13 ` Gavin Shan 2021-11-10 11:16 ` Eric Auger 2021-11-10 11:16 ` Eric Auger 2022-01-12 2:33 ` Gavin Shan 2022-01-12 2:33 ` Gavin Shan 2022-01-25 18:29 ` Eric Auger 2022-01-25 18:29 ` Eric Auger 2022-01-11 9:43 ` Shannon Zhao 2022-01-11 9:43 ` Shannon Zhao 2022-01-13 7:02 ` Gavin Shan 2022-01-13 7:02 ` Gavin Shan 2022-01-13 7:13 ` Gavin Shan 2022-01-13 7:13 ` Gavin Shan 2022-01-25 18:32 ` Eric Auger 2022-01-25 18:32 ` Eric Auger 2022-01-25 18:31 ` 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-08-15 0:13 ` Gavin Shan 2021-11-09 17:05 ` Eric Auger 2021-11-09 17:05 ` Eric Auger 2022-01-12 2:38 ` Gavin Shan 2022-01-12 2:38 ` Gavin Shan 2022-01-25 18:42 ` Eric Auger 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-08-15 0:13 ` Gavin Shan 2021-11-09 17:12 ` Eric Auger 2021-11-09 17:12 ` Eric Auger 2022-01-12 2:40 ` Gavin Shan 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-08-15 0:13 ` Gavin Shan 2021-11-09 17:19 ` Eric Auger 2021-11-09 17:19 ` Eric Auger 2022-01-12 2:46 ` Gavin Shan 2022-01-12 2:46 ` Gavin Shan 2022-01-27 14:19 ` Eric Auger 2022-01-27 14:19 ` Eric Auger 2021-08-15 0:13 ` [PATCH v4 10/21] KVM: arm64: Support SDEI_EVENT_ROUTING_SET hypercall Gavin Shan 2021-08-15 0:13 ` Gavin Shan 2021-11-09 18:47 ` Eric Auger 2021-11-09 18:47 ` Eric Auger 2022-01-12 2:54 ` Gavin Shan 2022-01-12 2:54 ` Gavin Shan 2022-01-27 14:13 ` Eric Auger 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-08-15 0:13 ` Gavin Shan 2021-11-09 20:31 ` Eric Auger 2021-11-09 20:31 ` Eric Auger 2022-01-12 2:58 ` Gavin Shan 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-08-15 0:13 ` Gavin Shan 2021-11-09 20:37 ` Eric Auger 2021-11-09 20:37 ` Eric Auger 2022-01-12 3:01 ` Gavin Shan [this message] 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-08-15 0:13 ` Gavin Shan 2021-11-10 10:58 ` Eric Auger 2021-11-10 10:58 ` Eric Auger 2022-01-12 6:34 ` Gavin Shan 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-08-15 0:13 ` Gavin Shan 2021-11-10 10:58 ` Eric Auger 2021-11-10 10:58 ` Eric Auger 2022-01-12 6:43 ` Gavin Shan 2022-01-12 6:43 ` Gavin Shan 2022-01-27 14:47 ` Eric Auger 2022-01-27 14:47 ` Eric Auger 2022-01-27 15:20 ` 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-08-15 0:13 ` Gavin Shan 2021-11-10 11:35 ` Eric Auger 2021-11-10 11:35 ` Eric Auger 2022-01-12 6:48 ` Gavin Shan 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-08-15 0:13 ` Gavin Shan 2021-11-10 13:48 ` Eric Auger 2021-11-10 13:48 ` Eric Auger 2022-01-12 7:03 ` Gavin Shan 2022-01-12 7:03 ` Gavin Shan 2022-01-27 13:48 ` Eric Auger 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 ` Gavin Shan 2021-08-15 0:13 ` [PATCH v4 18/21] KVM: arm64: Support SDEI event injection Gavin Shan 2021-08-15 0:13 ` Gavin Shan 2021-11-10 14:05 ` Eric Auger 2021-11-10 14:05 ` Eric Auger 2022-01-12 7:12 ` Gavin Shan 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-08-15 0:13 ` Gavin Shan 2021-11-10 14:09 ` Eric Auger 2021-11-10 14:09 ` Eric Auger 2022-01-12 7:19 ` Gavin Shan 2022-01-12 7:19 ` Gavin Shan 2021-08-15 0:13 ` [PATCH v4 20/21] KVM: arm64: Export SDEI capability Gavin Shan 2021-08-15 0:13 ` Gavin Shan 2021-11-10 13:55 ` Eric Auger 2021-11-10 13:55 ` Eric Auger 2022-01-12 7:20 ` Gavin Shan 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:13 ` Gavin Shan 2021-08-15 0:19 ` [PATCH v4 00/21] Support SDEI Virtualization Gavin Shan 2021-08-15 0:19 ` Gavin Shan 2021-11-10 14:29 ` Eric Auger 2021-11-10 14:29 ` Eric Auger 2022-01-12 7:24 ` Gavin Shan 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=d163631c-6e66-f7a1-6eea-3bc000e771ca@redhat.com \ --to=gshan@redhat.com \ --cc=Jonathan.Cameron@huawei.com \ --cc=eauger@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.