From: Jan Beulich <jbeulich@suse.com>
To: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
Cc: "Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
"Community Manager" <community.manager@xenproject.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v4 1/4] x86: Reject CPU policies with vendors other than the host's
Date: Wed, 11 Mar 2026 15:52:32 +0100 [thread overview]
Message-ID: <ffeb30e4-ccb0-43ff-905a-e9273dff79b7@suse.com> (raw)
In-Reply-To: <20260311142711.16754-2-alejandro.garciavallejo@amd.com>
On 11.03.2026 15:27, Alejandro Vallejo wrote:
> While in principle it's possible to have a vendor virtualising another,
> this is fairly tricky in practice and comes with the world's supply of
> security issues.
>
> Reject any CPU policy with vendors not matching the host's.
>
> Signed-off-by: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2026-03-11 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 14:27 [PATCH v4 0/4] x86: Drop cross-vendor support Alejandro Vallejo
2026-03-11 14:27 ` [PATCH v4 1/4] x86: Reject CPU policies with vendors other than the host's Alejandro Vallejo
2026-03-11 14:52 ` Jan Beulich [this message]
2026-03-11 14:27 ` [PATCH v4 2/4] x86/hvm: Disable cross-vendor handling in #UD handler Alejandro Vallejo
2026-03-11 14:59 ` Jan Beulich
2026-03-11 18:01 ` Alejandro Vallejo
2026-03-12 6:57 ` Jan Beulich
2026-03-11 18:48 ` Andrew Cooper
2026-03-11 14:27 ` [PATCH v4 3/4] x86/hvm: Remove cross-vendor checks from MSR handlers Alejandro Vallejo
2026-03-11 14:27 ` [PATCH v4 4/4] x86/svm: Drop emulation of Intel's SYSENTER behaviour on AMD systems Alejandro Vallejo
2026-03-11 18:54 ` Andrew Cooper
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=ffeb30e4-ccb0-43ff-905a-e9273dff79b7@suse.com \
--to=jbeulich@suse.com \
--cc=alejandro.garciavallejo@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=community.manager@xenproject.org \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.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.