From: Qiliang Yuan <odys.yuan@gmail.com>
To: Wei Liu <wei.liu@kernel.org>
Cc: Qiliang Yuan <odys.yuan@gmail.com>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Vitaly Kuznetsov <vkuznets@redhat.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Dexuan Cui <decui@microsoft.com>, Long Li <longli@microsoft.com>,
linux-hyperv@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Clear CR3[63:32] on SMM entry from long mode
Date: Tue, 29 Sep 2026 08:57:55 +0800 [thread overview]
Message-ID: <20260929005755.64126-1-odys.yuan@gmail.com> (raw)
In-Reply-To: <arqvqW7g72AnVsLK@google.com>
On Mon, Sep 28, 2026 at 10:42:43AM -0700, Wei Liu wrote:
> Please share the Windows version from `winver`.
>
> My colleague said that it had been fixed. Maybe the change needs to be ported.
Windows 11 Pro, version 25H2, OS build 26200.9457, with WSL 2.9.3.0.
The host CPU is an AMD Ryzen 9 7940HX.
This machine is fully up to date through Windows Update, and the failure
reproduces on this build, so the fix does not seem to have reached the
released builds yet. Which build or channel (e.g. Insider) carries it?
I am happy to test it.
I have also filed it as a WSL issue, with repro steps and the SMRAM
analysis: https://github.com/microsoft/WSL/issues/41709
On Mon, Sep 28, 2026 at 11:19:21AM -0700, Sean Christopherson wrote:
> Ya, I'd much prefer to get this fixed in Hyper-V. If we need to carry a KVM hack,
> then at the very least it should be limited to when KVM detects that it's running
> on Hyper-V.
Understood, a Hyper-V fix is the right answer. Since current released
builds are affected, I can send a v2 that applies the workaround only
when KVM is running on Hyper-V, if you'd take that in the meantime.
Otherwise I'll drop this and wait for the Hyper-V fix to ship.
Thanks,
Qiliang
next prev parent reply other threads:[~2026-09-29 0:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 7:05 Qiliang Yuan
2026-09-28 7:25 ` Qiliang Yuan
2026-09-28 17:42 ` Wei Liu
2026-09-28 18:19 ` Sean Christopherson
2026-09-29 0:57 ` Qiliang Yuan [this message]
2026-09-30 1:42 ` Wei Liu
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=20260929005755.64126-1-odys.yuan@gmail.com \
--to=odys.yuan@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@kernel.org \
--cc=vkuznets@redhat.com \
--cc=wei.liu@kernel.org \
--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®