From: no-reply@sashiko.virtuozzo.com
To: andrey.zhadchenko@virtuozzo.com, "Denis V. Lunev" <den@openvz.org>
Cc: svt-core@virtuozzo.com, den@openvz.org
Subject: Re: [PATCH v3 hci-8.0/hci-8.1 3/6] i386: keep spec-ctrl for AMD guests on vz machine types up to vz9.2.0 #VSTOR-151770
Date: Thu, 29 Oct 2026 12:29:31 +0000 [thread overview]
Message-ID: <010701a187a3091b-75a86f71-9f2b-4067-afe9-7bd890b8ed76-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <20261029122527.365104-4-den@openvz.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] i386: shared tsx_compat comment does not describe conditional spec_ctrl_compat
--
commit f0225ca6e631cf113e6cd09a3b55911125b7a154
Author: Denis V. Lunev <den@openvz.org>
i386: keep spec-ctrl for AMD guests on vz machine types up to vz9.2.0 #VSTOR-151770
This patch adds an x-spec-ctrl-compat CPU property and enables it in
pc_vz_9_2_compat. On AMD guests, a requested spec-ctrl bit is kept when the
guest and host both report amd-ibpb and at least one of amd-ibrs, amd-stibp
or amd-ssbd.
> diff --git a/target/i386/cpu.h b/target/i386/cpu.h
> index 85efd0b9fbe5..740fb3aedc56 100644
> --- a/target/i386/cpu.h
> +++ b/target/i386/cpu.h
> @@ -2337,6 +2337,7 @@ struct ArchCPU {
> * older node keeps its CPUID.
> */
> bool tsx_compat;
> + bool spec_ctrl_compat;
>
[Severity: Low]
This isn't a bug, but the comment above tsx_compat now also appears to
cover spec_ctrl_compat:
/*
* Virtuozzo machine types up to vz9.2.0: do not filter requested
* features the host no longer provides, so that a guest started on an
* older node keeps its CPUID.
*/
bool tsx_compat;
bool spec_ctrl_compat;
Is that description accurate for the new flag? In
x86_cpu_compat_kept_features(), spec_ctrl_compat keeps SPEC_CTRL only when
the vendor is AMD, the guest and the host both have amd-ibpb, and at least
one of amd-ibrs, amd-stibp or amd-ssbd is present. It does not keep every
requested feature the host no longer provides.
Could spec_ctrl_compat get its own comment that describes these conditions?
--
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261029122527.365104-1-den@openvz.org?part=3
next prev parent reply other threads:[~2026-10-29 12:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 12:25 [PATCH v3 hci-8.0/hci-8.1 0/6] i386: keep CPU features of guests from older nodes on vz machine types #VSTOR-152264 Denis V. Lunev
2026-10-29 12:25 ` [PATCH v3 hci-8.0/hci-8.1 1/6] i386/pc: raise the limit of compat arrays per Virtuozzo machine type to four #VSTOR-152264 Denis V. Lunev
2026-10-29 12:27 ` no-reply
2026-10-29 12:25 ` [PATCH v3 hci-8.0/hci-8.1 2/6] i386: keep hle and rtm on Virtuozzo machine types up to vz9.2.0 #PSBM-149402 Denis V. Lunev
2026-10-29 12:29 ` no-reply
2026-10-29 12:25 ` [PATCH v3 hci-8.0/hci-8.1 3/6] i386: keep spec-ctrl for AMD guests on vz machine types up to vz9.2.0 #VSTOR-151770 Denis V. Lunev
2026-10-29 12:29 ` no-reply [this message]
2026-10-29 12:25 ` [PATCH v3 hci-8.0/hci-8.1 4/6] i386: keep bus-lock-detect for AMD guests on vz machine types up to vz9.2.0 #VSTOR-152291 Denis V. Lunev
2026-10-29 12:30 ` no-reply
2026-10-29 12:25 ` [PATCH v3 hci-8.0/hci-8.1 5/6] i386: keep v-vmsave-vmload for nested AMD guests on vz types up to vz9.2.0 #VSTOR-152264 Denis V. Lunev
2026-10-29 12:30 ` no-reply
2026-10-29 12:25 ` [PATCH v3 hci-8.0/hci-8.1 6/6] i386: keep SVM leaf features without svm on vz types up to vz9.2.0 #PSBM-144630 Denis V. Lunev
2026-10-29 12:33 ` no-reply
2026-10-29 13:30 ` [PATCH v3 hci-8.0/hci-8.1 0/6] i386: keep CPU features of guests from older nodes on vz machine types #VSTOR-152264 Andrey Drobyshev
2026-10-29 13:47 ` Andrey Drobyshev
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=010701a187a3091b-75a86f71-9f2b-4067-afe9-7bd890b8ed76-000000@eu-central-1.amazonses.com \
--to=no-reply@sashiko.virtuozzo.com \
--cc=andrey.zhadchenko@virtuozzo.com \
--cc=den@openvz.org \
--cc=svt-core@virtuozzo.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