linux-um archives
 help / color / mirror / Atom feed
From: Mariia Nikitash <nikitash.mariiaw@gmail.com>
To: richard@nod.at, anton.ivanov@cambridgegreys.com,
	johannes@sipsolutions.net, alex.hung@amd.com,
	linux-um@lists.infradead.org
Cc: Mariia Nikitash <nikitash.mariiaw@gmail.com>
Subject: Re: [PATCH] um: fix CONFIG_GCOV for built-in code
Date: Tue, 22 Sep 2026 22:05:10 -0700	[thread overview]
Message-ID: <20260923050510.204386-1-nikitash.mariiaw@gmail.com> (raw)
In-Reply-To: <20260727195515.2306731-1-alex.hung@amd.com>

Hi Alex,

I tested this while investigating GCC/GCOV coverage under UML using KUnit.

Tested on:
  Architecture: x86_64 UML
  Kernel: v7.3-rc3-61-gbc77531b2a6f
  KUnit configs: default.config + coverage_uml.config
  Compilers: GCC 13.3.0 and GCC 16.2.0

With GCC 13.3, the unpatched tree produced 731 .gcno files and
0 .gcda files after the KUnit run. With the patch applied, the
same run produced 731 .gcno files and 704 .gcda files, and LCOV
was able to generate coverage successfully.

I also reproduced the same result with GCC 16.2:

  without patch: 731 .gcno / 0 .gcda
  with patch:    731 .gcno / 704 .gcda

LCOV coverage generation also completed successfully with GCC 16.2.

Tested-by: Mariia Nikitash <nikitash.mariiaw@gmail.com>

Thanks,
Mariia


  parent reply	other threads:[~2026-09-23  5:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 19:55 [PATCH] um: fix CONFIG_GCOV for built-in code Alex Hung
2026-08-10 13:51 ` Alex Hung
2026-08-21 15:25   ` Alex Hung
2026-09-23  5:05 ` Mariia Nikitash [this message]
2026-09-24  3:42 ` Kees Cook
2026-09-28 18:09   ` Johannes Berg

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=20260923050510.204386-1-nikitash.mariiaw@gmail.com \
    --to=nikitash.mariiaw@gmail.com \
    --cc=alex.hung@amd.com \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-um@lists.infradead.org \
    --cc=richard@nod.at \
    /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