From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>,
Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v6 0/5] x86/ve: CPUID override follow-ups: arm at once, prefixes, selftests
Date: Thu, 08 Oct 2026 15:39:05 +0200 [thread overview]
Message-ID: <179146674589.1215016.16196011593577300767.b4-ty@b4> (raw)
In-Reply-To: <20261007-b4-prep-khorenko-vstor-148656-cpuid-v6-0-a8eb906e69b8@virtuozzo.com>
On Wed, 07 Oct 2026 13:57:01 +0200, Konstantin Khorenko wrote:
> x86/ve: CPUID override follow-ups: arm at once, prefixes, selftests
>
> VSTOR-148656, every Container start dying with SIGSEGV once
> /proc/vz/cpuid_override is non-empty, is fixed in 22.8 by 07338fbae5a3
> ("x86/traps: emulate CPUID faults for user tasks in
> exc_general_protection()"). Working on it turned up two more defects in
> the same feature, and the fact that nothing had ever exercised it. This
> series takes care of those. None of them is a 22.x regression, all have
> been there since the vz9 port.
>
> [...]
Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.9.vz10, thanks!
[1/5] selftests/ve: check CPUID override emulation for VE tasks
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/9d42a52a993c
[2/5] x86/ve: enable CPUID faulting at once when the current task enters a VE
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/f2176fcad7e5
[3/5] selftests/ve: check CPUID override right after entering a VE
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/f5881322c62d
[4/5] x86/traps: decode the faulting CPUID with the instruction decoder
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/83f8ff040d0e
[5/5] selftests/ve: check CPUID override emulation for a prefixed CPUID
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/c22db725e448
--
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-10-08 13:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 11:57 Konstantin Khorenko
2026-10-07 11:57 ` [Devel] [PATCH hci-8.1 v6 1/5] selftests/ve: check CPUID override emulation for VE tasks Konstantin Khorenko
2026-10-07 12:04 ` no-reply
2026-10-07 13:16 ` Konstantin Khorenko
2026-10-07 11:57 ` [Devel] [PATCH hci-8.1 v6 2/5] x86/ve: enable CPUID faulting at once when the current task enters a VE Konstantin Khorenko
2026-10-07 12:02 ` no-reply
2026-10-08 10:18 ` Vasileios Almpanis
2026-10-08 13:38 ` Konstantin Khorenko
2026-10-07 11:57 ` [Devel] [PATCH hci-8.1 v6 3/5] selftests/ve: check CPUID override right after entering " Konstantin Khorenko
2026-10-07 12:03 ` no-reply
2026-10-07 11:57 ` [Devel] [PATCH hci-8.1 v6 4/5] x86/traps: decode the faulting CPUID with the instruction decoder Konstantin Khorenko
2026-10-07 12:04 ` no-reply
2026-10-07 11:57 ` [Devel] [PATCH hci-8.1 v6 5/5] selftests/ve: check CPUID override emulation for a prefixed CPUID Konstantin Khorenko
2026-10-07 12:04 ` no-reply
2026-10-08 10:18 ` [Devel] [PATCH hci-8.1 v6 0/5] x86/ve: CPUID override follow-ups: arm at once, prefixes, selftests Vasileios Almpanis
2026-10-08 13:39 ` Konstantin Khorenko [this message]
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=179146674589.1215016.16196011593577300767.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=vasileios.almpanis@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.