From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.11]) (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 D0E2B3AB283 for ; Mon, 18 May 2026 22:21:08 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779142870; cv=none; b=AOrPh/zr18F3mCIaamVy2GUxDSrQJiHzu9oFmGAuwW6UiIK1DteQlt+zDBpY74t2oBCJLVwmv35VOJ7cZeR1evrsxu57QdMxLq1pr4w6K776yu5V0F6xz/T2pt6hSTwxW5S3TV61LMcJQFDVvEeYM5eN7kQHmLZu4j22pa/f73A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779142870; c=relaxed/simple; bh=D1ZgGQjfRdsiaJd2opOYWb72S7Ib6zYLfiyUZijWnFQ=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=e+c9wwRO50aSSesL9hrNnUQNYOT8rOm9oOKUit76Y3z4Nv8/7a/jncOLdkqH/PyPH3YarHZm2JWWyU0sG4rDc+heCL13PYYz8A9UzWTHDrGAV17nwRpRV8qOJ9Xeq2jxj9XsFmcqcAGRqJfWK6TjLuHbxqf7iZz5M8Dc0fjATwc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=YLKb0tEw; arc=none smtp.client-ip=198.175.65.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="YLKb0tEw" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1779142869; x=1810678869; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=D1ZgGQjfRdsiaJd2opOYWb72S7Ib6zYLfiyUZijWnFQ=; b=YLKb0tEwP+X8EyngFXhyhS9OSwHizITQDfgUvUM9p3WsjuaeAC3UqjH4 f45W9LSwaFazV9qd4tF+YQDL+317j/IKaDwTOuaGmwgwi7qSDa9Mqb+M0 zetvnz2t5oxaD9Zn5Tq9iiDKUYfSWGYxzNxks4dZQV5ok696I/OwjmqFq zkQK8A7gEvbB7hOnrqp7N1QJMLhKKbdtEhJYnQGMrR4xV+MHhfrM3UtO9 cd4ZeBzMoYcS7wfc+ORz5bh/wjqVm8+2aTYhOIIdtNgzA/h3/OhD1kkn4 Ad6GWcN6sPSMu32ysNo5QXFwA4CjLBgNl7rkl9qw3R/N5wnuHzoM64QoL A==; X-CSE-ConnectionGUID: EvZWWKHeTiaYKw00owUi9A== X-CSE-MsgGUID: YB8LuXfYRoCq8pwj9Rtbwg== X-IronPort-AV: E=McAfee;i="6800,10657,11790"; a="90317865" X-IronPort-AV: E=Sophos;i="6.23,242,1770624000"; d="scan'208";a="90317865" Received: from orviesa005.jf.intel.com ([10.64.159.145]) by orvoesa103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 May 2026 15:21:06 -0700 X-CSE-ConnectionGUID: xwnwQz7xT/uSvBARSnanpQ== X-CSE-MsgGUID: MA3esNiMR9ajXvvTubmeXg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,242,1770624000"; d="scan'208";a="244564550" Received: from sohilmeh.sc.intel.com ([172.25.103.65]) by orviesa005.jf.intel.com with ESMTP; 18 May 2026 15:21:06 -0700 From: Sohil Mehta To: Dave Hansen , Borislav Petkov , x86@kernel.org Cc: Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , Josh Poimboeuf , Richard Weinberger , Andrew Cooper , Tony Luck , Sohil Mehta , "Ahmed S . Darwish" , linux-kernel@vger.kernel.org Subject: [PATCH v3 2/3] x86/cpu/intel: Remove the F00F bug workaround notice Date: Mon, 18 May 2026 15:17:17 -0700 Message-ID: <20260518221718.3303288-3-sohil.mehta@intel.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20260518221718.3303288-1-sohil.mehta@intel.com> References: <20260518221718.3303288-1-sohil.mehta@intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit The F00F bug workaround announcement goes through a lot of effort to print the kernel notice exactly once. CPU bugs with workarounds typically don't require user notifications. If needed, the presence of the F00F bug can be determined through /proc/cpuinfo. Remove the notice and the surrounding logic to print it once. Signed-off-by: Sohil Mehta --- v3: - Get rid of the notice instead of simplifying it. (Ahmed) v2: - New patch --- arch/x86/kernel/cpu/intel.c | 14 +++----------- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c index e957c5a1501c..329ab1a90f5e 100644 --- a/arch/x86/kernel/cpu/intel.c +++ b/arch/x86/kernel/cpu/intel.c @@ -388,23 +388,15 @@ __setup("forcepae", forcepae_setup); static void intel_workarounds(struct cpuinfo_x86 *c) { -#ifdef CONFIG_X86_F00F_BUG /* * All models of Pentium and Pentium with MMX technology CPUs * have the F0 0F bug, which lets nonprivileged users lock up the - * system. Announce that the fault handler will be checking for it. + * system. The fault handler always checks for it. * The Quark is also family 5, but does not have the same bug. */ - if (c->x86_vfm >= INTEL_FAM5_START && c->x86_vfm < INTEL_QUARK_X1000) { - static int f00f_workaround_enabled; - + if ((IS_ENABLED(CONFIG_X86_F00F_BUG)) && + (c->x86_vfm >= INTEL_FAM5_START && c->x86_vfm < INTEL_QUARK_X1000)) set_cpu_bug(c, X86_BUG_F00F); - if (!f00f_workaround_enabled) { - pr_notice("Intel Pentium with F0 0F bug - workaround enabled.\n"); - f00f_workaround_enabled = 1; - } - } -#endif /* * SEP CPUID bug: Pentium Pro reports SEP but doesn't have it until -- 2.43.0