All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: svt-core@virtuozzo.com
Cc: andrey.drobyshev@virtuozzo.com, den@openvz.org
Subject: [PATCH hci-8.1 v2 1/2] i386: turn off x-consistent-cache on all Virtuozzo machine types #VSTOR-154986
Date: Tue, 17 Nov 2026 18:46:09 +0100	[thread overview]
Message-ID: <20261117174610.1689714-2-den@openvz.org> (raw)
In-Reply-To: <20261117174610.1689714-1-den@openvz.org>

From: Denis V. Lunev <den@openvz.org>

pc-q35-vz10.1.0 is based on rhel10.2.0 and so takes the upstream default
of x-consistent-cache from 6699e5dc864 ("i386/cpu: Present same cache
model in CPUID 0x2 & 0x4"). CPUID leaf 2 then reports 0xff, "use leaf
4", instead of legacy descriptors. glibc reads leaf 2 for each of its
cache queries at every process start, and with 0xff each read walks the
leaf 4 subleaves. Under KVM every CPUID is a VM exit, so a vz10.1.0
guest takes many more CPUID exits per exec than a vz10.0.0 one, and
fork/exec heavy workloads (unixbench execl, spawn and shell) regress.

Neither cache model describes the host, both are synthetic, so the new
one buys the guest nothing. Turn it off in pc_vz_compat, which every
Virtuozzo machine type applies, so the types added later keep it off
too. Only pc-q35-vz10.1.0 changes, the older types and
pc-i440fx-vz10.1.0 already get it off from their RHEL base.

The guest reads leaf 2 at boot and glibc at process start, so a running
vz10.1.0 guest migrated to a node with this change keeps working, new
processes just see the old descriptors.

Signed-off-by: Denis V. Lunev <den@openvz.org>
---
 hw/i386/pc.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index 2834982dab4..40127f70269 100644
--- a/hw/i386/pc.c
+++ b/hw/i386/pc.c
@@ -545,6 +545,7 @@ GlobalProperty pc_vz_compat[] = {
     { TYPE_X86_CPU, "kvm-pv-tlb-flush", "on" },
     { TYPE_X86_CPU, "kvm-pv-sched-yield", "on" },
     { TYPE_X86_CPU, "kvm-asyncpf-int", "on" },
+    { TYPE_X86_CPU, "x-consistent-cache", "false" },
 };
 const size_t pc_vz_compat_len = G_N_ELEMENTS(pc_vz_compat);
 
-- 
2.55.0


  reply	other threads:[~2026-11-17 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 17:46 [PATCH hci-8.1 v2 0/2] i386: fix the exec slowdown of pc-q35-vz10.1.0 guests #VSTOR-154986 Denis V. Lunev
2026-11-17 17:46 ` Denis V. Lunev [this message]
2026-11-17 17:48   ` [PATCH hci-8.1 v2 1/2] i386: turn off x-consistent-cache on all Virtuozzo machine types #VSTOR-154986 no-reply
2026-11-17 17:46 ` [PATCH hci-8.1 v2 2/2] i386: hide la57 at fresh start " Denis V. Lunev
2026-11-17 17:49   ` no-reply
2026-11-17 18:04 ` [PATCH hci-8.1 v2 0/2] i386: fix the exec slowdown of pc-q35-vz10.1.0 guests #VSTOR-154986 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=20261117174610.1689714-2-den@openvz.org \
    --to=den@openvz.org \
    --cc=andrey.drobyshev@virtuozzo.com \
    --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 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.