All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Oleksii Kurochko <oleksii.kurochko@gmail.com>
Subject: Re: [PATCH v2 for-4.21 0/2] x86/AMD: deal with RDSEED issues
Date: Fri, 31 Oct 2025 11:22:20 +0100	[thread overview]
Message-ID: <aQSN3MKxAa_cltld@Mac.lan> (raw)
In-Reply-To: <272093dc-c97c-434a-9977-ad1c26e7e229@suse.com>

On Tue, Oct 28, 2025 at 04:32:17PM +0100, Jan Beulich wrote:
> Both patches also want 'x86/CPU: extend is_forced_cpu_cap()'s "reach"' in
> place.
> 
> 1: disable RDSEED on Fam17 model 47 stepping 0
> 2: disable RDSEED on most of Zen5

For both patches: don't we need to set the feature in the max policy
to allow for incoming migrations of guests that have already seen the
feature?

Thanks, Roger.


  parent reply	other threads:[~2025-10-31 10:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 15:32 [PATCH v2 for-4.21 0/2] x86/AMD: deal with RDSEED issues Jan Beulich
2025-10-28 15:33 ` [PATCH v2 for-4.21 1/2] x86/AMD: disable RDSEED on Fam17 model 47 stepping 0 Jan Beulich
2025-10-31  9:41   ` Teddy Astie
2025-10-28 15:34 ` [PATCH v2 for-4.21 2/2] x86/AMD: disable RDSEED on most of Zen5 Jan Beulich
2025-10-31  9:31 ` [PATCH v2 for-4.21 0/2] x86/AMD: deal with RDSEED issues Oleksii Kurochko
2025-10-31  9:34   ` Jan Beulich
2025-11-03  8:44     ` Oleksii Kurochko
2025-10-31 10:22 ` Roger Pau Monné [this message]
2025-10-31 10:29   ` Jan Beulich
2025-10-31 10:54     ` Roger Pau Monné
2025-10-31 11:47       ` Jan Beulich
2025-10-31 12:14         ` Roger Pau Monné
2025-10-31 12:34           ` Jan Beulich
2025-10-31 13:15             ` Roger Pau Monné
2025-11-06  8:39               ` Jan Beulich
2025-11-06  8:55               ` Jan Beulich
2025-11-03 14:10 ` Andrew Cooper
2025-11-06  8:49   ` Jan Beulich

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=aQSN3MKxAa_cltld@Mac.lan \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=oleksii.kurochko@gmail.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.