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 9AA6231E852 for ; Wed, 25 Mar 2026 23:18:32 +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=1774480713; cv=none; b=jpBSfe80+Veap9KIEG/gSlo2kAPUcFqD1VCKTcRt9SmB2VGJGFWWWcqR5ujdwILMXaqspMJsMqrxslezoSbYG1s5xmBzzSRGG5fxUT0wiDaJMDwOkqHvBoetXW+v/u4EZl22QbsFmM3A3leLkyEMkzRGuXlIbftyzMEFbSkAVgI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774480713; c=relaxed/simple; bh=SdLEbmsSaGjCUTAxKj2ckHExNZyRIHmm4sE7layOHU8=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=Wc6cUWkI0dQRq3te0XCSgFiMFTMOA9SaRP9eC5xzkSZBD6FT53/j23lVR1Wcxqg5342V8EzcjQkwsS+lyArSgDMO7FKOmDHsZlPea6N7gG6BRDY7TH8/6DK1JXIFd4lOYMoZ/evzK39Wz9rY9C1cwxN1EQXrqSG2ckYmt/D+5jM= 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=lAVPX8+z; 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="lAVPX8+z" Received: from mail.zytor.com (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 62PN21bs3806967 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 25 Mar 2026 16:02:05 -0700 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 62PN21bs3806967 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2026022301; t=1774479725; bh=EmD5B8hlBZ5xa+S6ZaB0hqWkM52DjCO70XM0zw5MGTU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=lAVPX8+zT2KOeipqz5gioWe//NSqG2rjCdlJN5KUB1xfTFRyyABvetCbqBv6Rifp2 k+bJBX43Yt583jk5uJ2BYff90wfW8rZ1nwnC0INf3t65Fxlcgts9PJqLgJf4xebqrq DWb8KPwa8o1J8NG65O0d6wqgPUs/g7OjvM+IgwP8L0Vbls0wPwZiqEJeUilTev8QMn JUsOAfotG5yZKPaBt2HEaPohc670yO5wDp8FiGD0+SHVWuP+hsA2XRH7lb6CXlFRxk WHgX2eLJ+M14aSiAD/K+woyT8HoEeY+qJ7djGToLJrU0bnOV5z0XH9qSaBkbqmkB8z 1oo+TEa5eJc0A== From: "H. Peter Anvin" To: Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" Cc: "Peter Zijlstra (Intel)" , Kees Cook , Xin Li , "Ahmed S. Darwish" , Sohil Mehta , linux-kernel@vger.kernel.org Subject: [PATCH v2 3/3] x86/fred: Remove kernel log message when initializing exceptions Date: Wed, 25 Mar 2026 16:01:49 -0700 Message-ID: <20260325230151.1898287-4-hpa@zytor.com> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260325230151.1898287-1-hpa@zytor.com> References: <20260325230151.1898287-1-hpa@zytor.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 From: Sohil Mehta 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 Signed-off-by: H. Peter Anvin (Intel) --- 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 e736b19e18de..117aa06d25ca 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 -- 2.53.0