Displaying 3 results from an estimated 3 matches for "task_stru".
Did you mean:
task_str
2007 Aug 20
3
[PATCH 2/4] Introduce a new fields "gtime" and "cgtime" in task_struct and signal_struct
[PATCH 2/4] like for cpustat, introduce the "gtime" (guest time of the task=
) and
"cgtime" (guest time of the task children) fields for the
tasks. Modify signal_struct and task_struct. Modify /proc/<pid>/stat to dis=
play
these new fields.
Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net>
-- =
------------- Laurent.Vivier@bull.net --------------
"Software is hard" - Donald Knuth
-------------- next part --------------
Index: kvm/fs/proc...
2007 Aug 20
3
[PATCH 2/4] Introduce a new fields "gtime" and "cgtime" in task_struct and signal_struct
[PATCH 2/4] like for cpustat, introduce the "gtime" (guest time of the task=
) and
"cgtime" (guest time of the task children) fields for the
tasks. Modify signal_struct and task_struct. Modify /proc/<pid>/stat to dis=
play
these new fields.
Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net>
-- =
------------- Laurent.Vivier@bull.net --------------
"Software is hard" - Donald Knuth
-------------- next part --------------
Index: kvm/fs/proc...
2019 Oct 21
0
[PATCH RFC 1/3] kcov: remote coverage support
...ackground 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.
>
> Signed-off-by: Andrey Konovalov <andreyknvl at google.com>
> ---
> Documentation/dev-tools/kcov.rst | 99...