From: Peter Zijlstra <peterz@infradead.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Kees Cook <kees@kernel.org>,
Xin Li <xin@zytor.com>, "Ahmed S. Darwish" <darwi@linutronix.de>,
Sohil Mehta <sohil.mehta@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] x86/fred: enable FRED by default
Date: Mon, 23 Mar 2026 21:24:34 +0100 [thread overview]
Message-ID: <20260323202434.GA3738010@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260323201510.1537333-1-hpa@zytor.com>
On Mon, Mar 23, 2026 at 01:15:03PM -0700, H. Peter Anvin wrote:
> From: H. Peter Anvin (Intel) <hpa@zytor.com>
>
> When FRED was added to the mainline kernel, it was set up as an
> explicit opt-in due to the risk of regressions before hardware was
> available publicly.
>
> Now, Panther Lake (Core Ultra 300 series) has been released, and
> benchmarking by Phoronix has shown that it provides a significant
> performance benefit on most workloads:
>
> https://www.phoronix.com/review/intel-fred-panther-lake
>
> Accordingly, enable FRED by default if the CPU supports it. FRED can
> of course still be disabled via the fred=off command line option.
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2026-03-23 20:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 20:15 H. Peter Anvin
2026-03-23 20:15 ` [PATCH 1/2] " H. Peter Anvin
2026-03-23 20:15 ` [PATCH 2/2] x86/Kconfig: tighten up wording of the CONFIG_X86_FRED help text H. Peter Anvin
2026-03-23 20:24 ` Peter Zijlstra [this message]
2026-03-24 1:01 ` [PATCH 0/2] x86/fred: enable FRED by default Sohil Mehta
2026-03-24 3:05 ` Xin Li
2026-03-24 3:52 ` H. Peter Anvin
2026-03-24 5:08 ` Sohil Mehta
2026-03-24 6:34 ` Sohil Mehta
2026-03-24 7:50 ` H. Peter Anvin
2026-03-24 17:19 ` Sohil Mehta
2026-03-24 19:53 ` Borislav Petkov
2026-03-25 16:22 ` H. Peter Anvin
2026-03-25 16:30 ` Borislav Petkov
2026-03-25 16:41 ` H. Peter Anvin
2026-03-25 17:07 ` Sohil Mehta
2026-03-24 19:50 ` Borislav Petkov
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=20260323202434.GA3738010@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=darwi@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
--cc=xin@zytor.com \
/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
Powered by JetHome