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>,
"Jason Andryuk" <jason.andryuk@amd.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 0/4] x86: Drop cross-vendor support
Date: Wed, 11 Mar 2026 09:54:35 +0100 [thread overview]
Message-ID: <7973d3d1-8984-421f-88db-ca17ea3cb2ac@suse.com> (raw)
In-Reply-To: <20260213114232.42996-1-alejandro.garciavallejo@amd.com>
On 13.02.2026 12:42, Alejandro Vallejo wrote:
> Alejandro Vallejo (4):
> x86: Reject CPU policies with vendors other than the host's
> x86/hvm: Disable cross-vendor handling in #UD handler
> x86/hvm: Remove cross-vendor checks from MSR handlers.
> x86/svm: Drop emulation of Intel's SYSENTER behaviour on AMD systems
With this, do we actually want to keep emulation of SYS{ENTER,EXIT,CALL,RET}
in the insn emulator? Or at least gate that on e.g. VM_EVENT, to still allow
its use by introspection? Whether to then also permit those with HVM_FEP=y
(but VM_EVENT=n) would be a follow-on question.
Jan
next prev parent reply other threads:[~2026-03-11 8:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 11:42 [PATCH v3 0/4] x86: Drop cross-vendor support Alejandro Vallejo
2026-02-13 11:42 ` [PATCH v3 1/4] x86: Reject CPU policies with vendors other than the host's Alejandro Vallejo
2026-03-11 8:26 ` Jan Beulich
2026-03-11 12:43 ` Alejandro Vallejo
2026-02-13 11:42 ` [PATCH v3 2/4] x86/hvm: Disable cross-vendor handling in #UD handler Alejandro Vallejo
2026-03-11 8:35 ` Jan Beulich
2026-03-11 9:25 ` Alejandro Vallejo
2026-03-11 9:30 ` Jan Beulich
2026-03-11 10:21 ` Alejandro Vallejo
2026-03-11 11:06 ` Jan Beulich
2026-03-11 12:40 ` Alejandro Vallejo
2026-02-13 11:42 ` [PATCH v3 3/4] x86/hvm: Remove cross-vendor checks from MSR handlers Alejandro Vallejo
2026-03-11 8:39 ` Jan Beulich
2026-02-13 11:42 ` [PATCH v3 4/4] x86/svm: Drop emulation of Intel's SYSENTER behaviour on AMD systems Alejandro Vallejo
2026-03-11 8:46 ` Jan Beulich
2026-03-11 9:27 ` Alejandro Vallejo
2026-03-11 8:54 ` Jan Beulich [this message]
2026-03-11 9:46 ` [PATCH v3 0/4] x86: Drop cross-vendor support Alejandro Vallejo
2026-03-11 10:11 ` 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=7973d3d1-8984-421f-88db-ca17ea3cb2ac@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=jason.andryuk@amd.com \
--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.