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 0/2] i386: fix the exec slowdown of pc-q35-vz10.1.0 guests #VSTOR-154986
Date: Mon, 16 Nov 2026 18:50:00 +0100	[thread overview]
Message-ID: <20261116175002.844361-1-den@openvz.org> (raw)

HCI 8.1 guests run fork/exec heavy work about 10% slower than on 8.0.
perf-atomic showed it in all five 8.0 vs 8.1 comparisons on four HDD
nodes: unixbench execl -10.4% to -14.7%, syscall/sysexec (which are
really fork+exec) -8.6% to -12.1%, cpu-ins -5%. The host is not the
cause. 8.1 nova creates VMs with pc-q35-vz10.1.0 where 8.0 used
pc-q35-vz10.0.0, and the new machine type changes two things the guest
sees: CPUID leaf 2 reports 0xff, so glibc's cache queries at process
start cost twice the CPUID exits, and la57 is no longer hidden, so
Linux guests boot with 5-level paging.

The series turns both off on pc-q35-vz10.1.0, so it gives the guest the
same CPU as pc-q35-vz10.0.0.

The trade-off: a vz10.1.0 guest no longer gets la57 on a fresh start,
"-cpu host" included, unless it asks for it with la57=on. Our guests
do not need a 57-bit address space.

This is for hci-8.1 only. hci-dev is identical to hci-8.1 at the moment,
so the patches apply there as is. The 8.0 QEMU defines pc-q35-vz10.1.0
too and keeps it unchanged, but nova on 8.0 pins pc-q35-vz10.0.0.

Tested with the qemu-kvm-10.1.0-20.vz10.23 SRPM rebuilt with both
patches on hw-hdd01 (HCI 8.1.0-227, Xeon Silver 4314). A minimal guest
with the perf guest kernel (6.12.0-211.74.2.el10_2), Icelake-Server,
pinned to one vCPU:

                       execl/s  fork+exec/s  insb/s  CPUID exits per run
  vz10.1.0, stock 8.1    3400       2675      217K         11.85M
  vz10.1.0, patched      3890       2985      228K          6.83M
  vz10.0.0, patched      3890       2990      229K          6.84M

The perf VM itself, hard rebooted through nova on the patched QEMU,
starts with la57 disabled in its live libvirt definition, boots with
48-bit virtual addresses and runs execl at ~3995/s against 3312/s
before (3667/s on the 8.0 node).

RCA and all comparisons are in VSTOR-154986:

  https://virtuozzo.atlassian.net/browse/VSTOR-154986

Denis V. Lunev (2):
  i386: turn off x-consistent-cache on pc-q35-vz10.1.0 #VSTOR-154986
  i386: hide la57 at fresh start on pc-q35-vz10.1.0 too #VSTOR-154986

 hw/i386/pc.c         | 5 +++--
 hw/i386/pc_piix.c    | 2 +-
 hw/i386/pc_q35.c     | 4 ++--
 include/hw/i386/pc.h | 4 ++--
 target/i386/cpu.h    | 2 +-
 5 files changed, 9 insertions(+), 8 deletions(-)


base-commit: ac2ba825418b2726a7a4f367f8ef6d69d8563e47
-- 
2.55.0


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 17:50 Denis V. Lunev [this message]
2026-11-16 17:50 ` [PATCH hci-8.1 1/2] i386: turn off x-consistent-cache on pc-q35-vz10.1.0 #VSTOR-154986 Denis V. Lunev
2026-11-16 17:53   ` no-reply
2026-11-17 17:03   ` Andrey Drobyshev
2026-11-16 17:50 ` [PATCH hci-8.1 2/2] i386: hide la57 at fresh start on pc-q35-vz10.1.0 too #VSTOR-154986 Denis V. Lunev
2026-11-16 17:53   ` no-reply
2026-11-17 17:03   ` 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=20261116175002.844361-1-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.