From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Eva Kurchatova <eva.kurchatova@virtuozzo.com>,
Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v2 0/6] configs: a User Mode Linux kernel for the KUnit tests
Date: Tue, 27 Oct 2026 11:51:47 +0100 [thread overview]
Message-ID: <179309830766.804544.3471517929501388261.b4-ty@b4> (raw)
In-Reply-To: <20261026-b4-prep-khorenko-vstor-143636-uml-config-v2-0-76c8329592af@virtuozzo.com>
On Mon, 26 Oct 2026 23:34:18 +0100, Konstantin Khorenko wrote:
> configs: a User Mode Linux kernel for the KUnit tests
>
> Several KUnit tests can only be built into the kernel image, and the
> shipped kernel builds its tests as modules, so nothing runs them. The
> series adds a "um" config variant: a User Mode Linux kernel with every
> KUnit test built in, under KASAN and UBSAN. kernel.spec builds it with
> ARCH=um, kernel-selftests-internal ships it, and the hci-kunit test runs
> it.
>
> [...]
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.10.vz10, thanks!
[1/6] configs: add a User Mode Linux config for the KUnit tests
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/c67082cdd639
[2/6] kasan: let a config leave the KUnit test out under KUNIT_ALL_TESTS
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/d71c7580c4a0
[3/6] configs: build the User Mode Linux KUnit kernel with KASAN
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/5350a101acdc
[4/6] configs: build the User Mode Linux KUnit kernel without debug info
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/9c767dbc20ac
[5/6] configs: turn off module-only subsystems in the User Mode Linux config
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/e65b6f7a1424
[6/6] configs: check the User Mode Linux KUnit config at build time
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/f4a3d912fd96
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-10-27 10:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 22:34 Konstantin Khorenko
2026-10-26 22:34 ` [Devel] [PATCH hci-8.1 v2 1/6] configs: add a User Mode Linux config " Konstantin Khorenko
2026-10-26 22:34 ` [Devel] [PATCH hci-8.1 v2 2/6] kasan: let a config leave the KUnit test out under KUNIT_ALL_TESTS Konstantin Khorenko
2026-10-26 22:34 ` [Devel] [PATCH hci-8.1 v2 3/6] configs: build the User Mode Linux KUnit kernel with KASAN Konstantin Khorenko
2026-10-26 22:34 ` [Devel] [PATCH hci-8.1 v2 4/6] configs: build the User Mode Linux KUnit kernel without debug info Konstantin Khorenko
2026-10-26 22:34 ` [Devel] [PATCH hci-8.1 v2 5/6] configs: turn off module-only subsystems in the User Mode Linux config Konstantin Khorenko
2026-10-26 22:34 ` [Devel] [PATCH hci-8.1 v2 6/6] configs: check the User Mode Linux KUnit config at build time Konstantin Khorenko
[not found] ` <0429d3d2-4664-4afa-a088-993344b6140f@virtuozzo.com>
2026-10-27 10:42 ` [Devel] [PATCH hci-8.1 v2 0/6] configs: a User Mode Linux kernel for the KUnit tests Konstantin Khorenko
2026-10-27 10:51 ` 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=179309830766.804544.3471517929501388261.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--cc=eva.kurchatova@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