From: Jon Kohler <jon@nutanix.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jonathan Kohler <jonmkohler@gmail.com>,
Dongli Zhang <dongli.zhang@oracle.com>,
Chao Gao <chao.gao@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Gulshan Gabel <gulshan.gabel@nutanix.com>,
Prerna Saxena <prerna.saxena@nutanix.com>
Subject: Re: [PATCH 6.18.y] KVM: VMX: Update SVI during runtime APICv activation
Date: Sun, 14 Jun 2026 16:48:52 +0000 [thread overview]
Message-ID: <C091BC70-A13B-46F8-A732-BD060DFEB030@nutanix.com> (raw)
In-Reply-To: <20260613143000.0001-1-sashal@kernel.org>
> On Jun 13, 2026, at 10:51 AM, Sasha Levin <sashal@kernel.org> wrote:
>
> On Fri, Jun 12, 2026 at 02:10:01PM -0700, Jon Kohler wrote:
>> From: Dongli Zhang <dongli.zhang@oracle.com>
>>
>> commit b2849bec936be642b5420801f902337f2507648e upstream.
>
> Queued for 6.18.y, thanks. (And thanks Sean for the ack.)
>
> --
> Thanks,
> Sasha
Bringing a side thread back on list, Sasha is going to queue this
for 6.12.y as well because it applies cleanly there; however, it
does not apply cleanly to 6.6.y.
Gulshan (CC’d) did all the great investigation work on this (and
the commit msg narrative on my original email was all him!), so
he's going to pick up the 6.6.y backport here as we’ve already
backported/shipped that to our internal 6.6.y production branch,
so that should be straight forward.
Jon
prev parent reply other threads:[~2026-06-14 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 21:10 Jon Kohler
2026-06-12 23:58 ` Sean Christopherson
2026-06-13 14:51 ` Sasha Levin
2026-06-14 16:48 ` Jon Kohler [this message]
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=C091BC70-A13B-46F8-A732-BD060DFEB030@nutanix.com \
--to=jon@nutanix.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dongli.zhang@oracle.com \
--cc=gulshan.gabel@nutanix.com \
--cc=hpa@zytor.com \
--cc=jonmkohler@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=prerna.saxena@nutanix.com \
--cc=sashal@kernel.org \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®