From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zytor.com (terminus.zytor.com [198.137.202.136]) (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 8035F396D15 for ; Mon, 18 May 2026 21:24:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.136 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779139447; cv=none; b=OqSZAkpLRbeOBptPAegeXecUv6CnHOF9CoFNpKywoBxZ972uVNANJxJSUTzQiFQ8B8PVAtRAa9qJNdj2UgY00gFWWLv/fyCgmNoxIo4ghcUxwvWFiHxbiTyyvLGW5bYNIPp913SvLyv/rrJnarddQ0tOkrsD9CbITZ4pE2+qap0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779139447; c=relaxed/simple; bh=3A68h42rn6NV1d7mNoxGPU9FMWJjyYYWrIHXP1Bd0B8=; h=Date:From:To:CC:Subject:In-Reply-To:References:Message-ID: MIME-Version:Content-Type; b=l07rhDHo8RcLLeOfdw+QypJtUrYdw/+ikc6ZW7mwBhEIn48YKdeily0eUYlZDmE8N391zCcroGA/afXmES9FeSAjqOecNmDUwklCjfpZx/NlgnqS1uD7derQu3EfeLH0NaxYCbfViup6fIeZ4sze1SVlP4wmE8JGL74pqDRnLlA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com; spf=pass smtp.mailfrom=zytor.com; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b=V6sVq4+v; arc=none smtp.client-ip=198.137.202.136 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zytor.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b="V6sVq4+v" Received: from ehlo.thunderbird.net (c-76-133-66-138.hsd1.ca.comcast.net [76.133.66.138]) (authenticated bits=0) by mail.zytor.com (8.18.1/8.17.1) with ESMTPSA id 64ILNEVP2424016 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Mon, 18 May 2026 14:23:15 -0700 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 64ILNEVP2424016 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2026042601; t=1779139395; bh=3A68h42rn6NV1d7mNoxGPU9FMWJjyYYWrIHXP1Bd0B8=; h=Date:From:To:CC:Subject:In-Reply-To:References:From; b=V6sVq4+vBWAogQFgKJSvkfaIY4YgnY5Jb14j9p5oJV+U3T/ysTl8fokpwQ9FiF1i5 qMH0qHWlUjptWm077HXjvnzGGGvQ/++zP0qzxl5cm60s1rZso/W2y4h1FdEx2u0GF1 rpcF7FJkS4ULUSa/yJwb0BZiRAgL2I1F1u+tgTGPjTjLnjtlUQ92AEg/rP+ZtvFehw Oa51qrZeuH/kGBqbGHQ08a+Dast0FKIP24nh+99GjaEOFNImLiSvsPicneyNehoe44 RbXLQu91NjCRla69KShdn/2GpLt1XE2vKK2ZEPp0Nmh8+tqr2rXSq8DwtNw06zopKm gXAkr4KEta1bg== Date: Mon, 18 May 2026 14:23:08 -0700 From: "H. Peter Anvin" To: Dave Hansen , Sohil Mehta , "Ahmed S. Darwish" CC: Dave Hansen , Borislav Petkov , x86@kernel.org, Thomas Gleixner , Ingo Molnar , Josh Poimboeuf , Richard Weinberger , Andrew Cooper , Tony Luck , linux-kernel@vger.kernel.org Subject: =?US-ASCII?Q?Re=3A_=5BPATCH_v2_2/3=5D_x86/cpu/intel=3A_Simpli?= =?US-ASCII?Q?fy_F00F_bug_notice_using_pr=5Fnotice=5Fonce=28=29?= User-Agent: K-9 Mail for Android In-Reply-To: References: <20260515002500.2463393-1-sohil.mehta@intel.com> <20260515002500.2463393-3-sohil.mehta@intel.com> Message-ID: <024D39DA-32BE-4511-91C4-F1687DE96EB6@zytor.com> 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=utf-8 Content-Transfer-Encoding: quoted-printable On May 18, 2026 2:17:13 PM PDT, Dave Hansen wro= te: >On 5/18/26 13:29, Sohil Mehta wrote: >>> I think this pr_notice() is fine to remove=2E >> Sure, I'll remove the notice and also convert the #ifdef >> CONFIG_X86_F00F_BUG into IS_ENABLED(CONFIG_X86_F00F_BUG)=2E > >BTW=2E=2E=2E The basic trajectory these days is not to be so careful with >32-bit-only gunk=2E If it's causing us any headache -- even a few lines o= f >code -- it better be unambiguously crucial to functionality to stick arou= nd=2E > >In this case, the guy still running a Pentium classic is highly unlikely >to be concerned about the kernel forgetting to add an F0 0F workaround=2E >There are also unlikely to be Pentiums sitting in data centers with log >monitoring tools that are desperately looking for that F0 0F hunk in dmes= g=2E > >The most likely thing is: there are a few dozen Pentiums (if that) out >there running mainline kernels=2E I'm not sure they even have more than a >couple of distros they can run=2E Nobody is going to notice this message >going away=2E Just nuke the text=2E It's pointless; we have many other bug workarounds w= e are less noisy about=2E