From: Sean Christopherson <seanjc@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Jim Mattson <jmattson@google.com>
Subject: Re: [PATCH 5.15.y] KVM: SVM: Mark VMCB_NPT as dirty on nested VMRUN
Date: Mon, 5 Jan 2026 12:27:20 -0800 [thread overview]
Message-ID: <aVweqPzM9j0xDcoe@google.com> (raw)
In-Reply-To: <20251231143917.3047237-1-sashal@kernel.org>
On Wed, Dec 31, 2025, Sasha Levin wrote:
> From: Jim Mattson <jmattson@google.com>
>
> [ Upstream commit 7c8b465a1c91f674655ea9cec5083744ec5f796a ]
>
> Mark the VMCB_NPT bit as dirty in nested_vmcb02_prepare_save()
> on every nested VMRUN.
>
> If L1 changes the PAT MSR between two VMRUN instructions on the same
> L1 vCPU, the g_pat field in the associated vmcb02 will change, and the
> VMCB_NPT clean bit should be cleared.
>
> Fixes: 4bb170a5430b ("KVM: nSVM: do not mark all VMCB02 fields dirty on nested vmexit")
> Cc: stable@vger.kernel.org
> Signed-off-by: Jim Mattson <jmattson@google.com>
> Link: https://lore.kernel.org/r/20250922162935.621409-3-jmattson@google.com
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> [ adapted vmcb02 local variable to svm->vmcb direct access pattern ]
FWIW, I double checked that vmcb02 is indeed guaranteed to be the active vmcb.
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
Acked-by: Sean Christopherson <seanjc@google.com>
prev parent reply other threads:[~2026-01-05 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 14:36 FAILED: patch "[PATCH] KVM: SVM: Mark VMCB_NPT as dirty on nested VMRUN" failed to apply to 5.15-stable tree gregkh
2025-12-31 14:39 ` [PATCH 5.15.y] KVM: SVM: Mark VMCB_NPT as dirty on nested VMRUN Sasha Levin
2026-01-05 20:27 ` Sean Christopherson [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=aVweqPzM9j0xDcoe@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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 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.