From: Sohil Mehta <sohil.mehta@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
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>
Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>,
Kees Cook <kees@kernel.org>, Xin Li <xin@zytor.com>,
"Ahmed S. Darwish" <darwi@linutronix.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] x86/fred: enable FRED by default
Date: Wed, 25 Mar 2026 19:04:16 -0700 [thread overview]
Message-ID: <37dfd1fb-991b-4c1e-8b50-8220a9f038fe@intel.com> (raw)
In-Reply-To: <20260325230151.1898287-2-hpa@zytor.com>
On 3/25/2026 4:01 PM, H. Peter Anvin wrote:
> Accordingly, enable FRED by default if the CPU supports it. FRED can
> of course still be disabled via the fred=off command line option.
>
> Signed-off-by: H. Peter Anvin (Intel) <hpa@zytor.com>
> ---
Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
next prev parent reply other threads:[~2026-03-26 2:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 23:01 [PATCH v2 0/3] " H. Peter Anvin
2026-03-25 23:01 ` [PATCH v2 1/3] " H. Peter Anvin
2026-03-26 2:04 ` Sohil Mehta [this message]
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: x86/fred] " tip-bot2 for Sohil Mehta
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=37dfd1fb-991b-4c1e-8b50-8220a9f038fe@intel.com \
--to=sohil.mehta@intel.com \
--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=peterz@infradead.org \
--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