From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 45E201C84D0 for ; Tue, 2 Dec 2025 12:02:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764676981; cv=none; b=Y8gYUNFIOP6454m2+I9n1NNZBQFraJ06M/hO3un7D4OuIQZbTF3KmNoZyXMqbOzkl06ct10l1rz59JJRnVk3gEOIlc5Kk2UqD6vER7kNKsIeH5ZLer2Uh6lj8rvYJ1pKp17aytXWvftfHCu2+4TU0dNA7YbNcbpxKBIcbIsExgc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764676981; c=relaxed/simple; bh=/KPEMqnDEiAGSaN5O+8OYfieXumAwbKpkHyzDT2lSxo=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=RZOMEincguEWnZVFZzBQWhKw9Q1wPXf/5PKNjuCM2A1GEbXX1Dlvq9jD1zUTiuwAgmrjxUJxeSUnoIoESU8ODJUp5MWOei8qF2byU6gw1dUL5WHROu08e5DK4GXJAt/XhDfqSIgoHkmHk2pidmA329aSCDKqd9sBTkoxTaRB0e0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=VMsfDtHW; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b=RBkC4VRd; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="VMsfDtHW"; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b="RBkC4VRd" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1764676978; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GGyHUUPhdZ5uvSSHXO1KoXFKVeTdFZEjpoTb5RrxTK4=; b=VMsfDtHWFJxEfn+PQjLYKIyeWSQB57ExwOKKmr9p/Xdw3143qk6y19tY2OV/wHV4Jx9gwc UvCb9ux8BNyfh4/7D6N++AesapLlgiraJ0SHVSrg4MUYapRLwjjltj/BnNQwbE73prNEbc nR15JMaG4ZNp7YiLBAehXY8dkHFF1kY= Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-42-gqMSk7QhMYC-336C6vaenQ-1; Tue, 02 Dec 2025 07:02:56 -0500 X-MC-Unique: gqMSk7QhMYC-336C6vaenQ-1 X-Mimecast-MFC-AGG-ID: gqMSk7QhMYC-336C6vaenQ_1764676974 Received: by mail-ed1-f71.google.com with SMTP id 4fb4d7f45d1cf-6450e804cd9so5074270a12.3 for ; Tue, 02 Dec 2025 04:02:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=google; t=1764676974; x=1765281774; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=GGyHUUPhdZ5uvSSHXO1KoXFKVeTdFZEjpoTb5RrxTK4=; b=RBkC4VRdmgj9rgElWXyYlhuqSDf2W3dpKzD2sLh5wYCNARbAZBA2OBMDJSoDRY3UVf A2q+TvFQItX+4ABs4v833HxQLMsX+TKJLRqM0tmPFkHCoo5idoVU+UWWMlX9ixZCmtd7 C9PzT5MtOOKqdLRHOQKfh0jT6FUW0ZmMYpseEvrqpXwyru1wk8ndgSkk4Y4PkeuThQ/8 PQ5sujFr61XsP4gl4qGODKObEcuhP43Xp6ns62IkNMGcEPgvHVl+ZvqRTlewBQyKKx9+ z6uULVPlh/gUrmMZVrPEwl5StYBt8+3sFMdHA+lzahmBVW5PWB/cKU8engrlnIQqORcW OHOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764676974; x=1765281774; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=GGyHUUPhdZ5uvSSHXO1KoXFKVeTdFZEjpoTb5RrxTK4=; b=hHcvjPcI0cHvLQlm6+qA2Jadn6odO+1nUIWHW++lF8PWR6PhSIVZjdGBS34tNRFaNt tzVo20xKI3yB4N0v+F9b36x8tp25sxIFQJlOpkpE6ebaTWw+5c787A0qwvDWWppFdYQ0 5n6S1rY1WPbFR2ZZkuVG4B0QZgLmbqWhnrkE8+dH7uABqeJUyV7dAg1HM+TaIBtd5umG 6WsEDyQs9o0evF8T1v+HNAYWsM165TSZznDO2712g1SBhlsi5JC+cf4GlMwcAJdsDsfl RUfEz15RRyfhczPhmW6LbgZUZd5JdN1y6z+xF38FtswwzA/Y4+/Lw51sqQy9gdIP7C/V zPsA== X-Forwarded-Encrypted: i=1; AJvYcCVo/JLPPeebOMru+tPqKDxFBy3dKQ/59xlOoVdfQesCROK/DAftoSTnFL7s5smYSEM7Y2SoKAAwU1uxobU=@vger.kernel.org X-Gm-Message-State: AOJu0YzOO9P63JbmIKirMcZF6cyH8G+cIj0JiS5lnXMk6rQ3D7VQ9mxE 5voKOXHczZKumrOOBhG2K1ZtdMgrwxPaoflC3wfAY0MX5aghb/L1g2QZij1bkaVgkhDFWFj7dzG F593h07zlHazV7ojjqS2NOT7DNU2vQrHwCziW8E5jfTDz4kIVXHAIDq1ZbrKecD3sSA== X-Gm-Gg: ASbGncsgp22rOKzSNJ0GtF+MPy0/8SH1Ln2k8xQMP9w8FIen1hFH7OT9ImhDRjGuwFM BBSLiSvjX8nkPqxlgdj957Q1xXa7DJyXKzBqAYYx+p0mxtM8/TzJ0GE+fVZeg7a+I4s/FtwElmb QLt7SyxRqW0xNb0Q16xIvfT6JcsV9JLpUpOMx1Ud2MaFQ/oh73iukGfC9la3e+fpS6K+KcjBrMI Nin1iAngYltGNlKLCqjY7H60D95W1s+W+ez41vfq7HfcDmPC2N1IzQIEOneJz4xaPNoFcTxJcm4 S0X61TcAZ5R9xW/3SfzwCQmlcgwUmHoMOuyseHQP5RHD8bIKwqu/P+7sp8DL0Aglzndy2g== X-Received: by 2002:a05:6402:2116:b0:640:bd21:242f with SMTP id 4fb4d7f45d1cf-64554442222mr37519692a12.1.1764676974125; Tue, 02 Dec 2025 04:02:54 -0800 (PST) X-Google-Smtp-Source: AGHT+IFIxXTIn/JqfgO673hNmcnsCE5++mQ0b34IFuJh1hndg1oxOZzpSsOjIje7OERrDqbfDJ8rcw== X-Received: by 2002:a05:6402:2116:b0:640:bd21:242f with SMTP id 4fb4d7f45d1cf-64554442222mr37519668a12.1.1764676973652; Tue, 02 Dec 2025 04:02:53 -0800 (PST) Received: from imammedo ([213.175.46.86]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-64751061e14sm17134647a12.31.2025.12.02.04.02.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 02 Dec 2025 04:02:52 -0800 (PST) Date: Tue, 2 Dec 2025 13:02:52 +0100 From: Igor Mammedov To: Sean Christopherson Cc: Paolo Bonzini , kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] KVM: x86: Apply runtime updates to current CPUID during KVM_SET_CPUID{,2} Message-ID: <20251202130252.1f799692@imammedo> In-Reply-To: <20251202015049.1167490-2-seanjc@google.com> References: <20251202015049.1167490-1-seanjc@google.com> <20251202015049.1167490-2-seanjc@google.com> X-Mailer: Claws Mail 4.3.1 (GTK 3.24.51; x86_64-redhat-linux-gnu) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 1 Dec 2025 17:50:48 -0800 Sean Christopherson wrote: > When handling KVM_SET_CPUID{,2}, do runtime CPUID updates on the vCPU's > current CPUID (and caps) prior to swapping in the incoming CPUID state so > that KVM doesn't lose pending updates if the incoming CPUID is rejected, > and to prevent a false failure on the equality check. > > Note, runtime updates are unconditionally performed on the incoming/new > CPUID (and associated caps), i.e. clearing the dirty flag won't negatively > affect the new CPUID. > > Fixes: 93da6af3ae56 ("KVM: x86: Defer runtime updates of dynamic CPUID bits until CPUID emulation") > Reported-by: Igor Mammedov > Closes: https://lore.kernel.org/all/20251128123202.68424a95@imammedo > Cc: stable@vger.kernel.org > Signed-off-by: Sean Christopherson Acked-by: Igor Mammedov Tested-by: Igor Mammedov > --- > arch/x86/kvm/cpuid.c | 11 +++++++++-- > 1 file changed, 9 insertions(+), 2 deletions(-) > > diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c > index d563a948318b..88a5426674a1 100644 > --- a/arch/x86/kvm/cpuid.c > +++ b/arch/x86/kvm/cpuid.c > @@ -509,11 +509,18 @@ static int kvm_set_cpuid(struct kvm_vcpu *vcpu, struct kvm_cpuid_entry2 *e2, > u32 vcpu_caps[NR_KVM_CPU_CAPS]; > int r; > > + /* > + * Apply pending runtime CPUID updates to the current CPUID entries to > + * avoid false positives due to mismatches on KVM-owned feature flags. > + */ > + if (vcpu->arch.cpuid_dynamic_bits_dirty) > + kvm_update_cpuid_runtime(vcpu); > + > /* > * Swap the existing (old) entries with the incoming (new) entries in > * order to massage the new entries, e.g. to account for dynamic bits > - * that KVM controls, without clobbering the current guest CPUID, which > - * KVM needs to preserve in order to unwind on failure. > + * that KVM controls, without losing the current guest CPUID, which KVM > + * needs to preserve in order to unwind on failure. > * > * Similarly, save the vCPU's current cpu_caps so that the capabilities > * can be updated alongside the CPUID entries when performing runtime