From: Jakub Kicinski <kuba@kernel.org>
To: Florian Westphal <fw@strlen.de>
Cc: allison.henderson@oracle.com, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, rds-devel@oss.oracle.com,
linux-rdma@vger.kernel.org, oberpar@linux.ibm.com,
chuck.lever@oracle.com, vegard.nossum@oracle.com
Subject: Re: [PATCH net-next v1 2/3] net: rds: add option for GCOV profiling
Date: Thu, 27 Jun 2024 16:28:08 -0700 [thread overview]
Message-ID: <20240627162808.015c25a7@kernel.org> (raw)
In-Reply-To: <20240626012834.5678-3-allison.henderson@oracle.com>
On Tue, 25 Jun 2024 18:28:33 -0700 allison.henderson@oracle.com wrote:
> From: Vegard Nossum <vegard.nossum@oracle.com>
>
> To better our unit tests we need code coverage to be part of the kernel.
> This patch borrows heavily from how CONFIG_GCOV_PROFILE_FTRACE is
> implemented
Hi Florian, IIRC you were able to generate test coverage reports for
nftables / netfilter. Is this the approach you used? I'm not sure how
well adding a Kconfig knob for every module would scale..
next prev parent reply other threads:[~2024-06-27 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 1:28 [PATCH net-next v1 0/3] selftests: rds selftest allison.henderson
2024-06-26 1:28 ` [PATCH net-next v1 1/3] .gitignore: add .gcda files allison.henderson
2024-06-26 1:28 ` [PATCH net-next v1 2/3] net: rds: add option for GCOV profiling allison.henderson
2024-06-27 23:28 ` Jakub Kicinski [this message]
2024-06-26 1:28 ` [PATCH net-next v1 3/3] selftests: rds: add testing infrastructure allison.henderson
2024-06-27 23:32 ` Jakub Kicinski
2024-07-12 20:16 ` Allison Henderson
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=20240627162808.015c25a7@kernel.org \
--to=kuba@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=fw@strlen.de \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=rds-devel@oss.oracle.com \
--cc=vegard.nossum@oracle.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.