From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Sohil Mehta <sohil.mehta@intel.com>, Xin Li <xin@zytor.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "Peter Zijlstra (Intel)" <peterz@infradead.org>,
Kees Cook <kees@kernel.org>,
"Ahmed S. Darwish" <darwi@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] x86/fred: enable FRED by default
Date: Wed, 25 Mar 2026 09:41:57 -0700 [thread overview]
Message-ID: <9bdc6bb7-0b74-4156-87dc-d2441f2a38ac@zytor.com> (raw)
In-Reply-To: <20260325163028.GAacQNpB7DlkyS4MJ4@fat_crate.local>
On 2026-03-25 09:30, Borislav Petkov wrote:
>>
>> Well, it is useful for testing code paths for legacy hardware.
>
> ... which would presume you know what you're doing.
>
> clearcpuid= is not something you or I or anyone else wants to debug when
> people start clearing random CPUID bits without knowing any better.
>
> Thus the tainting.
>
Exactly.
-hpa
next prev parent reply other threads:[~2026-03-25 16:42 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 ` [PATCH 0/2] x86/fred: enable FRED by default Peter Zijlstra
2026-03-24 1:01 ` 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 [this message]
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=9bdc6bb7-0b74-4156-87dc-d2441f2a38ac@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=darwi@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®