[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240627162808.015c25a7@kernel.org>
Date: Thu, 27 Jun 2024 16:28:08 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Florian Westphal <fw@...len.de>
Cc: allison.henderson@...cle.com, netdev@...r.kernel.org,
linux-kselftest@...r.kernel.org, rds-devel@....oracle.com,
linux-rdma@...r.kernel.org, oberpar@...ux.ibm.com, chuck.lever@...cle.com,
vegard.nossum@...cle.com
Subject: Re: [PATCH net-next v1 2/3] net: rds: add option for GCOV profiling
On Tue, 25 Jun 2024 18:28:33 -0700 allison.henderson@...cle.com wrote:
> From: Vegard Nossum <vegard.nossum@...cle.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..
Powered by blists - more mailing lists