Displaying 3 results from an estimated 3 matches for "kcov_remote_en".
Did you mean:
kcov_remote_id
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 of k...
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 spa...
2019 Oct 17
0
[PATCH RFC 2/3] usb, kcov: collect coverage from hub_event
...return KCOV_REMOTE_HANDLE_USB + (__u64)bus;
> > > +}
> >
> > Why is this function in a uapi .h file? What userspace code would call
> > this?
>
> A userspace process that wants to collect coverage from USB bus # N
> needs to pass kcov_remote_handle_usb(N) into KCOV_REMOTE_ENABLE ioctl.
Ugh, ok. Then you should make "unsigned int bus" a __u64 so that this
actually will work on all kernels properly.
thanks,
greg k-h