[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1460759535-22403-1-git-send-email-hcochran@kernelspring.com>
Date: Fri, 15 Apr 2016 18:32:10 -0400
From: Howard Cochran <hcochran@...nelspring.com>
To: linux-kernel@...r.kernel.org
Cc: Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>,
Howard Cochran <cochran@...mark.com>
Subject: [PATCH v2 0/5] tracing: Make event triggers affect correct instance
This is version 2 of the patches to make tracing event triggers affect
the correct instance rather than always the top-level instance. The sum
of these patches is identical to version 1, but this version fixes an
error in patch #1 that the kbuild test robot found.
Original Description:
Although all of the trace event triggers can be used in instances, most
of them affect the top-level instance even when triggered from within an
instance. This patch set makes them affect the instance in which the
trigger occurred. The enable_event & disable_event triggers already work
within the correct instance, so these are unchanged.
The same problem also exists with the function probe triggers, but they
will be fixed in a later patch set.
Patch 1 is preparatory.
Patch 2 fixes the stacktrace event trigger
Patch 3 fixes the traceon & traceoff event triggers
Patch 4 fixes the snapshot event trigger
Patch 5 Makes related warning messages also go to the correct instance
kernel/trace/trace.c | 96 +++++++++++++++++++++++++------------
kernel/trace/trace.h | 14 +++++-
kernel/trace/trace_events_trigger.c | 62 ++++++++++++++----------
3 files changed, 113 insertions(+), 59 deletions(-)
Powered by blists - more mailing lists