public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Melody Wang <huibo.wang@amd.com>
To: Joerg Rodel <joro@8bytes.org>
Cc: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Tom Lendacky <thomas.lendacky@amd.com>,
	kvm@vger.kernel.org
Subject: Re: [PATCH v4 3/7] KVM: SVM: Inject #HV when Restricted Injection is active
Date: Tue, 28 Apr 2026 10:58:45 -0700	[thread overview]
Message-ID: <c90bd541-a54d-478c-b618-226696679f4b@amd.com> (raw)
In-Reply-To: <7sewxapo7kapbfxw463crzltkojmylmlldtqxdzhaf4bnhecz5@vzn2nemcgqak>

Hi Joerg,

On 4/28/26 4:12 AM, Joerg Rodel wrote:
> On Fri, Apr 24, 2026 at 05:42:07PM +0000, Melody Wang wrote:
>> +void sev_snp_cancel_injection(struct kvm_vcpu *vcpu)
>> +{
>> +	struct vcpu_svm *svm = to_svm(vcpu);
>> +	struct kvm_host_map hvdb_map;
>> +	struct hvdb *hvdb;
>> +
>> +	if (!sev_snp_is_rinj_active(vcpu))
>> +		return;
>> +
>> +	if (!svm->vmcb->control.event_inj)
>> +		return;
>> +
>> +	if (WARN_ONCE((svm->vmcb->control.event_inj & SVM_EVTINJ_VEC_MASK) != HV_VECTOR,
>> +			"Restricted Injection enabled,  %u vector not supported\n",
>> +			svm->vmcb->control.event_inj & SVM_EVTINJ_VEC_MASK))
>> +		return;
>> +
>> +	/*
>> +	 * Copy the information in the doorbell page into the event injection
>> +	 * fields to complete the cancellation flow.
>> +	 */
>> +	hvdb = map_hvdb(vcpu, &hvdb_map);
>> +	if (!hvdb)
>> +		return;
>> +
>> +	if (!hvdb->events.pending_events) {
>> +		/* No pending events, then event_inj field should be 0 */
>> +		WARN_ON_ONCE(svm->vmcb->control.event_inj);
>> +		goto out;
>> +	}
>> +
>> +	/* Copy info back into event_inj field (replaces #HV) */
>> +	svm->vmcb->control.event_inj = SVM_EVTINJ_VALID;
>> +
>> +	if (hvdb->events.vector)
>> +		svm->vmcb->control.event_inj |= hvdb->events.vector |
>> +						SVM_EVTINJ_TYPE_INTR;
>> +
>> +	hvdb->events.pending_events = 0;
> 
> Does this also need to clear no_further_signal?

Yes, the no_further_signal is a bit in pending_events so it is getting 
cleared already. :)

Thanks,
Melody
> 
> -Joerg

-- 
Thanks,
Melody


  reply	other threads:[~2026-04-28 17:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24 17:42 [PATCH v4 0/7] Add SEV-SNP restricted injection hypervisor support Melody Wang
2026-04-24 17:42 ` [PATCH v4 1/7] x86/sev: Define the #HV doorbell page structure Melody Wang
2026-04-24 17:42 ` [PATCH v4 2/7] KVM: SVM: Add support for the SEV-SNP #HV doorbell page NAE event Melody Wang
2026-04-24 17:42 ` [PATCH v4 3/7] KVM: SVM: Inject #HV when Restricted Injection is active Melody Wang
2026-04-28 11:12   ` Joerg Rodel
2026-04-28 17:58     ` Melody Wang [this message]
2026-04-28 19:17   ` Tom Lendacky
2026-04-24 17:42 ` [PATCH v4 4/7] KVM: SVM: Inject NMIs " Melody Wang
2026-04-24 17:42 ` [PATCH v4 5/7] KVM: SVM: Inject MCEs " Melody Wang
2026-04-28 10:50   ` Joerg Rodel
2026-04-28 18:19     ` Melody Wang
2026-04-28 19:24   ` Tom Lendacky
2026-04-28 23:00     ` Melody Wang
2026-04-24 17:50 ` [PATCH 6/7] KVM: SVM: Add support for the SEV-SNP #HV IPI NAE event Melody Wang
2026-04-24 17:51 ` [PATCH v4 7/7] KVM: SVM: Enable Restricted Injection for an SEV-SNP guest Melody Wang
2026-04-28 10:52   ` Joerg Rodel
2026-04-28 18:25     ` Melody Wang

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=c90bd541-a54d-478c-b618-226696679f4b@amd.com \
    --to=huibo.wang@amd.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=thomas.lendacky@amd.com \
    --cc=x86@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