From: "Huang, Kai" <kai.huang@intel.com>
To: "seanjc@google.com" <seanjc@google.com>
Cc: "aashish@aashishsharma.net" <aashish@aashishsharma.net>,
"Gao, Chao" <chao.gao@intel.com>,
"guang.zeng@intel.com" <guang.zeng@intel.com>,
"dmaluka@chromium.org" <dmaluka@chromium.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"vineeth@bitbyteword.org" <vineeth@bitbyteword.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jaszczyk@chromium.org" <jaszczyk@chromium.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"Dong, Chuanxiao" <chuanxiao.dong@intel.com>
Subject: Re: [PATCH] KVM: VMX: Postpone IPIv setup after successful vCPU creation
Date: Mon, 20 Jul 2026 23:22:20 +0000 [thread overview]
Message-ID: <ca2aef4bd776ca9613a5614e14974e6fc188dd7a.camel@intel.com> (raw)
In-Reply-To: <al6r-2sAm2tVh1Wn@google.com>
On Mon, 2026-07-20 at 16:15 -0700, Sean Christopherson wrote:
> My only
> concern is that we could consume a garbage @id if kvm_arch_vcpu_precreate()
> performs additional checks on @id, as x86's implementation does. However, I
> don't think that's a meaningful concern since kvm_vm_ioctl_create_vcpu() *must*
> perform at least basic sanity checks.
Agreed.
next prev parent reply other threads:[~2026-07-20 23:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 16:08 [PATCH] KVM: VMX: Postpone IPIv setup after successful vCPU creation Dmytro Maluka
2026-07-16 16:29 ` sashiko-bot
2026-07-16 17:24 ` Dmytro Maluka
2026-07-20 14:18 ` Naveen N Rao
2026-07-20 21:38 ` Sean Christopherson
2026-07-17 12:59 ` Huang, Kai
2026-07-17 16:20 ` Dmytro Maluka
2026-07-17 21:21 ` Huang, Kai
2026-07-20 22:17 ` Sean Christopherson
2026-07-20 23:10 ` Huang, Kai
2026-07-20 23:15 ` Sean Christopherson
2026-07-20 23:22 ` Huang, Kai [this message]
2026-07-21 9:26 ` Dmytro Maluka
2026-07-20 6:29 ` Chao Gao
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=ca2aef4bd776ca9613a5614e14974e6fc188dd7a.camel@intel.com \
--to=kai.huang@intel.com \
--cc=aashish@aashishsharma.net \
--cc=chao.gao@intel.com \
--cc=chuanxiao.dong@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dmaluka@chromium.org \
--cc=guang.zeng@intel.com \
--cc=jaszczyk@chromium.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vineeth@bitbyteword.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 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.