From: Mikhail Paulyshka <me@mixaill.net>
To: Dave Hansen <dave.hansen@intel.com>, Borislav Petkov <bp@alien8.de>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] x86/rdrand: disable RDSEED on AMD Cyan Skillfish
Date: Mon, 7 Jul 2025 13:17:41 +0300 [thread overview]
Message-ID: <40cd274e-a02b-450d-88df-aa2b92b51b12@mixaill.net> (raw)
In-Reply-To: <cfb12298-5214-4fc1-859c-2218c7da4ce3@intel.com>
On 6/17/25 11:21 PM, Dave Hansen wrote:
> Heh, maybe if x86_init_rdrand() did RDSEED too, this wouldn't have
> slipped through QA.
This might be interesting to you: in V1 of this patch set, there was an
RDSEED sanity check, and Intel's CI detected broken RDSEED on Comet Lake:
https://lore.kernel.org/all/202503211421.fc83271a-lkp@intel.com/
next prev parent reply other threads:[~2025-07-07 10:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 14:53 [PATCH v2 1/1] x86/rdrand: disable RDSEED on AMD Cyan Skillfish Mikhail Paulyshka
2025-05-24 16:11 ` Borislav Petkov
2025-06-17 20:05 ` Borislav Petkov
2025-06-17 20:21 ` Dave Hansen
2025-07-07 10:17 ` Mikhail Paulyshka [this message]
2025-07-07 15:25 ` Borislav Petkov
2025-07-07 15:34 ` Dave Hansen
2025-07-06 16:42 ` Mikhail Paulyshka
2025-07-06 17:07 ` Borislav Petkov
2025-07-06 20:31 ` Mikhail Paulyshka
2025-07-08 14:50 ` [tip: x86/urgent] x86/CPU/AMD: Disable INVLPGB on Zen2 tip-bot2 for Mikhail Paulyshka
2025-07-08 19:50 ` tip-bot2 for Mikhail Paulyshka
2025-07-08 14:50 ` [tip: x86/urgent] x86/rdrand: Disable RDSEED on AMD Cyan Skillfish tip-bot2 for Mikhail Paulyshka
2025-07-08 19:50 ` tip-bot2 for Mikhail Paulyshka
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=40cd274e-a02b-450d-88df-aa2b92b51b12@mixaill.net \
--to=me@mixaill.net \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).