From: Howard Cochran <hcochran@kernelspring.com>
To: linux-kernel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Howard Cochran <cochran@lexmark.com>
Subject: [PATCHSET] tracing: Make event triggers affect correct instance
Date: Fri, 15 Apr 2016 02:53:45 -0400 [thread overview]
Message-ID: <1460703230-13307-1-git-send-email-hcochran@kernelspring.com> (raw)
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(-)
next reply other threads:[~2016-04-15 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 6:53 Howard Cochran [this message]
2016-04-15 6:53 ` [PATCH 1/5] tracing: Add param to event_trigger_ops.func() for instances Howard Cochran
2016-04-15 7:10 ` kbuild test robot
2016-04-15 6:53 ` [PATCH 2/5] tracing: Make stacktrace trigger affect the correct instance Howard Cochran
2016-04-15 6:53 ` [PATCH 3/5] tracing: Make traceon, traceoff " Howard Cochran
2016-04-15 6:53 ` [PATCH 4/5] tracing: Make snapshot " Howard Cochran
2016-04-15 6:53 ` [PATCH 5/5] tracing: Make internal_trace_puts() write to " Howard Cochran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1460703230-13307-1-git-send-email-hcochran@kernelspring.com \
--to=hcochran@kernelspring.com \
--cc=cochran@lexmark.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).