From: Eric Auger <eauger@redhat.com>
To: Gavin Shan <gshan@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 18/21] KVM: arm64: Support SDEI event injection
Date: Wed, 10 Nov 2021 15:05:34 +0100 [thread overview]
Message-ID: <6c11ed83-796e-765e-bb6a-116947d33eab@redhat.com> (raw)
In-Reply-To: <20210815001352.81927-19-gshan@redhat.com>
On 8/15/21 2:13 AM, Gavin Shan wrote:
> This supports SDEI event injection by implementing kvm_sdei_inject().
> It's called by kernel directly or VMM through ioctl command to inject
> SDEI event to the specific vCPU.
>
> Signed-off-by: Gavin Shan <gshan@redhat.com>
> ---
> arch/arm64/include/asm/kvm_sdei.h | 2 +
> arch/arm64/include/uapi/asm/kvm_sdei.h | 1 +
> arch/arm64/kvm/sdei.c | 108 +++++++++++++++++++++++++
> 3 files changed, 111 insertions(+)
>
> diff --git a/arch/arm64/include/asm/kvm_sdei.h b/arch/arm64/include/asm/kvm_sdei.h
> index a997989bab77..51087fe971ba 100644
> --- a/arch/arm64/include/asm/kvm_sdei.h
> +++ b/arch/arm64/include/asm/kvm_sdei.h
> @@ -124,6 +124,8 @@ void kvm_sdei_create_vcpu(struct kvm_vcpu *vcpu);
> int kvm_sdei_hypercall(struct kvm_vcpu *vcpu);
> int kvm_sdei_register_notifier(struct kvm *kvm, unsigned long num,
> kvm_sdei_notifier notifier);
> +int kvm_sdei_inject(struct kvm_vcpu *vcpu,
> + unsigned long num, bool immediate);
> void kvm_sdei_deliver(struct kvm_vcpu *vcpu);
> long kvm_sdei_vm_ioctl(struct kvm *kvm, unsigned long arg);
> long kvm_sdei_vcpu_ioctl(struct kvm_vcpu *vcpu, unsigned long arg);
> diff --git a/arch/arm64/include/uapi/asm/kvm_sdei.h b/arch/arm64/include/uapi/asm/kvm_sdei.h
> index b916c3435646..f7a6b2b22b50 100644
> --- a/arch/arm64/include/uapi/asm/kvm_sdei.h
> +++ b/arch/arm64/include/uapi/asm/kvm_sdei.h
> @@ -67,6 +67,7 @@ struct kvm_sdei_vcpu_state {
> #define KVM_SDEI_CMD_SET_VEVENT 7
> #define KVM_SDEI_CMD_GET_VCPU_STATE 8
> #define KVM_SDEI_CMD_SET_VCPU_STATE 9
> +#define KVM_SDEI_CMD_INJECT_EVENT 10
>
> struct kvm_sdei_cmd {
> __u32 cmd;
> diff --git a/arch/arm64/kvm/sdei.c b/arch/arm64/kvm/sdei.c
> index 79315b77f24b..7c2789cd1421 100644
> --- a/arch/arm64/kvm/sdei.c
> +++ b/arch/arm64/kvm/sdei.c
> @@ -802,6 +802,111 @@ int kvm_sdei_register_notifier(struct kvm *kvm,
> return ret;
> }
>
> +int kvm_sdei_inject(struct kvm_vcpu *vcpu,
> + unsigned long num,
> + bool immediate)
don't get the immediate param.
> +{
> + 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;
> + struct kvm_sdei_vcpu_event *ksve = NULL;
> + int index, ret = 0;
> +
> + /* Sanity check */
> + if (!(ksdei && vsdei)) {
> + ret = -EPERM;
> + goto out;
> + }
> +
> + if (!kvm_sdei_is_valid_event_num(num)) {
> + ret = -EINVAL;
> + goto out;
> + }
> +
> + /* Check the kvm event */
> + spin_lock(&ksdei->lock);
> + kske = kvm_sdei_find_kvm_event(kvm, num);
> + if (!kske) {
> + ret = -ENOENT;
> + goto unlock_kvm;
> + }
> +
> + kse = kske->kse;
> + index = (kse->state.type == SDEI_EVENT_TYPE_PRIVATE) ?
> + vcpu->vcpu_idx : 0;
> + if (!(kvm_sdei_is_registered(kske, index) &&
> + kvm_sdei_is_enabled(kske, index))) {
> + ret = -EPERM;
> + goto unlock_kvm;
> + }
> +
> + /* Check the vcpu state */
> + spin_lock(&vsdei->lock);
> + if (vsdei->state.masked) {
> + ret = -EPERM;
> + goto unlock_vcpu;
> + }
> +
> + /* Check if the event can be delivered immediately */
> + if (immediate) {
According to the dispatcher pseudo code this should be always checked?
> + if (kse->state.priority == SDEI_EVENT_PRIORITY_CRITICAL &&
> + !list_empty(&vsdei->critical_events)) {
> + ret = -ENOSPC;
> + goto unlock_vcpu;
> + }
> +
> + if (kse->state.priority == SDEI_EVENT_PRIORITY_NORMAL &&
> + (!list_empty(&vsdei->critical_events) ||
> + !list_empty(&vsdei->normal_events))) {
> + ret = -ENOSPC;
> + goto unlock_vcpu;
> + }
> + }
What about shared event dispatching. I don't see the afficinity checked
anywhere?
> +
> + /* Check if the vcpu event exists */
> + ksve = kvm_sdei_find_vcpu_event(vcpu, num);
> + if (ksve) {
> + kske->state.refcount++;
> + ksve->state.refcount++;
why this double refcount increment??
> + kvm_make_request(KVM_REQ_SDEI, vcpu);
> + goto unlock_vcpu;
> + }
> +
> + /* Allocate vcpu event */
> + ksve = kzalloc(sizeof(*ksve), GFP_KERNEL);
> + if (!ksve) {
> + ret = -ENOMEM;
> + goto unlock_vcpu;
> + }
> +
> + /*
> + * We should take lock to update KVM event state because its
> + * reference count might be zero. In that case, the KVM event
> + * could be destroyed.
> + */
> + kske->state.refcount++;
> + ksve->state.num = num;
> + ksve->state.refcount = 1;
> + ksve->kske = kske;
> + ksve->vcpu = vcpu;
> +
> + if (kse->state.priority == SDEI_EVENT_PRIORITY_CRITICAL)
> + list_add_tail(&ksve->link, &vsdei->critical_events);
> + else
> + list_add_tail(&ksve->link, &vsdei->normal_events);
> +
> + kvm_make_request(KVM_REQ_SDEI, vcpu);
> +
> +unlock_vcpu:
> + spin_unlock(&vsdei->lock);
> +unlock_kvm:
> + spin_unlock(&ksdei->lock);
> +out:
> + return ret;
> +}
> +
> void kvm_sdei_deliver(struct kvm_vcpu *vcpu)
> {
> struct kvm *kvm = vcpu->kvm;
> @@ -1317,6 +1422,9 @@ long kvm_sdei_vcpu_ioctl(struct kvm_vcpu *vcpu, unsigned long arg)
> case KVM_SDEI_CMD_SET_VCPU_STATE:
> ret = kvm_sdei_set_vcpu_state(vcpu, &cmd->ksv_state);
> break;
> + case KVM_SDEI_CMD_INJECT_EVENT:
> + ret = kvm_sdei_inject(vcpu, cmd->num, false);
> + break;
> default:
> ret = -EINVAL;
> }
>
Eric
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2021-11-10 14:05 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
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 [this message]
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=6c11ed83-796e-765e-bb6a-116947d33eab@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