From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: devel@openvz.org, Konstantin Khorenko <khorenko@virtuozzo.com>
Subject: [Devel] [PATCH hci-8.1 0/2] ms/kbuild: GCOV follow-ups to the prefer-atomic fix
Date: Mon, 19 Oct 2026 20:26:49 +0200 [thread overview]
Message-ID: <20261019-b4-prep-khorenko-vstor-148131-gcov-followups-v1-0-2932ec685608@virtuozzo.com> (raw)
Two follow-ups to commit 6e1a837a05d4 ("ms/gcov: use atomic counter
updates to fix concurrent access crashes"). Peter Oberparleiter suggested
them while reviewing the upstream patch.
Both are taken from the akpm/mm tree, branch mm-nonmm-stable, and are not
in Linus's tree yet:
4719c9264131 kbuild: use $(CFLAGS_GCOV) in the prefer-atomic try-run test
f541906e89f9 kbuild: move GCOV flags to scripts/Makefile.gcov
- Patch 1 makes the try-run test compile with $(CFLAGS_GCOV) instead of a
copy of its flags, so the test also sees -fno-tree-loop-im. The outcome
of the test is unchanged.
- Patch 2 moves the CFLAGS_GCOV block into scripts/Makefile.gcov,
included via include-$(CONFIG_GCOV_KERNEL) like the KCOV and KASAN
makefiles. Builds without GCOV no longer run the try-run.
Patch 2 had a context conflict in Makefile: the CFLAGS_GCOV block has
different neighbours in this tree. The resolution is noted in the commit.
Upstream series:
https://lore.kernel.org/lkml/20261001-b4-prep-gcov-v1-0-794792e06f24@virtuozzo.com/
https://virtuozzo.atlassian.net/browse/VSTOR-148131
Signed-off-by: Konstantin Khorenko <khorenko@virtuozzo.com>
---
Konstantin Khorenko (2):
ms/kbuild: use $(CFLAGS_GCOV) in the prefer-atomic try-run test
ms/kbuild: move GCOV flags to scripts/Makefile.gcov
MAINTAINERS | 1 +
Makefile | 22 +---------------------
scripts/Makefile.gcov | 21 +++++++++++++++++++++
3 files changed, 23 insertions(+), 21 deletions(-)
---
base-commit: 8026fb5599f945a36a6911f8febad3ab569176da
change-id: 20261019-b4-prep-khorenko-vstor-148131-gcov-followups-697f640b297e
Best regards,
--
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-10-19 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 18:26 Konstantin Khorenko [this message]
2026-10-19 18:26 ` [Devel] [PATCH hci-8.1 1/2] ms/kbuild: use $(CFLAGS_GCOV) in the prefer-atomic try-run test Konstantin Khorenko
2026-10-19 18:29 ` no-reply
2026-10-19 18:26 ` [Devel] [PATCH hci-8.1 2/2] ms/kbuild: move GCOV flags to scripts/Makefile.gcov Konstantin Khorenko
2026-10-19 18:30 ` no-reply
2026-10-19 19:54 ` [Devel] [PATCH hci-8.1 0/2] ms/kbuild: GCOV follow-ups to the prefer-atomic fix Konstantin Khorenko
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=20261019-b4-prep-khorenko-vstor-148131-gcov-followups-v1-0-2932ec685608@virtuozzo.com \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
/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