From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-dy2-f42.google.com (mail-dy2-f42.google.com [74.125.229.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 03AE52F7EE4 for ; Tue, 29 Sep 2026 00:58:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=74.125.229.42 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790643489; cv=none; b=BffNbTf/2/2Grq+bHpkoC9iHlpSThMekoF0PpT2mWMQwPbxc2eMNFUrXCUaP1a1/vx/kgnnTwGJtvWcpYA5+6z3Au30sddJwmSKX/4JvwIjI7kwLP8PpeOdOvt1uFXF6oQg5LGz8zVA2LL2CSi/wor6MojbovRpyizH14gVGykw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790643489; c=relaxed/simple; bh=K6rejY1PiyjrRi5fjv/FpvD2GeFIOd/rznJ4sRh5qGc=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=NGmiTl5GvwlHYIkME49/sE2NlF4cHbbf6MHQST8YylaurKQTaL65uRvf0x+fva1Eh5sAiSYVks2Tqxns0C2hg99Rat7TjpltY/UkB1GV6NlGADxl0NpjET2AdmCa8fwiKstNyDBL73971sjFFkxck+q0p+ti7oqoS3V2Yrk1giY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=mFwcXpPb; arc=none smtp.client-ip=74.125.229.42 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="mFwcXpPb" Received: by mail-dy2-f42.google.com with SMTP id 5a478bee46e88-3428f70d7e7so2100876eec.3 for ; Mon, 28 Sep 2026 17:58:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1790643487; x=1791248287; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to:content-type; bh=E22AfzmQFmy3baYsl/FqRMEYfQ92PfmP91jOLK3cr5Q=; b=mFwcXpPbdcJbZCdCtA97yvmNWXETu05Y05f1k1U2ejJwZItKgnWvdgfm7gQ5YncbVu 8DmtBbGew4JUYADXJ3KYuWiWKS3yDnJdtb52IhOiBVS/8N2YOPe/ZKWnEjoXzmDFe54R XZNtEM5u7qys3FlcTzvy2akkyDGccWzUvMLpV4XFXEJDO6aVvsEwwUXiaWITZh6jSxUr PBgP8BLxJPQ0ftDNdl+SO4tPR8t6pqvgt/2aFTJXQixwBYC0sK/dDwz85T8qHS2aGDe2 5l8NykwxZy1zZEu12PUkoatMuxbla1wHa58I2hj+CxRuvUES0MuGjkQLs+gIsGmIt0Q2 FrQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1790643487; x=1791248287; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to:content-type; bh=E22AfzmQFmy3baYsl/FqRMEYfQ92PfmP91jOLK3cr5Q=; b=wROgx83SZPQdqiV0Gp3NgMvz0i+ICXG1lBCLJjJavOpgMVT4MapsIQxg0KN2a11fRN v/zSePHZnFU/14NyAdGjkR2bsoyQ9Y/4vlvhNj/I+Rwo4YMhHofzxl1keUBgyep+0eLV rJTM0csbRI/nIb0MD8COZ9sN3+OdYYSTULKpaym2zAEseUqi8friA/ukhz8qniz7Aw8e 3aN+mhTUPf+o/ps+JLcbfwqMu8mXaSmxu/6cQdDpUePbtZPCydWMpcpzbcVbrwaBmLKq JsfEbJKdtEmKO3fDt662YZZ7d9al4MbVDy4EmJvz8E5Tg6q2pKIH1feoLHwBQvVCMVad FDuQ== X-Forwarded-Encrypted: i=1; AKwUvBy2fjls4no4LK04WLVgNDp9Mw6BGIAdvJzZx6EyFEdWIjUacTz4BgzOS3uRO6JhisquDoU=@vger.kernel.org X-Gm-Message-State: AFuF++lIx/luDyh+97AAEBjNdj0tTUw5Y7n8o/MfUafrja+iQszuTAC5 6OiNv7VIpLiYxTngWzkSYPEbCKQoKn4yiJftKPDUS6aPItMPBa4/Gxp6 X-Gm-Gg: AYBFou1tamm4v+FBFcRfRH+wbLa2oEOPDWgr7PZtJ9/dQVub4MpWplpVm3Ep4RERdsu h9JG8w8fh1JhMJs2PTcKDrEZ55KKHG9gbo9Em6n2Kg9nChYaq2q3CNMbpn60+qzxR5HpDRbkxnz sKb0PHZkti6ovDkmFU0iFmWFDh4kYi2HshpXis0c+tvXVzod8d+RzCcGXeJ0VofYNJ2nqzgau3s E5eeuj4iSyqCC5AOu2Jaxfnnb2y9ma6Vl/w8kQtNtB46+pHN7Xdlw24CH1Iu8G9joha0P21IG9x zS9VH4JdrZdNeAEwr3uz8NnrjahfHMqztqWVK87+c8dBZzDl8Zc7wLPdaaKjDlU4LSob/futpKy zEW3m2bMVSaAsyzm4ePeq1QtWckyG4U1DnlNZ6u19GOE7XPdqKEbwsgBPvgG/Xj64z+qOfq0HQt q5zOb3JXQVAZqZ9WrzMXTnty+yAjjuBzv46hpq1IHr1wObLcSXa00DeDfzsLB6et5YqskXswiX+ nM= X-Received: by 2002:a05:701b:231b:b0:14a:5284:1bf7 with SMTP id a92af1059eb24-14a52841df9mr3805513c88.14.1790643486645; Mon, 28 Sep 2026 17:58:06 -0700 (PDT) Received: from wujing.localdomain ([23.254.208.9]) by smtp.gmail.com with ESMTPSA id a92af1059eb24-145aa0cb6b9sm25673546c88.1.2026.09.28.17.58.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Sep 2026 17:58:06 -0700 (PDT) From: Qiliang Yuan To: Wei Liu Cc: Qiliang Yuan , Sean Christopherson , Paolo Bonzini , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Vitaly Kuznetsov , "K. Y. Srinivasan" , Haiyang Zhang , Dexuan Cui , Long Li , 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 Message-ID: <20260929005755.64126-1-odys.yuan@gmail.com> X-Mailer: git-send-email 2.53.0 In-Reply-To: References: <20260928-kvm-smm-cr3-upper-bits-v1-1-138f52dd531e@gmail.com> <20260928072534.1987-1-odys.yuan@gmail.com> <20260928174243.GA3705413@liuwe-devbox-debian-v2.local> Precedence: bulk X-Mailing-List: kvm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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