License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 17:07:57 +03:00
/* SPDX-License-Identifier: GPL-2.0 */
2009-07-13 06:33:21 +04:00
# undef TRACE_SYSTEM
# define TRACE_SYSTEM sched
2009-04-10 16:54:16 +04:00
# if !defined(_TRACE_SCHED_H) || defined(TRACE_HEADER_MULTI_READ)
tracing, sched: LTTng instrumentation - scheduler
Instrument the scheduler activity (sched_switch, migration, wakeups,
wait for a task, signal delivery) and process/thread
creation/destruction (fork, exit, kthread stop). Actually, kthread
creation is not instrumented in this patch because it is architecture
dependent. It allows to connect tracers such as ftrace which detects
scheduling latencies, good/bad scheduler decisions. Tools like LTTng can
export this scheduler information along with instrumentation of the rest
of the kernel activity to perform post-mortem analysis on the scheduler
activity.
About the performance impact of tracepoints (which is comparable to
markers), even without immediate values optimizations, tests done by
Hideo Aoki on ia64 show no regression. His test case was using hackbench
on a kernel where scheduler instrumentation (about 5 events in code
scheduler code) was added. See the "Tracepoints" patch header for
performance result detail.
Changelog :
- Change instrumentation location and parameter to match ftrace
instrumentation, previously done with kernel markers.
[ mingo@elte.hu: conflict resolutions ]
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Acked-by: 'Peter Zijlstra' <peterz@infradead.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2008-07-18 20:16:17 +04:00
# define _TRACE_SCHED_H
2020-12-15 06:03:14 +03:00
# include <linux/kthread.h>
2017-02-08 20:51:31 +03:00
# include <linux/sched/numa_balancing.h>
tracing, sched: LTTng instrumentation - scheduler
Instrument the scheduler activity (sched_switch, migration, wakeups,
wait for a task, signal delivery) and process/thread
creation/destruction (fork, exit, kthread stop). Actually, kthread
creation is not instrumented in this patch because it is architecture
dependent. It allows to connect tracers such as ftrace which detects
scheduling latencies, good/bad scheduler decisions. Tools like LTTng can
export this scheduler information along with instrumentation of the rest
of the kernel activity to perform post-mortem analysis on the scheduler
activity.
About the performance impact of tracepoints (which is comparable to
markers), even without immediate values optimizations, tests done by
Hideo Aoki on ia64 show no regression. His test case was using hackbench
on a kernel where scheduler instrumentation (about 5 events in code
scheduler code) was added. See the "Tracepoints" patch header for
performance result detail.
Changelog :
- Change instrumentation location and parameter to match ftrace
instrumentation, previously done with kernel markers.
[ mingo@elte.hu: conflict resolutions ]
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Acked-by: 'Peter Zijlstra' <peterz@infradead.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2008-07-18 20:16:17 +04:00
# include <linux/tracepoint.h>
2012-02-07 20:11:05 +04:00
# include <linux/binfmts.h>
tracing, sched: LTTng instrumentation - scheduler
Instrument the scheduler activity (sched_switch, migration, wakeups,
wait for a task, signal delivery) and process/thread
creation/destruction (fork, exit, kthread stop). Actually, kthread
creation is not instrumented in this patch because it is architecture
dependent. It allows to connect tracers such as ftrace which detects
scheduling latencies, good/bad scheduler decisions. Tools like LTTng can
export this scheduler information along with instrumentation of the rest
of the kernel activity to perform post-mortem analysis on the scheduler
activity.
About the performance impact of tracepoints (which is comparable to
markers), even without immediate values optimizations, tests done by
Hideo Aoki on ia64 show no regression. His test case was using hackbench
on a kernel where scheduler instrumentation (about 5 events in code
scheduler code) was added. See the "Tracepoints" patch header for
performance result detail.
Changelog :
- Change instrumentation location and parameter to match ftrace
instrumentation, previously done with kernel markers.
[ mingo@elte.hu: conflict resolutions ]
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Acked-by: 'Peter Zijlstra' <peterz@infradead.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2008-07-18 20:16:17 +04:00
2009-04-10 16:54:16 +04:00
/*
* Tracepoint for calling kthread_stop , performed to end a kthread :
*/
TRACE_EVENT ( sched_kthread_stop ,
TP_PROTO ( struct task_struct * t ) ,
TP_ARGS ( t ) ,
TP_STRUCT__entry (
__array ( char , comm , TASK_COMM_LEN )
__field ( pid_t , pid )
) ,
TP_fast_assign (
memcpy ( __entry - > comm , t - > comm , TASK_COMM_LEN ) ;
__entry - > pid = t - > pid ;
) ,
events: Harmonize event field names and print output names
Now that we can filter based on fields via perf record, people
will start using filter expressions and will expect them to
be obvious.
The primary way to see which fields are available is by looking
at the trace output, such as:
gcc-18676 [000] 343.011728: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.012727: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.032692: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.033690: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.034687: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.035686: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.036684: irq_handler_entry: irq=0 handler=timer
While 'irq==0' filters work, the 'handler==<x>' filter expression
does not work:
$ perf record -R -f -a -e irq:irq_handler_entry --filter handler=timer sleep 1
Error: failed to set filter with 22 (Invalid argument)
The problem is that while an 'irq' field exists and is recognized
as a filter field - 'handler' does not exist - its name is 'name'
in the output.
To solve this, we need to synchronize the printout and the field
names, wherever possible.
In cases where the printout prints a non-field, we enclose
that information in square brackets, such as:
perf-1380 [013] 724.903505: softirq_exit: vec=9 [action=RCU]
perf-1380 [013] 724.904482: softirq_exit: vec=1 [action=TIMER]
This way users can use filter expressions more intuitively: all
fields that show up as 'primary' (non-bracketed) information is
filterable.
This patch harmonizes the field names for all irq, bkl, power,
sched and timer events.
We might in fact think about dropping the print format bit of
generic tracepoints altogether, and just print the fields that
are being recorded.
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-10-15 13:50:39 +04:00
TP_printk ( " comm=%s pid=%d " , __entry - > comm , __entry - > pid )
2009-04-10 16:54:16 +04:00
) ;
/*
* Tracepoint for the return value of the kthread stopping :
*/
TRACE_EVENT ( sched_kthread_stop_ret ,
TP_PROTO ( int ret ) ,
TP_ARGS ( ret ) ,
TP_STRUCT__entry (
__field ( int , ret )
) ,
TP_fast_assign (
__entry - > ret = ret ;
) ,
events: Harmonize event field names and print output names
Now that we can filter based on fields via perf record, people
will start using filter expressions and will expect them to
be obvious.
The primary way to see which fields are available is by looking
at the trace output, such as:
gcc-18676 [000] 343.011728: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.012727: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.032692: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.033690: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.034687: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.035686: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.036684: irq_handler_entry: irq=0 handler=timer
While 'irq==0' filters work, the 'handler==<x>' filter expression
does not work:
$ perf record -R -f -a -e irq:irq_handler_entry --filter handler=timer sleep 1
Error: failed to set filter with 22 (Invalid argument)
The problem is that while an 'irq' field exists and is recognized
as a filter field - 'handler' does not exist - its name is 'name'
in the output.
To solve this, we need to synchronize the printout and the field
names, wherever possible.
In cases where the printout prints a non-field, we enclose
that information in square brackets, such as:
perf-1380 [013] 724.903505: softirq_exit: vec=9 [action=RCU]
perf-1380 [013] 724.904482: softirq_exit: vec=1 [action=TIMER]
This way users can use filter expressions more intuitively: all
fields that show up as 'primary' (non-bracketed) information is
filterable.
This patch harmonizes the field names for all irq, bkl, power,
sched and timer events.
We might in fact think about dropping the print format bit of
generic tracepoints altogether, and just print the fields that
are being recorded.
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-10-15 13:50:39 +04:00
TP_printk ( " ret=%d " , __entry - > ret )
2009-04-10 16:54:16 +04:00
) ;
2020-12-15 06:03:14 +03:00
/**
* sched_kthread_work_queue_work - called when a work gets queued
* @ worker : pointer to the kthread_worker
* @ work : pointer to struct kthread_work
*
* This event occurs when a work is queued immediately or once a
* delayed work is actually queued ( ie : once the delay has been
* reached ) .
*/
TRACE_EVENT ( sched_kthread_work_queue_work ,
TP_PROTO ( struct kthread_worker * worker ,
struct kthread_work * work ) ,
TP_ARGS ( worker , work ) ,
TP_STRUCT__entry (
__field ( void * , work )
__field ( void * , function )
__field ( void * , worker )
) ,
TP_fast_assign (
__entry - > work = work ;
__entry - > function = work - > func ;
__entry - > worker = worker ;
) ,
TP_printk ( " work struct=%p function=%ps worker=%p " ,
__entry - > work , __entry - > function , __entry - > worker )
) ;
/**
* sched_kthread_work_execute_start - called immediately before the work callback
* @ work : pointer to struct kthread_work
*
* Allows to track kthread work execution .
*/
TRACE_EVENT ( sched_kthread_work_execute_start ,
TP_PROTO ( struct kthread_work * work ) ,
TP_ARGS ( work ) ,
TP_STRUCT__entry (
__field ( void * , work )
__field ( void * , function )
) ,
TP_fast_assign (
__entry - > work = work ;
__entry - > function = work - > func ;
) ,
TP_printk ( " work struct %p: function %ps " , __entry - > work , __entry - > function )
) ;
/**
* sched_kthread_work_execute_end - called immediately after the work callback
* @ work : pointer to struct work_struct
* @ function : pointer to worker function
*
* Allows to track workqueue execution .
*/
TRACE_EVENT ( sched_kthread_work_execute_end ,
TP_PROTO ( struct kthread_work * work , kthread_work_func_t function ) ,
TP_ARGS ( work , function ) ,
TP_STRUCT__entry (
__field ( void * , work )
__field ( void * , function )
) ,
TP_fast_assign (
__entry - > work = work ;
__entry - > function = function ;
) ,
TP_printk ( " work struct %p: function %ps " , __entry - > work , __entry - > function )
) ;
2009-04-10 16:54:16 +04:00
/*
* Tracepoint for waking up a task :
*/
2009-11-26 11:04:55 +03:00
DECLARE_EVENT_CLASS ( sched_wakeup_template ,
2009-04-10 16:54:16 +04:00
2015-06-09 12:13:36 +03:00
TP_PROTO ( struct task_struct * p ) ,
2009-04-10 16:54:16 +04:00
2015-06-09 12:13:36 +03:00
TP_ARGS ( __perf_task ( p ) ) ,
2009-04-10 16:54:16 +04:00
TP_STRUCT__entry (
__array ( char , comm , TASK_COMM_LEN )
__field ( pid_t , pid )
__field ( int , prio )
events: Harmonize event field names and print output names
Now that we can filter based on fields via perf record, people
will start using filter expressions and will expect them to
be obvious.
The primary way to see which fields are available is by looking
at the trace output, such as:
gcc-18676 [000] 343.011728: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.012727: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.032692: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.033690: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.034687: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.035686: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.036684: irq_handler_entry: irq=0 handler=timer
While 'irq==0' filters work, the 'handler==<x>' filter expression
does not work:
$ perf record -R -f -a -e irq:irq_handler_entry --filter handler=timer sleep 1
Error: failed to set filter with 22 (Invalid argument)
The problem is that while an 'irq' field exists and is recognized
as a filter field - 'handler' does not exist - its name is 'name'
in the output.
To solve this, we need to synchronize the printout and the field
names, wherever possible.
In cases where the printout prints a non-field, we enclose
that information in square brackets, such as:
perf-1380 [013] 724.903505: softirq_exit: vec=9 [action=RCU]
perf-1380 [013] 724.904482: softirq_exit: vec=1 [action=TIMER]
This way users can use filter expressions more intuitively: all
fields that show up as 'primary' (non-bracketed) information is
filterable.
This patch harmonizes the field names for all irq, bkl, power,
sched and timer events.
We might in fact think about dropping the print format bit of
generic tracepoints altogether, and just print the fields that
are being recorded.
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-10-15 13:50:39 +04:00
__field ( int , target_cpu )
2009-04-10 16:54:16 +04:00
) ,
TP_fast_assign (
memcpy ( __entry - > comm , p - > comm , TASK_COMM_LEN ) ;
__entry - > pid = p - > pid ;
2017-03-23 17:56:12 +03:00
__entry - > prio = p - > prio ; /* XXX SCHED_DEADLINE */
events: Harmonize event field names and print output names
Now that we can filter based on fields via perf record, people
will start using filter expressions and will expect them to
be obvious.
The primary way to see which fields are available is by looking
at the trace output, such as:
gcc-18676 [000] 343.011728: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.012727: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.032692: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.033690: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.034687: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.035686: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.036684: irq_handler_entry: irq=0 handler=timer
While 'irq==0' filters work, the 'handler==<x>' filter expression
does not work:
$ perf record -R -f -a -e irq:irq_handler_entry --filter handler=timer sleep 1
Error: failed to set filter with 22 (Invalid argument)
The problem is that while an 'irq' field exists and is recognized
as a filter field - 'handler' does not exist - its name is 'name'
in the output.
To solve this, we need to synchronize the printout and the field
names, wherever possible.
In cases where the printout prints a non-field, we enclose
that information in square brackets, such as:
perf-1380 [013] 724.903505: softirq_exit: vec=9 [action=RCU]
perf-1380 [013] 724.904482: softirq_exit: vec=1 [action=TIMER]
This way users can use filter expressions more intuitively: all
fields that show up as 'primary' (non-bracketed) information is
filterable.
This patch harmonizes the field names for all irq, bkl, power,
sched and timer events.
We might in fact think about dropping the print format bit of
generic tracepoints altogether, and just print the fields that
are being recorded.
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-10-15 13:50:39 +04:00
__entry - > target_cpu = task_cpu ( p ) ;
2009-04-10 16:54:16 +04:00
) ,
2015-06-09 12:13:36 +03:00
TP_printk ( " comm=%s pid=%d prio=%d target_cpu=%03d " ,
2009-04-10 16:54:16 +04:00
__entry - > comm , __entry - > pid , __entry - > prio ,
2015-06-09 12:13:36 +03:00
__entry - > target_cpu )
2009-04-10 16:54:16 +04:00
) ;
2015-06-09 12:13:36 +03:00
/*
* Tracepoint called when waking a task ; this tracepoint is guaranteed to be
* called from the waking context .
*/
DEFINE_EVENT ( sched_wakeup_template , sched_waking ,
TP_PROTO ( struct task_struct * p ) ,
TP_ARGS ( p ) ) ;
/*
2021-03-23 20:49:35 +03:00
* Tracepoint called when the task is actually woken ; p - > state = = TASK_RUNNING .
2020-07-16 04:31:38 +03:00
* It is not always called from the waking context .
2015-06-09 12:13:36 +03:00
*/
2009-11-19 04:48:08 +03:00
DEFINE_EVENT ( sched_wakeup_template , sched_wakeup ,
2015-06-09 12:13:36 +03:00
TP_PROTO ( struct task_struct * p ) ,
TP_ARGS ( p ) ) ;
2009-11-19 04:48:08 +03:00
2009-04-10 16:54:16 +04:00
/*
* Tracepoint for waking up a new task :
*/
2009-11-19 04:48:08 +03:00
DEFINE_EVENT ( sched_wakeup_template , sched_wakeup_new ,
2015-06-09 12:13:36 +03:00
TP_PROTO ( struct task_struct * p ) ,
TP_ARGS ( p ) ) ;
2009-04-10 16:54:16 +04:00
2010-05-31 20:13:25 +04:00
# ifdef CREATE_TRACE_POINTS
2022-01-20 19:25:19 +03:00
static inline long __trace_sched_switch_state ( bool preempt ,
unsigned int prev_state ,
struct task_struct * p )
2010-05-31 20:13:25 +04:00
{
2018-10-30 09:54:33 +03:00
unsigned int state ;
2014-10-07 23:51:08 +04:00
# ifdef CONFIG_SCHED_DEBUG
BUG_ON ( p ! = current ) ;
# endif /* CONFIG_SCHED_DEBUG */
2015-09-28 19:06:56 +03:00
2010-05-31 20:13:25 +04:00
/*
2015-09-28 19:06:56 +03:00
* Preemption ignores task state , therefore preempted tasks are always
* RUNNING ( we will not have dequeued if state ! = RUNNING ) .
2010-05-31 20:13:25 +04:00
*/
2017-09-22 19:19:53 +03:00
if ( preempt )
2017-11-22 15:05:48 +03:00
return TASK_REPORT_MAX ;
2017-09-22 19:19:53 +03:00
2018-10-30 09:54:33 +03:00
/*
* task_state_index ( ) uses fls ( ) and returns a value from 0 - 8 range .
* Decrement it by 1 ( except TASK_RUNNING state i . e 0 ) before using
* it for left shift operation to get the correct task - > state
* mapping .
*/
2022-01-20 19:25:19 +03:00
state = __task_state_index ( prev_state , p - > exit_state ) ;
2018-10-30 09:54:33 +03:00
return state ? ( 1 < < ( state - 1 ) ) : state ;
2010-05-31 20:13:25 +04:00
}
2014-10-07 23:51:08 +04:00
# endif /* CREATE_TRACE_POINTS */
2010-05-31 20:13:25 +04:00
2009-04-10 16:54:16 +04:00
/*
* Tracepoint for task switches , performed by the scheduler :
*/
TRACE_EVENT ( sched_switch ,
2015-09-28 19:06:56 +03:00
TP_PROTO ( bool preempt ,
struct task_struct * prev ,
2022-05-11 21:28:36 +03:00
struct task_struct * next ,
unsigned int prev_state ) ,
2009-04-10 16:54:16 +04:00
2022-05-11 21:28:36 +03:00
TP_ARGS ( preempt , prev , next , prev_state ) ,
2009-04-10 16:54:16 +04:00
TP_STRUCT__entry (
__array ( char , prev_comm , TASK_COMM_LEN )
__field ( pid_t , prev_pid )
__field ( int , prev_prio )
2009-05-15 18:51:13 +04:00
__field ( long , prev_state )
2009-04-10 16:54:16 +04:00
__array ( char , next_comm , TASK_COMM_LEN )
__field ( pid_t , next_pid )
__field ( int , next_prio )
) ,
TP_fast_assign (
memcpy ( __entry - > next_comm , next - > comm , TASK_COMM_LEN ) ;
__entry - > prev_pid = prev - > pid ;
__entry - > prev_prio = prev - > prio ;
2022-01-20 19:25:19 +03:00
__entry - > prev_state = __trace_sched_switch_state ( preempt , prev_state , prev ) ;
2009-04-10 16:54:16 +04:00
memcpy ( __entry - > prev_comm , prev - > comm , TASK_COMM_LEN ) ;
__entry - > next_pid = next - > pid ;
__entry - > next_prio = next - > prio ;
2017-03-23 17:56:12 +03:00
/* XXX SCHED_DEADLINE */
2009-04-10 16:54:16 +04:00
) ,
2011-09-16 13:16:43 +04:00
TP_printk ( " prev_comm=%s prev_pid=%d prev_prio=%d prev_state=%s%s ==> next_comm=%s next_pid=%d next_prio=%d " ,
2009-04-10 16:54:16 +04:00
__entry - > prev_comm , __entry - > prev_pid , __entry - > prev_prio ,
2017-09-22 19:19:53 +03:00
2017-09-22 19:30:40 +03:00
( __entry - > prev_state & ( TASK_REPORT_MAX - 1 ) ) ?
__print_flags ( __entry - > prev_state & ( TASK_REPORT_MAX - 1 ) , " | " ,
2018-09-05 12:36:36 +03:00
{ TASK_INTERRUPTIBLE , " S " } ,
{ TASK_UNINTERRUPTIBLE , " D " } ,
{ __TASK_STOPPED , " T " } ,
{ __TASK_TRACED , " t " } ,
{ EXIT_DEAD , " X " } ,
{ EXIT_ZOMBIE , " Z " } ,
{ TASK_PARKED , " P " } ,
{ TASK_DEAD , " I " } ) :
2017-09-22 19:19:53 +03:00
" R " ,
2017-11-22 15:05:48 +03:00
__entry - > prev_state & TASK_REPORT_MAX ? " + " : " " ,
2009-04-10 16:54:16 +04:00
__entry - > next_comm , __entry - > next_pid , __entry - > next_prio )
) ;
/*
* Tracepoint for a task being migrated :
*/
TRACE_EVENT ( sched_migrate_task ,
2009-05-05 12:49:59 +04:00
TP_PROTO ( struct task_struct * p , int dest_cpu ) ,
2009-04-10 16:54:16 +04:00
2009-05-05 12:49:59 +04:00
TP_ARGS ( p , dest_cpu ) ,
2009-04-10 16:54:16 +04:00
TP_STRUCT__entry (
__array ( char , comm , TASK_COMM_LEN )
__field ( pid_t , pid )
__field ( int , prio )
__field ( int , orig_cpu )
__field ( int , dest_cpu )
) ,
TP_fast_assign (
memcpy ( __entry - > comm , p - > comm , TASK_COMM_LEN ) ;
__entry - > pid = p - > pid ;
2017-03-23 17:56:12 +03:00
__entry - > prio = p - > prio ; /* XXX SCHED_DEADLINE */
2009-05-05 12:49:59 +04:00
__entry - > orig_cpu = task_cpu ( p ) ;
2009-04-10 16:54:16 +04:00
__entry - > dest_cpu = dest_cpu ;
) ,
events: Harmonize event field names and print output names
Now that we can filter based on fields via perf record, people
will start using filter expressions and will expect them to
be obvious.
The primary way to see which fields are available is by looking
at the trace output, such as:
gcc-18676 [000] 343.011728: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.012727: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.032692: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.033690: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.034687: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.035686: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.036684: irq_handler_entry: irq=0 handler=timer
While 'irq==0' filters work, the 'handler==<x>' filter expression
does not work:
$ perf record -R -f -a -e irq:irq_handler_entry --filter handler=timer sleep 1
Error: failed to set filter with 22 (Invalid argument)
The problem is that while an 'irq' field exists and is recognized
as a filter field - 'handler' does not exist - its name is 'name'
in the output.
To solve this, we need to synchronize the printout and the field
names, wherever possible.
In cases where the printout prints a non-field, we enclose
that information in square brackets, such as:
perf-1380 [013] 724.903505: softirq_exit: vec=9 [action=RCU]
perf-1380 [013] 724.904482: softirq_exit: vec=1 [action=TIMER]
This way users can use filter expressions more intuitively: all
fields that show up as 'primary' (non-bracketed) information is
filterable.
This patch harmonizes the field names for all irq, bkl, power,
sched and timer events.
We might in fact think about dropping the print format bit of
generic tracepoints altogether, and just print the fields that
are being recorded.
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-10-15 13:50:39 +04:00
TP_printk ( " comm=%s pid=%d prio=%d orig_cpu=%d dest_cpu=%d " ,
2009-04-10 16:54:16 +04:00
__entry - > comm , __entry - > pid , __entry - > prio ,
__entry - > orig_cpu , __entry - > dest_cpu )
) ;
2009-11-26 11:04:55 +03:00
DECLARE_EVENT_CLASS ( sched_process_template ,
2009-04-10 16:54:16 +04:00
TP_PROTO ( struct task_struct * p ) ,
TP_ARGS ( p ) ,
TP_STRUCT__entry (
__array ( char , comm , TASK_COMM_LEN )
__field ( pid_t , pid )
__field ( int , prio )
) ,
TP_fast_assign (
memcpy ( __entry - > comm , p - > comm , TASK_COMM_LEN ) ;
__entry - > pid = p - > pid ;
2017-03-23 17:56:12 +03:00
__entry - > prio = p - > prio ; /* XXX SCHED_DEADLINE */
2009-04-10 16:54:16 +04:00
) ,
events: Harmonize event field names and print output names
Now that we can filter based on fields via perf record, people
will start using filter expressions and will expect them to
be obvious.
The primary way to see which fields are available is by looking
at the trace output, such as:
gcc-18676 [000] 343.011728: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.012727: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.032692: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.033690: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.034687: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.035686: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.036684: irq_handler_entry: irq=0 handler=timer
While 'irq==0' filters work, the 'handler==<x>' filter expression
does not work:
$ perf record -R -f -a -e irq:irq_handler_entry --filter handler=timer sleep 1
Error: failed to set filter with 22 (Invalid argument)
The problem is that while an 'irq' field exists and is recognized
as a filter field - 'handler' does not exist - its name is 'name'
in the output.
To solve this, we need to synchronize the printout and the field
names, wherever possible.
In cases where the printout prints a non-field, we enclose
that information in square brackets, such as:
perf-1380 [013] 724.903505: softirq_exit: vec=9 [action=RCU]
perf-1380 [013] 724.904482: softirq_exit: vec=1 [action=TIMER]
This way users can use filter expressions more intuitively: all
fields that show up as 'primary' (non-bracketed) information is
filterable.
This patch harmonizes the field names for all irq, bkl, power,
sched and timer events.
We might in fact think about dropping the print format bit of
generic tracepoints altogether, and just print the fields that
are being recorded.
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-10-15 13:50:39 +04:00
TP_printk ( " comm=%s pid=%d prio=%d " ,
2009-04-10 16:54:16 +04:00
__entry - > comm , __entry - > pid , __entry - > prio )
) ;
/*
2009-11-19 04:48:08 +03:00
* Tracepoint for freeing a task :
2009-04-10 16:54:16 +04:00
*/
2009-11-19 04:48:08 +03:00
DEFINE_EVENT ( sched_process_template , sched_process_free ,
TP_PROTO ( struct task_struct * p ) ,
TP_ARGS ( p ) ) ;
2009-04-10 16:54:16 +04:00
2009-11-19 04:48:08 +03:00
/*
* Tracepoint for a task exiting :
*/
DEFINE_EVENT ( sched_process_template , sched_process_exit ,
TP_PROTO ( struct task_struct * p ) ,
TP_ARGS ( p ) ) ;
2009-04-10 16:54:16 +04:00
2010-05-24 12:23:35 +04:00
/*
* Tracepoint for waiting on task to unschedule :
*/
DEFINE_EVENT ( sched_process_template , sched_wait_task ,
TP_PROTO ( struct task_struct * p ) ,
TP_ARGS ( p ) ) ;
2009-04-10 16:54:16 +04:00
/*
* Tracepoint for a waiting task :
*/
TRACE_EVENT ( sched_process_wait ,
TP_PROTO ( struct pid * pid ) ,
TP_ARGS ( pid ) ,
TP_STRUCT__entry (
__array ( char , comm , TASK_COMM_LEN )
__field ( pid_t , pid )
__field ( int , prio )
) ,
TP_fast_assign (
memcpy ( __entry - > comm , current - > comm , TASK_COMM_LEN ) ;
__entry - > pid = pid_nr ( pid ) ;
2017-03-23 17:56:12 +03:00
__entry - > prio = current - > prio ; /* XXX SCHED_DEADLINE */
2009-04-10 16:54:16 +04:00
) ,
events: Harmonize event field names and print output names
Now that we can filter based on fields via perf record, people
will start using filter expressions and will expect them to
be obvious.
The primary way to see which fields are available is by looking
at the trace output, such as:
gcc-18676 [000] 343.011728: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.012727: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.032692: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.033690: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.034687: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.035686: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.036684: irq_handler_entry: irq=0 handler=timer
While 'irq==0' filters work, the 'handler==<x>' filter expression
does not work:
$ perf record -R -f -a -e irq:irq_handler_entry --filter handler=timer sleep 1
Error: failed to set filter with 22 (Invalid argument)
The problem is that while an 'irq' field exists and is recognized
as a filter field - 'handler' does not exist - its name is 'name'
in the output.
To solve this, we need to synchronize the printout and the field
names, wherever possible.
In cases where the printout prints a non-field, we enclose
that information in square brackets, such as:
perf-1380 [013] 724.903505: softirq_exit: vec=9 [action=RCU]
perf-1380 [013] 724.904482: softirq_exit: vec=1 [action=TIMER]
This way users can use filter expressions more intuitively: all
fields that show up as 'primary' (non-bracketed) information is
filterable.
This patch harmonizes the field names for all irq, bkl, power,
sched and timer events.
We might in fact think about dropping the print format bit of
generic tracepoints altogether, and just print the fields that
are being recorded.
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-10-15 13:50:39 +04:00
TP_printk ( " comm=%s pid=%d prio=%d " ,
2009-04-10 16:54:16 +04:00
__entry - > comm , __entry - > pid , __entry - > prio )
) ;
/*
2021-01-11 13:48:07 +03:00
* Tracepoint for kernel_clone :
2009-04-10 16:54:16 +04:00
*/
TRACE_EVENT ( sched_process_fork ,
TP_PROTO ( struct task_struct * parent , struct task_struct * child ) ,
TP_ARGS ( parent , child ) ,
TP_STRUCT__entry (
__array ( char , parent_comm , TASK_COMM_LEN )
__field ( pid_t , parent_pid )
__array ( char , child_comm , TASK_COMM_LEN )
__field ( pid_t , child_pid )
) ,
TP_fast_assign (
memcpy ( __entry - > parent_comm , parent - > comm , TASK_COMM_LEN ) ;
__entry - > parent_pid = parent - > pid ;
memcpy ( __entry - > child_comm , child - > comm , TASK_COMM_LEN ) ;
__entry - > child_pid = child - > pid ;
) ,
events: Harmonize event field names and print output names
Now that we can filter based on fields via perf record, people
will start using filter expressions and will expect them to
be obvious.
The primary way to see which fields are available is by looking
at the trace output, such as:
gcc-18676 [000] 343.011728: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.012727: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.032692: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.033690: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.034687: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.035686: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.036684: irq_handler_entry: irq=0 handler=timer
While 'irq==0' filters work, the 'handler==<x>' filter expression
does not work:
$ perf record -R -f -a -e irq:irq_handler_entry --filter handler=timer sleep 1
Error: failed to set filter with 22 (Invalid argument)
The problem is that while an 'irq' field exists and is recognized
as a filter field - 'handler' does not exist - its name is 'name'
in the output.
To solve this, we need to synchronize the printout and the field
names, wherever possible.
In cases where the printout prints a non-field, we enclose
that information in square brackets, such as:
perf-1380 [013] 724.903505: softirq_exit: vec=9 [action=RCU]
perf-1380 [013] 724.904482: softirq_exit: vec=1 [action=TIMER]
This way users can use filter expressions more intuitively: all
fields that show up as 'primary' (non-bracketed) information is
filterable.
This patch harmonizes the field names for all irq, bkl, power,
sched and timer events.
We might in fact think about dropping the print format bit of
generic tracepoints altogether, and just print the fields that
are being recorded.
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-10-15 13:50:39 +04:00
TP_printk ( " comm=%s pid=%d child_comm=%s child_pid=%d " ,
2009-04-10 16:54:16 +04:00
__entry - > parent_comm , __entry - > parent_pid ,
__entry - > child_comm , __entry - > child_pid )
) ;
2012-02-07 20:11:05 +04:00
/*
* Tracepoint for exec :
*/
TRACE_EVENT ( sched_process_exec ,
TP_PROTO ( struct task_struct * p , pid_t old_pid ,
struct linux_binprm * bprm ) ,
TP_ARGS ( p , old_pid , bprm ) ,
TP_STRUCT__entry (
__string ( filename , bprm - > filename )
__field ( pid_t , pid )
__field ( pid_t , old_pid )
) ,
TP_fast_assign (
__assign_str ( filename , bprm - > filename ) ;
__entry - > pid = p - > pid ;
2012-03-30 20:26:36 +04:00
__entry - > old_pid = old_pid ;
2012-02-07 20:11:05 +04:00
) ,
TP_printk ( " filename=%s pid=%d old_pid=%d " , __get_str ( filename ) ,
__entry - > pid , __entry - > old_pid )
) ;
2019-03-26 15:13:10 +03:00
# ifdef CONFIG_SCHEDSTATS
# define DEFINE_EVENT_SCHEDSTAT DEFINE_EVENT
# define DECLARE_EVENT_CLASS_SCHEDSTAT DECLARE_EVENT_CLASS
# else
# define DEFINE_EVENT_SCHEDSTAT DEFINE_EVENT_NOP
# define DECLARE_EVENT_CLASS_SCHEDSTAT DECLARE_EVENT_CLASS_NOP
# endif
2009-07-23 22:13:26 +04:00
/*
* XXX the below sched_stat tracepoints only apply to SCHED_OTHER / BATCH / IDLE
* adding sched_stat support to SCHED_FIFO / RR would be welcome .
*/
2019-03-26 15:13:10 +03:00
DECLARE_EVENT_CLASS_SCHEDSTAT ( sched_stat_template ,
2009-07-23 22:13:26 +04:00
TP_PROTO ( struct task_struct * tsk , u64 delay ) ,
2013-08-06 20:08:44 +04:00
TP_ARGS ( __perf_task ( tsk ) , __perf_count ( delay ) ) ,
2009-07-23 22:13:26 +04:00
TP_STRUCT__entry (
__array ( char , comm , TASK_COMM_LEN )
__field ( pid_t , pid )
__field ( u64 , delay )
) ,
TP_fast_assign (
memcpy ( __entry - > comm , tsk - > comm , TASK_COMM_LEN ) ;
__entry - > pid = tsk - > pid ;
__entry - > delay = delay ;
) ,
events: Harmonize event field names and print output names
Now that we can filter based on fields via perf record, people
will start using filter expressions and will expect them to
be obvious.
The primary way to see which fields are available is by looking
at the trace output, such as:
gcc-18676 [000] 343.011728: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.012727: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.032692: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.033690: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.034687: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.035686: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.036684: irq_handler_entry: irq=0 handler=timer
While 'irq==0' filters work, the 'handler==<x>' filter expression
does not work:
$ perf record -R -f -a -e irq:irq_handler_entry --filter handler=timer sleep 1
Error: failed to set filter with 22 (Invalid argument)
The problem is that while an 'irq' field exists and is recognized
as a filter field - 'handler' does not exist - its name is 'name'
in the output.
To solve this, we need to synchronize the printout and the field
names, wherever possible.
In cases where the printout prints a non-field, we enclose
that information in square brackets, such as:
perf-1380 [013] 724.903505: softirq_exit: vec=9 [action=RCU]
perf-1380 [013] 724.904482: softirq_exit: vec=1 [action=TIMER]
This way users can use filter expressions more intuitively: all
fields that show up as 'primary' (non-bracketed) information is
filterable.
This patch harmonizes the field names for all irq, bkl, power,
sched and timer events.
We might in fact think about dropping the print format bit of
generic tracepoints altogether, and just print the fields that
are being recorded.
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-10-15 13:50:39 +04:00
TP_printk ( " comm=%s pid=%d delay=%Lu [ns] " ,
2009-07-23 22:13:26 +04:00
__entry - > comm , __entry - > pid ,
( unsigned long long ) __entry - > delay )
) ;
2009-11-19 04:48:08 +03:00
/*
* Tracepoint for accounting wait time ( time the task is runnable
* but not actually running due to scheduler contention ) .
*/
2019-03-26 15:13:10 +03:00
DEFINE_EVENT_SCHEDSTAT ( sched_stat_template , sched_stat_wait ,
2009-11-19 04:48:08 +03:00
TP_PROTO ( struct task_struct * tsk , u64 delay ) ,
TP_ARGS ( tsk , delay ) ) ;
/*
* Tracepoint for accounting sleep time ( time the task is not runnable ,
* including iowait , see below ) .
*/
2019-03-26 15:13:10 +03:00
DEFINE_EVENT_SCHEDSTAT ( sched_stat_template , sched_stat_sleep ,
2009-11-26 10:08:01 +03:00
TP_PROTO ( struct task_struct * tsk , u64 delay ) ,
TP_ARGS ( tsk , delay ) ) ;
2009-11-19 04:48:08 +03:00
/*
* Tracepoint for accounting iowait time ( time the task is not runnable
* due to waiting on IO to complete ) .
*/
2019-03-26 15:13:10 +03:00
DEFINE_EVENT_SCHEDSTAT ( sched_stat_template , sched_stat_iowait ,
2009-11-26 10:08:01 +03:00
TP_PROTO ( struct task_struct * tsk , u64 delay ) ,
TP_ARGS ( tsk , delay ) ) ;
2009-11-19 04:48:08 +03:00
2011-11-28 13:03:35 +04:00
/*
* Tracepoint for accounting blocked time ( time the task is in uninterruptible ) .
*/
2019-03-26 15:13:10 +03:00
DEFINE_EVENT_SCHEDSTAT ( sched_stat_template , sched_stat_blocked ,
2011-11-28 13:03:35 +04:00
TP_PROTO ( struct task_struct * tsk , u64 delay ) ,
TP_ARGS ( tsk , delay ) ) ;
2009-09-13 20:15:54 +04:00
/*
* Tracepoint for accounting runtime ( time the task is executing
* on a CPU ) .
*/
2013-08-06 20:08:41 +04:00
DECLARE_EVENT_CLASS ( sched_stat_runtime ,
2009-09-13 20:15:54 +04:00
TP_PROTO ( struct task_struct * tsk , u64 runtime , u64 vruntime ) ,
2013-08-06 20:08:44 +04:00
TP_ARGS ( tsk , __perf_count ( runtime ) , vruntime ) ,
2009-09-13 20:15:54 +04:00
TP_STRUCT__entry (
__array ( char , comm , TASK_COMM_LEN )
__field ( pid_t , pid )
__field ( u64 , runtime )
__field ( u64 , vruntime )
) ,
TP_fast_assign (
memcpy ( __entry - > comm , tsk - > comm , TASK_COMM_LEN ) ;
__entry - > pid = tsk - > pid ;
__entry - > runtime = runtime ;
__entry - > vruntime = vruntime ;
) ,
events: Harmonize event field names and print output names
Now that we can filter based on fields via perf record, people
will start using filter expressions and will expect them to
be obvious.
The primary way to see which fields are available is by looking
at the trace output, such as:
gcc-18676 [000] 343.011728: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.012727: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.032692: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.033690: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.034687: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.035686: irq_handler_entry: irq=0 handler=timer
cc1-18677 [000] 343.036684: irq_handler_entry: irq=0 handler=timer
While 'irq==0' filters work, the 'handler==<x>' filter expression
does not work:
$ perf record -R -f -a -e irq:irq_handler_entry --filter handler=timer sleep 1
Error: failed to set filter with 22 (Invalid argument)
The problem is that while an 'irq' field exists and is recognized
as a filter field - 'handler' does not exist - its name is 'name'
in the output.
To solve this, we need to synchronize the printout and the field
names, wherever possible.
In cases where the printout prints a non-field, we enclose
that information in square brackets, such as:
perf-1380 [013] 724.903505: softirq_exit: vec=9 [action=RCU]
perf-1380 [013] 724.904482: softirq_exit: vec=1 [action=TIMER]
This way users can use filter expressions more intuitively: all
fields that show up as 'primary' (non-bracketed) information is
filterable.
This patch harmonizes the field names for all irq, bkl, power,
sched and timer events.
We might in fact think about dropping the print format bit of
generic tracepoints altogether, and just print the fields that
are being recorded.
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Tom Zanussi <tzanussi@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-10-15 13:50:39 +04:00
TP_printk ( " comm=%s pid=%d runtime=%Lu [ns] vruntime=%Lu [ns] " ,
2009-09-13 20:15:54 +04:00
__entry - > comm , __entry - > pid ,
( unsigned long long ) __entry - > runtime ,
( unsigned long long ) __entry - > vruntime )
) ;
2013-08-06 20:08:41 +04:00
DEFINE_EVENT ( sched_stat_runtime , sched_stat_runtime ,
TP_PROTO ( struct task_struct * tsk , u64 runtime , u64 vruntime ) ,
TP_ARGS ( tsk , runtime , vruntime ) ) ;
2010-09-20 23:13:34 +04:00
/*
* Tracepoint for showing priority inheritance modifying a tasks
* priority .
*/
TRACE_EVENT ( sched_pi_setprio ,
2017-03-23 17:56:12 +03:00
TP_PROTO ( struct task_struct * tsk , struct task_struct * pi_task ) ,
2010-09-20 23:13:34 +04:00
2017-03-23 17:56:12 +03:00
TP_ARGS ( tsk , pi_task ) ,
2010-09-20 23:13:34 +04:00
TP_STRUCT__entry (
__array ( char , comm , TASK_COMM_LEN )
__field ( pid_t , pid )
__field ( int , oldprio )
__field ( int , newprio )
) ,
TP_fast_assign (
memcpy ( __entry - > comm , tsk - > comm , TASK_COMM_LEN ) ;
__entry - > pid = tsk - > pid ;
__entry - > oldprio = tsk - > prio ;
2018-05-24 16:26:48 +03:00
__entry - > newprio = pi_task ?
min ( tsk - > normal_prio , pi_task - > prio ) :
tsk - > normal_prio ;
2017-03-23 17:56:12 +03:00
/* XXX SCHED_DEADLINE bits missing */
2010-09-20 23:13:34 +04:00
) ,
TP_printk ( " comm=%s pid=%d oldprio=%d newprio=%d " ,
__entry - > comm , __entry - > pid ,
__entry - > oldprio , __entry - > newprio )
) ;
2013-10-19 20:18:28 +04:00
# ifdef CONFIG_DETECT_HUNG_TASK
TRACE_EVENT ( sched_process_hang ,
TP_PROTO ( struct task_struct * tsk ) ,
TP_ARGS ( tsk ) ,
TP_STRUCT__entry (
__array ( char , comm , TASK_COMM_LEN )
__field ( pid_t , pid )
) ,
TP_fast_assign (
memcpy ( __entry - > comm , tsk - > comm , TASK_COMM_LEN ) ;
__entry - > pid = tsk - > pid ;
) ,
TP_printk ( " comm=%s pid=%d " , __entry - > comm , __entry - > pid )
) ;
# endif /* CONFIG_DETECT_HUNG_TASK */
2020-02-24 12:52:13 +03:00
/*
* Tracks migration of tasks from one runqueue to another . Can be used to
* detect if automatic NUMA balancing is bouncing between nodes .
*/
TRACE_EVENT ( sched_move_numa ,
2014-01-22 03:51:03 +04:00
TP_PROTO ( struct task_struct * tsk , int src_cpu , int dst_cpu ) ,
TP_ARGS ( tsk , src_cpu , dst_cpu ) ,
TP_STRUCT__entry (
__field ( pid_t , pid )
__field ( pid_t , tgid )
__field ( pid_t , ngid )
__field ( int , src_cpu )
__field ( int , src_nid )
__field ( int , dst_cpu )
__field ( int , dst_nid )
) ,
TP_fast_assign (
__entry - > pid = task_pid_nr ( tsk ) ;
__entry - > tgid = task_tgid_nr ( tsk ) ;
__entry - > ngid = task_numa_group_id ( tsk ) ;
__entry - > src_cpu = src_cpu ;
__entry - > src_nid = cpu_to_node ( src_cpu ) ;
__entry - > dst_cpu = dst_cpu ;
__entry - > dst_nid = cpu_to_node ( dst_cpu ) ;
) ,
TP_printk ( " pid=%d tgid=%d ngid=%d src_cpu=%d src_nid=%d dst_cpu=%d dst_nid=%d " ,
__entry - > pid , __entry - > tgid , __entry - > ngid ,
__entry - > src_cpu , __entry - > src_nid ,
__entry - > dst_cpu , __entry - > dst_nid )
) ;
2020-02-24 12:52:13 +03:00
DECLARE_EVENT_CLASS ( sched_numa_pair_template ,
2014-01-22 03:51:03 +04:00
TP_PROTO ( struct task_struct * src_tsk , int src_cpu ,
struct task_struct * dst_tsk , int dst_cpu ) ,
TP_ARGS ( src_tsk , src_cpu , dst_tsk , dst_cpu ) ,
TP_STRUCT__entry (
__field ( pid_t , src_pid )
__field ( pid_t , src_tgid )
__field ( pid_t , src_ngid )
__field ( int , src_cpu )
__field ( int , src_nid )
__field ( pid_t , dst_pid )
__field ( pid_t , dst_tgid )
__field ( pid_t , dst_ngid )
__field ( int , dst_cpu )
__field ( int , dst_nid )
) ,
TP_fast_assign (
__entry - > src_pid = task_pid_nr ( src_tsk ) ;
__entry - > src_tgid = task_tgid_nr ( src_tsk ) ;
__entry - > src_ngid = task_numa_group_id ( src_tsk ) ;
__entry - > src_cpu = src_cpu ;
__entry - > src_nid = cpu_to_node ( src_cpu ) ;
2020-02-24 12:52:13 +03:00
__entry - > dst_pid = dst_tsk ? task_pid_nr ( dst_tsk ) : 0 ;
__entry - > dst_tgid = dst_tsk ? task_tgid_nr ( dst_tsk ) : 0 ;
__entry - > dst_ngid = dst_tsk ? task_numa_group_id ( dst_tsk ) : 0 ;
2014-01-22 03:51:03 +04:00
__entry - > dst_cpu = dst_cpu ;
2020-02-24 12:52:13 +03:00
__entry - > dst_nid = dst_cpu > = 0 ? cpu_to_node ( dst_cpu ) : - 1 ;
2014-01-22 03:51:03 +04:00
) ,
TP_printk ( " src_pid=%d src_tgid=%d src_ngid=%d src_cpu=%d src_nid=%d dst_pid=%d dst_tgid=%d dst_ngid=%d dst_cpu=%d dst_nid=%d " ,
__entry - > src_pid , __entry - > src_tgid , __entry - > src_ngid ,
__entry - > src_cpu , __entry - > src_nid ,
__entry - > dst_pid , __entry - > dst_tgid , __entry - > dst_ngid ,
__entry - > dst_cpu , __entry - > dst_nid )
) ;
2014-06-04 21:31:15 +04:00
2020-02-24 12:52:13 +03:00
DEFINE_EVENT ( sched_numa_pair_template , sched_stick_numa ,
TP_PROTO ( struct task_struct * src_tsk , int src_cpu ,
struct task_struct * dst_tsk , int dst_cpu ) ,
TP_ARGS ( src_tsk , src_cpu , dst_tsk , dst_cpu )
) ;
DEFINE_EVENT ( sched_numa_pair_template , sched_swap_numa ,
TP_PROTO ( struct task_struct * src_tsk , int src_cpu ,
struct task_struct * dst_tsk , int dst_cpu ) ,
TP_ARGS ( src_tsk , src_cpu , dst_tsk , dst_cpu )
) ;
2014-06-04 21:31:15 +04:00
/*
* Tracepoint for waking a polling cpu without an IPI .
*/
TRACE_EVENT ( sched_wake_idle_without_ipi ,
TP_PROTO ( int cpu ) ,
TP_ARGS ( cpu ) ,
TP_STRUCT__entry (
__field ( int , cpu )
) ,
TP_fast_assign (
__entry - > cpu = cpu ;
) ,
TP_printk ( " cpu=%d " , __entry - > cpu )
) ;
2019-06-04 14:14:56 +03:00
/*
* Following tracepoints are not exported in tracefs and provide hooking
* mechanisms only for testing and debugging purposes .
*
* Postfixed with _tp to make them easily identifiable in the code .
*/
DECLARE_TRACE ( pelt_cfs_tp ,
TP_PROTO ( struct cfs_rq * cfs_rq ) ,
TP_ARGS ( cfs_rq ) ) ;
DECLARE_TRACE ( pelt_rt_tp ,
TP_PROTO ( struct rq * rq ) ,
TP_ARGS ( rq ) ) ;
DECLARE_TRACE ( pelt_dl_tp ,
TP_PROTO ( struct rq * rq ) ,
TP_ARGS ( rq ) ) ;
2020-02-22 03:52:05 +03:00
DECLARE_TRACE ( pelt_thermal_tp ,
TP_PROTO ( struct rq * rq ) ,
TP_ARGS ( rq ) ) ;
2019-06-04 14:14:56 +03:00
DECLARE_TRACE ( pelt_irq_tp ,
TP_PROTO ( struct rq * rq ) ,
TP_ARGS ( rq ) ) ;
2019-06-04 14:14:57 +03:00
DECLARE_TRACE ( pelt_se_tp ,
TP_PROTO ( struct sched_entity * se ) ,
TP_ARGS ( se ) ) ;
2020-08-28 12:00:49 +03:00
DECLARE_TRACE ( sched_cpu_capacity_tp ,
TP_PROTO ( struct rq * rq ) ,
TP_ARGS ( rq ) ) ;
2019-06-04 14:14:58 +03:00
DECLARE_TRACE ( sched_overutilized_tp ,
TP_PROTO ( struct root_domain * rd , bool overutilized ) ,
TP_ARGS ( rd , overutilized ) ) ;
2020-05-27 19:39:14 +03:00
DECLARE_TRACE ( sched_util_est_cfs_tp ,
TP_PROTO ( struct cfs_rq * cfs_rq ) ,
TP_ARGS ( cfs_rq ) ) ;
DECLARE_TRACE ( sched_util_est_se_tp ,
TP_PROTO ( struct sched_entity * se ) ,
TP_ARGS ( se ) ) ;
2020-06-29 22:23:03 +03:00
DECLARE_TRACE ( sched_update_nr_running_tp ,
TP_PROTO ( struct rq * rq , int change ) ,
TP_ARGS ( rq , change ) ) ;
2009-04-10 16:54:16 +04:00
# endif /* _TRACE_SCHED_H */
2009-04-10 17:36:00 +04:00
/* This part must be outside protection */
# include <trace/define_trace.h>
