search for: kcov_remote_start

...Konovalov <andreyknvl at google.com> wrote: > > On Wed, Oct 23, 2019 at 10:36 AM Dmitry Vyukov <dvyukov at google.com> wrote: > > > > On Tue, Oct 22, 2019 at 6:46 PM Andrey Konovalov <andreyknvl at google.com> wrote: > > > > > > This patch adds kcov_remote_start()/kcov_remote_stop() annotations to the > > > vhost_worker() function, which is responsible for processing vhost works. > > > Since vhost_worker() threads are spawned per vhost device instance > > > the common kcov handle is used for kcov_remote_start()/stop() annotations...

...rote: > > 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 kernel background > threads: the global ones, that are spawned during kernel boot and are > always running (e.g. USB hub_event); and the local ones, that...

On Thu, Oct 17, 2019 at 07:44:15PM +0200, Andrey Konovalov wrote: > This patch adds kcov_remote_start/kcov_remote_stop annotations to the > vhost_worker function, which is responsible for processing vhost works. > Since vhost_worker is spawned when a vhost device instance is created, > the common kcov handle is used for kcov_remote_start/stop annotations. > > Signed-off-by: Andrey K...

On Thu, Oct 17, 2019 at 07:44:14PM +0200, Andrey Konovalov wrote: > This patch adds kcov_remote_start/kcov_remote_stop annotations to the > hub_event function, which is responsible for processing events on USB > buses, in particular events that happen during USB device enumeration. > Each USB bus gets a unique id, which can be used to attach a kcov device > to a particular USB bus for c...

On Thu, Oct 17, 2019 at 09:00:18PM +0200, Andrey Konovalov wrote: > On Thu, Oct 17, 2019 at 8:18 PM Greg Kroah-Hartman > <gregkh at linuxfoundation.org> wrote: > > > > On Thu, Oct 17, 2019 at 07:44:15PM +0200, Andrey Konovalov wrote: > > > This patch adds kcov_remote_start/kcov_remote_stop annotations to the > > > vhost_worker function, which is responsible for processing vhost works. > > > Since vhost_worker is spawned when a vhost device instance is created, > > > the common kcov handle is used for kcov_remote_start/stop annotations. >...

On Tue, Oct 22, 2019 at 6:46 PM Andrey Konovalov <andreyknvl at google.com> wrote: > > This patch adds kcov_remote_start()/kcov_remote_stop() annotations to the > vhost_worker() function, which is responsible for processing vhost works. > Since vhost_worker() threads are spawned per vhost device instance > the common kcov handle is used for kcov_remote_start()/stop() annotations > (see Documentation/dev-t...

On Thu, Oct 17, 2019 at 09:06:56PM +0200, Andrey Konovalov wrote: > On Thu, Oct 17, 2019 at 8:19 PM Greg Kroah-Hartman > <gregkh at linuxfoundation.org> wrote: > > > > On Thu, Oct 17, 2019 at 07:44:14PM +0200, Andrey Konovalov wrote: > > > This patch adds kcov_remote_start/kcov_remote_stop annotations to the > > > hub_event function, which is responsible for processing events on USB > > > buses, in particular events that happen during USB device enumeration. > > > Each USB bus gets a unique id, which can be used to attach a kcov device >...

...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 spawned during kernel boot and are > always running (e.g. USB hub_event()); and the local ones, that are > spawned when a user interacts with some kerne...

...w.googlesource.com/c/linux/kernel/git/torvalds/linux/+/1524 Oh, so much easier to review with side-by-side diffs, context and smart in-line colouring! > Changes from RFC v1: > - Remove unnecessary #ifdef's from drivers/vhost/vhost.c. > - Reset t->kcov when area allocation fails in kcov_remote_start(). > - Use struct_size to calculate array size in kcov_ioctl(). > - Add a limit on area_size in kcov_remote_arg. > - Added kcov_disable() helper. > - Changed encoding of kcov remote handle ids, see the documentation. > - Added a comment reference for kcov_sequence task_struct field....

...indly add following tag Reported-by: kbuild test robot <lkp at intel.com> All errors (new ones prefixed by >>): >> ERROR: "kcov_common_handle" [drivers/vhost/vhost.ko] undefined! ERROR: "kcov_remote_stop" [drivers/vhost/vhost.ko] undefined! ERROR: "kcov_remote_start" [drivers/vhost/vhost.ko] undefined! ERROR: "kcov_remote_stop" [drivers/usb/core/usbcore.ko] undefined! ERROR: "kcov_remote_start" [drivers/usb/core/usbcore.ko] undefined! --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists...

...GCC_VERSION=7.4.0 make.cross ARCH=s390 If you fix the issue, kindly add following tag Reported-by: kbuild test robot <lkp at intel.com> All errors (new ones prefixed by >>): >> ERROR: "kcov_remote_stop" [drivers/usb/core/usbcore.ko] undefined! >> ERROR: "kcov_remote_start" [drivers/usb/core/usbcore.ko] undefined! --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation -------------- next part -------------- A non-text attachment was scrubbed... Name: .config...

...t;lock); > + kcov_debug("t = %px, kcov->t = %px\n", t, kcov->t); > + /* > + * If !kcov->remote, this checks that t->kcov->t == t. > + * If kcov->remote == true then the exiting task is either: > + * 1. a remote task between kcov_remote_start() and kcov_remote_stop(), > + * in this case t != kcov->t and we'll print a warning; or Why? Is kcov->t == NULL for remote kcov's? May be worth mentioning in the comment b/c it's a very condensed form to check lots of different things at once. Otherwise the series l...

On Tue, Oct 29, 2019 at 05:32:28PM +0100, Andrey Konovalov wrote: > This patch adds kcov_remote_start()/kcov_remote_stop() annotations to the > hub_event() function, which is responsible for processing events on USB > buses, in particular events that happen during USB device enumeration. > Since hub_event() is run in a global background kernel thread (see > Documentation/dev-tools/kcov....