From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
David Sharp <dhsharp@google.com>,
Vaibhav Nagarnaik <vnagarnaik@google.com>,
hcochran@lexmark.com,
Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com>
Subject: [for-next][PATCH 0/2] tracing: Snapshot command line and branch tracer fix
Date: Fri, 08 Mar 2013 12:59:31 -0500 [thread overview]
Message-ID: <20130308175931.135352630@goodmis.org> (raw)
Two more patches to my queue. I added alloc_snapshot to the kernel
command line parameter to alloc allocation of the snapshot buffer
when the main tracing buffer is allocated, allowing the use of
tracing_snapshot() without the fear of it not being allocated.
Also Fengguang Wu's tests discovered that my changes broke the branch
tracer. I guess I should add that to my test suite ;-)
Steven Rostedt (Red Hat) (2):
tracing: Add alloc_snapshot kernel command line parameter
tracing: Fix the branch tracer that broke with buffer change
----
Documentation/kernel-parameters.txt | 7 +++
kernel/trace/trace.c | 81 +++++++++++++++++++++--------------
kernel/trace/trace.h | 2 +-
kernel/trace/trace_branch.c | 4 +-
kernel/trace/trace_events.c | 4 +-
5 files changed, 60 insertions(+), 38 deletions(-)
next reply other threads:[~2013-03-08 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 17:59 Steven Rostedt [this message]
2013-03-08 17:59 ` [for-next][PATCH 1/2] tracing: Add alloc_snapshot kernel command line parameter Steven Rostedt
2013-03-08 17:59 ` [for-next][PATCH 2/2] tracing: Fix the branch tracer that broke with buffer change Steven Rostedt
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=20130308175931.135352630@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=dhsharp@google.com \
--cc=fweisbec@gmail.com \
--cc=hcochran@lexmark.com \
--cc=hiraku.toyooka.gu@hitachi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=vnagarnaik@google.com \
/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
all inboxes | Powered by JetHome®