Re: [PATCH v2 06/11] kcov: x86: introduce CONFIG_KCOV_UNIQUE

From: Peter Zijlstra
Date: Fri Jun 27 2025 - 04:12:11 EST


On Thu, Jun 26, 2025 at 03:41:53PM +0200, Alexander Potapenko wrote:
> The new config switches coverage instrumentation to using
> __sanitizer_cov_trace_pc_guard(u32 *guard)
> instead of
> __sanitizer_cov_trace_pc(void)
>
> This relies on Clang's -fsanitize-coverage=trace-pc-guard flag [1].
>
> Each callback receives a unique 32-bit guard variable residing in the
> __sancov_guards section. Those guards can be used by kcov to deduplicate
> the coverage on the fly.

This sounds like a *LOT* of data; how big is this for a typical kernel
build?