Re: [PATCHv2] kcov: reject open when kernel not instrumented

2016-06-16 Thread Mark Rutland
On Thu, Jun 16, 2016 at 11:09:37AM +0100, James Morse wrote: > Hi Mark, > > On 15/06/16 18:04, Mark Rutland wrote: > > If the toolchain does not support -fsanitize-coverage=trace-pc, we blat > > this option from CFLAGS_KCOV, and build the kernel without > > instrumentation, even if CONFIG_KCOV was

Re: [PATCHv2] kcov: reject open when kernel not instrumented

2016-06-16 Thread James Morse
Hi Mark, On 15/06/16 18:04, Mark Rutland wrote: > If the toolchain does not support -fsanitize-coverage=trace-pc, we blat > this option from CFLAGS_KCOV, and build the kernel without > instrumentation, even if CONFIG_KCOV was selected. However, we still > build the rest of the kcov infrastructure,

Re: [PATCHv2] kcov: reject open when kernel not instrumented

2016-06-15 Thread Dmitry Vyukov
On Wed, Jun 15, 2016 at 7:04 PM, Mark Rutland wrote: > If the toolchain does not support -fsanitize-coverage=trace-pc, we blat > this option from CFLAGS_KCOV, and build the kernel without > instrumentation, even if CONFIG_KCOV was selected. However, we still > build the rest of the kcov infrastruc

[PATCHv2] kcov: reject open when kernel not instrumented

2016-06-15 Thread Mark Rutland
If the toolchain does not support -fsanitize-coverage=trace-pc, we blat this option from CFLAGS_KCOV, and build the kernel without instrumentation, even if CONFIG_KCOV was selected. However, we still build the rest of the kcov infrastructure, and expose a kcov file under debugfs. This can be confus