From nobody Thu Apr 2 06:11:21 2026 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (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 380403B4EB5; Mon, 30 Mar 2026 10:23:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774866232; cv=none; b=HEhfgHEk0JqQz/ACWVDQwdtBROm5maL0Ehn0YO08qNXfU7SxdNjePjZmWYFjQrKuV8+y+TGvco3NSqp/M8u4jfCzvk+PMG1ZZUIXNjYPz4LCgs5QRtnQaUquhlHgpubb5xVt4+Xqg82GyHCKTH8H4jvvuDni5gM6smysWDitMBk= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774866232; c=relaxed/simple; bh=Q48isQZeM0XCkUpt/6OnLUXUjnbK2j/+y+1iiwL7dvU=; h=Date:From:To:Subject:Cc:In-Reply-To:References:MIME-Version: Message-ID:Content-Type; b=kcpUNTSapxO2S3JWTqKVO9nCiMuWiW6CjV0F0aS1pzEAy2GlJMs01bUCo5XOLWX1PIo+4OHMpM3+u7f2GQsmeYggdRuiBROWiILkq416UCfkuJMudY6kNS0OLbnoA/AfMtCpaTxfIG+QathQIy28K84wTjhK8XmpVm1DReC+E+0= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=hF+hTuLO; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=csI58Keq; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="hF+hTuLO"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="csI58Keq" Date: Mon, 30 Mar 2026 10:23:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1774866228; h=from:from:sender:sender:reply-to: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=2k2DwY3Ix5pxuUkSqCMyNig9Cui2AsXxYDH+oxxriX8=; b=hF+hTuLOh+hmps/lFeU2RtAsuT2rUtV+PqWZlf9JItGPgnE2UoW1L/8QMX2Kpg65jaatTE OZzN1r2NrljNTx3O5KkdbVsK7Ywa4+bJTCKU5yESSN3XLNp9iJFoNswIdhtD2vOUcTNlXg SRh/l/a4Mw0V9g+ydto6vlxVUjSowbZyV99n2VYdmC6HEr/nI9mWipUvMR9moyj9UZ1h9t vOAAr4ITCE3bMgpl6o5256eFMnF/nDB0mvDIk+W04fhhRO8Xmag/3z9yC9BOL+dOAxpOVY 113MlicXV8c/ySiiWNsnWQgdHwK+5RomZ5XmG2lWIKVsKHhSjvZe4drDQue1Yg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1774866228; h=from:from:sender:sender:reply-to: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=2k2DwY3Ix5pxuUkSqCMyNig9Cui2AsXxYDH+oxxriX8=; b=csI58KeqeDzX+YNgdbPLKnp5tZJytKnmOPM6eFg8uqOPRUXpl8lkxhfe2TIX/DMyLxzd1s sUuZ1gyXZPQrlaCQ== From: "tip-bot2 for Sohil Mehta" Sender: tip-bot2@linutronix.de Reply-to: linux-kernel@vger.kernel.org To: linux-tip-commits@vger.kernel.org Subject: [tip: x86/fred] x86/fred: Remove kernel log message when initializing exceptions Cc: Sohil Mehta , "H. Peter Anvin (Intel)" , "Borislav Petkov (AMD)" , x86@kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <20260325230151.1898287-4-hpa@zytor.com> References: <20260325230151.1898287-4-hpa@zytor.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Message-ID: <177486622630.1647592.2608945108811799.tip-bot2@tip-bot2> Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails Precedence: bulk Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable The following commit has been merged into the x86/fred branch of tip: Commit-ID: f0958d588e6de263224ca92087b45ce72fa25c91 Gitweb: https://git.kernel.org/tip/f0958d588e6de263224ca92087b45ce72= fa25c91 Author: Sohil Mehta AuthorDate: Wed, 25 Mar 2026 16:01:49 -07:00 Committer: Borislav Petkov (AMD) CommitterDate: Fri, 27 Mar 2026 16:38:24 +01:00 x86/fred: Remove kernel log message when initializing exceptions When FRED is enabled, its initialization message is printed for every CPU during boot as well as during suspend-resume. This debug message can be noi= sy and it isn't very useful unless someone is debugging FRED itself. As FRED is enabled by default, remove the log message as mentioned in the code comment. Signed-off-by: Sohil Mehta Signed-off-by: H. Peter Anvin (Intel) Signed-off-by: Borislav Petkov (AMD) Link: https://patch.msgid.link/20260325230151.1898287-4-hpa@zytor.com --- arch/x86/kernel/fred.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/arch/x86/kernel/fred.c b/arch/x86/kernel/fred.c index e736b19..117aa06 100644 --- a/arch/x86/kernel/fred.c +++ b/arch/x86/kernel/fred.c @@ -27,9 +27,6 @@ EXPORT_PER_CPU_SYMBOL(fred_rsp0); =20 void cpu_init_fred_exceptions(void) { - /* When FRED is enabled by default, remove this log message */ - pr_info("Initialize FRED on CPU%d\n", smp_processor_id()); - /* * If a kernel event is delivered before a CPU goes to user level for * the first time, its SS is NULL thus NULL is pushed into the SS field