public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Enable fine-grained kcov instrumentation
Date: Thu, 04 Aug 2016 14:49:17 +0300	[thread overview]
Message-ID: <1470311357.3633.55.camel@linux.intel.com> (raw)
In-Reply-To: <20160804063030.GF12611@nuc-i3427.alporthouse.com>

On to, 2016-08-04 at 07:30 +0100, Chris Wilson wrote:
> On Thu, Aug 04, 2016 at 09:12:07AM +0300, Joonas Lahtinen wrote:
> > 
> > On ke, 2016-08-03 at 20:38 +0100, Chris Wilson wrote:
> > > 
> > > In the next merge, we can build support for kcov at the individual file,
> > > or driver level. This is useful to filter out the noise when doing
> > > coverage test, i.e. we do get edges through code outside of i915.ko.
> > > 
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Umm, is not KCOV enabled by selecting KCOV and then instrumentation is
> > only disabled on select objects? "KCOV_INSTRUMENT_foo.o := n"?
> commit a4691deabf284a601149a067525759939cc563b2
> Author: Vegard Nossum <vegard.nossum@oracle.com>
> Date:   Tue Aug 2 14:07:30 2016 -0700
> 
>     kcov: allow more fine-grained coverage instrumentation
>     
>     For more targeted fuzzing, it's better to disable kernel-wide
>     instrumentation and instead enable it on a per-subsystem basis.  This
>     follows the pattern of UBSAN and allows you to compile in the kcov
>     driver without instrumenting the whole kernel.
>     
>     To instrument a part of the kernel, you can use either
>     
>         # for a single file in the current directory
>         KCOV_INSTRUMENT_filename.o := y
>     
>     or
>     
>         # for all the files in the current directory (excluding subdirectories)
>         KCOV_INSTRUMENT := y
>     
>     or
>     
>         # (same as above)
>         ccflags-y += $(CFLAGS_KCOV)
>     
>     or
>     
>         # for all the files in the current directory (including subdirectories)
>         subdir-ccflags-y += $(CFLAGS_KCOV)
> 
> 
> The commit itself adds KCOV_INSTRUMENT_ALL config target to enable
> kernel-wide coverage, with KCOV then just enabling the debug interface.

Could reference the patch in commit message if you especially want this
reviewed upfront. I see it could be merged after we get the commit to
our tree, too.

Regards, Joonas

> -Chris
> 
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-08-04 11:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03 19:38 [PATCH] drm/i915: Enable fine-grained kcov instrumentation Chris Wilson
2016-08-04  5:30 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-08-04  6:12 ` [PATCH] " Joonas Lahtinen
2016-08-04  6:30   ` Chris Wilson
2016-08-04 11:49     ` Joonas Lahtinen [this message]
2016-08-04 11:52       ` Chris Wilson
2016-08-04  7:12 ` Jani Nikula
2017-07-24 14:50 ` Chris Wilson
2017-07-24 14:50 ` Chris Wilson

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=1470311357.3633.55.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /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