From: Naveen N Rao <naveen@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Xiao Wu <xiaowu.417@qq.com>
Subject: Re: [PATCH v2 1/3] KVM: SVM: Make kvm_x86_ops.vcpu_precreate() hook fully AVIC specific
Date: Fri, 3 Jul 2026 21:55:16 +0530 [thread overview]
Message-ID: <akfiPEKZguDXPs6I@blrnaveerao1> (raw)
In-Reply-To: <20260630210156.457151-2-seanjc@google.com>
On Tue, Jun 30, 2026 at 02:01:54PM -0700, Sean Christopherson wrote:
> In anticipation of deferring all per-VM AVIC initialization until a vCPU
> is first created, move SVM's kvm_x86_ops.vcpu_precreate() hook into avic.c
> as avic_vcpu_pre_create() and nullify the hook if AVIC is disabled (and
^^^^^^^^^^^^^^^^^^^^ avic_vcpu_precreate()
> WARN if the hook is somehow invoked without AVIC enabled).
>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> arch/x86/kvm/svm/avic.c | 13 +++++++++----
> arch/x86/kvm/svm/svm.c | 8 ++------
> arch/x86/kvm/svm/svm.h | 2 +-
> 3 files changed, 12 insertions(+), 11 deletions(-)
Reviewed-by: Naveen N Rao (AMD) <naveen@kernel.org>
- Naveen
next prev parent reply other threads:[~2026-07-03 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 21:01 [PATCH v2 0/3] KVM: SVM: Fix a (very) unlikely UAF for GA Log IRQs Sean Christopherson
2026-06-30 21:01 ` [PATCH v2 1/3] KVM: SVM: Make kvm_x86_ops.vcpu_precreate() hook fully AVIC specific Sean Christopherson
2026-07-03 16:25 ` Naveen N Rao [this message]
2026-06-30 21:01 ` [PATCH v2 2/3] KVM: SVM: Do all per-VM AVIC initialization during vCPU precreation phase Sean Christopherson
2026-07-03 17:14 ` Naveen N Rao
2026-06-30 21:01 ` [PATCH v2 3/3] KVM: SVM: Remove VM from the GA Log notifier list before VM destruction Sean Christopherson
2026-07-03 17:21 ` Naveen N Rao
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=akfiPEKZguDXPs6I@blrnaveerao1 \
--to=naveen@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=xiaowu.417@qq.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