Ashok Raj e272d1e118 platform/x86/intel/ifs: Add current batch number to trace output ... Add the current batch number in the trace output. When there are failures, it's important to know which test content resulted in failure. # TASK-PID CPU# ||||| TIMESTAMP FUNCTION # | | | ||||| | | migration/0-18 [000] d..1. 527287.084668: ifs_status: batch: 02, start: 0000, stop: 007f, status: 0000000000007f80 migration/128-785 [128] d..1. 527287.084669: ifs_status: batch: 02, start: 0000, stop: 007f, status: 0000000000007f80 Signed-off-by: Ashok Raj <ashok.raj@intel.com> Reviewed-by: Tony Luck <tony.luck@intel.com> Link: https://lore.kernel.org/r/20240125082254.424859-4-ashok.raj@intel.com Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>		2024-01-31 11:57:27 +02:00
..
events	platform/x86/intel/ifs: Add current batch number to trace output	2024-01-31 11:57:27 +02:00
misc	NFSD: add CB_RECALL_ANY tracepoints	2022-12-10 11:01:12 -05:00
stages	tracing: Error if a trace event has an array for a __field()	2023-04-03 11:52:51 -04:00
bpf_probe.h	kernel.h: split out COUNT_ARGS() and CONCATENATE() to args.h	2023-08-18 10:18:56 -07:00
define_custom_trace.h
define_trace.h
perf.h	perf/tracing: Use stage6 of tracing to not duplicate macros	2023-01-25 10:31:24 -05:00
syscall.h
trace_custom_events.h	tracing: Rename the staging files for trace_events	2022-04-02 08:40:04 -04:00
trace_events.h	tracing: Rename the staging files for trace_events	2022-04-02 08:40:04 -04:00