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 9ABD938F65A 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=1774480714; cv=none; b=bO77oWtkP4Wiwg4u0ZU54ncNbAV67ChL0FFR0JDHrNn6zZA8ZcfnAEG7mr1w5cDFtGk6Kz0zL4DOgYmgGJSmtGwwTyXdtYtbXtaYUOf8hUXSgFV1cCKmdlAkgRGNSpAu214VUuznjCgBqB383YUDt7Y7y/2QCuYuQ1bi1ZNsmWg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774480714; c=relaxed/simple; bh=dl5fLUi+QyzsR8JUGnbDc0wqJeC7IG8TujZVYx0iXSA=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=W6yJXK6N6Btssuu847hOqCMv5S1fm6WqqgRrqevp07SOgIZp7Z/HzSG59opCz8kMcSn6qXMnZsjj8GBWcc6AlueaaOgMS7ST2pJUPYRCC9rvFZBk1jJZgUygHs8CMBXsAdxgv+1GxFeSIJZ4/eQuHCWezQyKnE0Hxg4V1nLl8FI= 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=OBheJibs; 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="OBheJibs" 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 62PN21br3806967 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 25 Mar 2026 16:02:04 -0700 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 62PN21br3806967 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2026022301; t=1774479724; bh=EPn0TwMqh67fwpN1tu3gkpmogXCxSXiEVNcqMGKGqJg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=OBheJibsb2UVU2G05Fp1CKh9eQHVqXM2dNdaEqjOlRKlbHStnSHZTmx4p4srDb4yZ i2QeO2fwoOoacBjRHGTqKDFVK9sWbhRcheN6r1FerN4aHRCeyeF1U9AS8Ruu1xWZ+K hByrszPcffXaQkXfoDkVEfxVK1z5eQiRhDv1NGW19Xp6Sb9YKjiwVp9kU2c24IYKJ4 OnTECsmeQ69DrCgfVX5GRNI7twHMojK/mI9X2n4qE86f2SUxprxHGmCCqDyPPgOEFp Sy6MonHHZY9VdCut64RSFqVPJH4dcBp4cBTlTYOIOzCWb2qCbD6dNQoBmHxhQk9l6n jkbyyI2TlsfHw== 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 2/3] x86/Kconfig: tighten up wording of the CONFIG_X86_FRED help text Date: Wed, 25 Mar 2026 16:01:48 -0700 Message-ID: <20260325230151.1898287-3-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 The CONFIG_X86_FRED help text has both "try to" and "if the system supports it", which are redundant statements. Remove "try to". Signed-off-by: H. Peter Anvin (Intel) --- arch/x86/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index e2df1b147184..876b663dcf38 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -557,7 +557,7 @@ config X86_FRED bool "Flexible Return and Event Delivery" depends on X86_64 help - When enabled, try to use Flexible Return and Event Delivery + When enabled, use Flexible Return and Event Delivery instead of the legacy SYSCALL/SYSENTER/IDT architecture for ring transitions and exception/interrupt handling if the system supports it. -- 2.53.0