mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "tip-bot2 for Sohil Mehta" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Sohil Mehta <sohil.mehta@intel.com>,
	"H. Peter Anvin (Intel)" <hpa@zytor.com>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/fred] x86/fred: Remove kernel log message when initializing exceptions
Date: Mon, 30 Mar 2026 10:23:46 -0000	[thread overview]
Message-ID: <177486622630.1647592.2608945108811799.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20260325230151.1898287-4-hpa@zytor.com>

The following commit has been merged into the x86/fred branch of tip:

Commit-ID:     f0958d588e6de263224ca92087b45ce72fa25c91
Gitweb:        https://git.kernel.org/tip/f0958d588e6de263224ca92087b45ce72fa25c91
Author:        Sohil Mehta <sohil.mehta@intel.com>
AuthorDate:    Wed, 25 Mar 2026 16:01:49 -07:00
Committer:     Borislav Petkov (AMD) <bp@alien8.de>
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 noisy
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 <sohil.mehta@intel.com>
Signed-off-by: H. Peter Anvin (Intel) <hpa@zytor.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
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);
 
 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

  reply	other threads:[~2026-03-30 10:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 23:01 [PATCH v2 0/3] x86/fred: enable FRED by default H. Peter Anvin
2026-03-25 23:01 ` [PATCH v2 1/3] " H. Peter Anvin
2026-03-26  2:04   ` Sohil Mehta
2026-03-30 10:23   ` [tip: x86/fred] x86/fred: Enable " tip-bot2 for H. Peter Anvin
2026-03-25 23:01 ` [PATCH v2 2/3] x86/Kconfig: tighten up wording of the CONFIG_X86_FRED help text H. Peter Anvin
2026-03-26 16:26   ` Borislav Petkov
2026-03-25 23:01 ` [PATCH v2 3/3] x86/fred: Remove kernel log message when initializing exceptions H. Peter Anvin
2026-03-30 10:23   ` tip-bot2 for Sohil Mehta [this message]
2026-03-26 22:11 ` [PATCH v2 0/3] x86/fred: enable FRED by default Andy Lutomirski
2026-03-26 22:26   ` Jens Axboe
2026-03-28  1:20   ` H. Peter Anvin
2026-04-03 15:29     ` Andy Lutomirski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=177486622630.1647592.2608945108811799.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=sohil.mehta@intel.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®