"trace-cmd reset" command should put all ftrace config to its default
state, but trace cpumask was not reseted. The patch sets cpumask to
its default value - all CPUs are enabled for tracing.
Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@xxxxxxxxx>
---
tracecmd/trace-record.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/tracecmd/trace-record.c b/tracecmd/trace-record.c
index 69de82a..c41f55f 100644
--- a/tracecmd/trace-record.c
+++ b/tracecmd/trace-record.c
@@ -4096,6 +4096,24 @@ static void reset_clock(void)
write_instance_file(instance, "trace_clock", "local", "clock");
}
+static void reset_cpu_mask(void)
+{
+ char str[24];
+ int cpumask = 0;
+ int cpus = count_cpus();
+ struct buffer_instance *instance;
+
+ while (cpus--) {
+ cpumask <<= 1;
+ cpumask |= 1;
+ }
+ if (snprintf(str, 24, "%x", cpumask) <= 0)
+ return;
+
+ for_all_instances(instance)
+ write_instance_file(instance, "tracing_cpumask", str, "cpumask");
+}
+
static void reset_event_pid(void)
{
add_event_pid("");
@@ -4808,6 +4826,7 @@ void trace_reset(int argc, char **argv)
reset_clock();
reset_event_pid();
reset_max_latency_instance();
+ reset_cpu_mask();
tracecmd_remove_instances();
clear_func_filters();
/* restore tracing_on to 1 */
--
2.21.0
|