From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Mikhail Zaslonko <zaslonko@linux.ibm.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Konstantin Khorenko <khorenko@virtuozzo.com>
Subject: [PATCH 0/2] kbuild: GCOV cleanups following the prefer-atomic fix
Date: Thu, 01 Oct 2026 18:57:10 +0200 [thread overview]
Message-ID: <20261001-b4-prep-gcov-v1-0-794792e06f24@virtuozzo.com> (raw)
Two cleanups Peter Oberparleiter suggested while reviewing
commit 56cb9b7d96b2 ("gcov: use atomic counter updates to fix
concurrent access crashes"):
https://lore.kernel.org/e1b6e768-51af-468b-a729-0ed3fceef2f1@linux.ibm.com
Patch 1 makes the prefer-atomic try-run test reuse $(CFLAGS_GCOV)
instead of spelling the flags out again, so the test compiles with the
exact GCOV flags, -fno-tree-loop-im included.
Patch 2 moves the CFLAGS_GCOV block into scripts/Makefile.gcov,
included via include-$(CONFIG_GCOV_KERNEL) like the other
instrumentation makefiles. The try-run also stops running on builds
without GCOV.
Signed-off-by: Konstantin Khorenko <khorenko@virtuozzo.com>
---
Konstantin Khorenko (2):
kbuild: use $(CFLAGS_GCOV) in the prefer-atomic try-run test
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: 551c722f40809618230001baccf219193e22fc5a
change-id: 20261001-b4-prep-gcov-82edd7efd6b9
Best regards,
--
Konstantin Khorenko <khorenko@virtuozzo.com>
next reply other threads:[~2026-10-01 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 16:57 Konstantin Khorenko [this message]
2026-10-01 16:57 ` [PATCH 1/2] kbuild: use $(CFLAGS_GCOV) in the prefer-atomic try-run test Konstantin Khorenko
2026-10-01 16:57 ` [PATCH 2/2] kbuild: move GCOV flags to scripts/Makefile.gcov Konstantin Khorenko
2026-10-06 8:24 ` [PATCH 0/2] kbuild: GCOV cleanups following the prefer-atomic fix Peter Oberparleiter
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=20261001-b4-prep-gcov-v1-0-794792e06f24@virtuozzo.com \
--to=khorenko@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=zaslonko@linux.ibm.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
all inboxes | Powered by JetHome®