search for: common_handl

...Multiple ids can be targeted with the same > kcov device simultaneously. > > Since there might be many local background threads spawned from different > userspace processes, we can't use a single global id per annotation. > Instead, the userspace process passes an id through the common_handle > field of the kcov_remote_arg struct. This id gets saved to the kcov_handle > field in the current task_struct and needs to be passed to the newly > spawned threads via custom annotations. Those threads should be in turn > annotated with kcov_remote_start/kcov_remote_stop. > > S...

...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. > - Change common_handle type to u32. > - Add checks for handle validity into kcov_ioctl_locked() and > kcov_remote_start(). > - Updated documentation to reflect the changes. > > Andrey Konovalov (3): > kcov: remote coverage support > usb, kcov: collect coverage from hub_event > vhost, kc...

...e > sections, that are referenced by those handles. > > Since there might be many local background threads spawned from different > userspace processes, we can't use a single global handle per annotation. > Instead, the userspace process passes a non-zero handle through the > common_handle field of the kcov_remote_arg struct. This common handle gets > saved to the kcov_handle field in the current task_struct and needs to be > passed to the newly spawned threads via custom annotations. Those threads > should in turn be annotated with kcov_remote_start()/kcov_remote_stop(). &...