search for: kcov_remot

Displaying 3 results from an estimated 3 matches for "kcov_remot".

Did you mean: kcov_remote
2019 Oct 21
0
[PATCH RFC 1/3] kcov: remote coverage support
On Thu, Oct 17, 2019 at 7:44 PM Andrey Konovalov <andreyknvl at google.com> wrote: > > Currently kcov can only collect coverage for syscalls that are issued > from the current process. This patch adds support for KCOV_REMOTE_ENABLE, > that makes it possible to collect coverage for arbitrary parts of the > kernel code, provided that this part is annotated with kcov_remote_start > and kcov_remote_stop. Nitpick: () after function names is the common C style. > This allows to collect coverage from two types...
2019 Oct 24
0
[PATCH v2 1/3] kcov: remote coverage support
On Wed, Oct 23, 2019 at 5:24 PM Andrey Konovalov <andreyknvl at google.com> wrote: > > This patch adds background thread coverage collection ability to kcov. ... > +static struct kcov_remote *kcov_remote_add(struct kcov *kcov, u64 handle) > +{ > + struct kcov_remote *remote; > + > + if (kcov_remote_find(handle)) > + return ERR_PTR(-EEXIST); > + remote = kmalloc(sizeof(*remote), GFP_ATOMIC); > + if (!remote) > +...
2019 Oct 23
0
[PATCH v2 1/3] kcov: remote coverage support
On Wed, 23 Oct 2019 17:24:29 +0200 Andrey Konovalov <andreyknvl at google.com> wrote: > This patch adds background thread coverage collection ability to kcov. > > With KCOV_ENABLE coverage is collected only for syscalls that are issued > from the current process. With KCOV_REMOTE_ENABLE it's possible to collect > coverage for arbitrary parts of the kernel code, provided that those parts > are annotated with kcov_remote_start()/kcov_remote_stop(). > > This allows to collect coverage from two types of kernel background > threads: the global ones, that are...