From: nicolas.pitre@linaro.org (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] generic IPI tracing
Date: Fri, 25 Jul 2014 16:05:28 -0400 [thread overview]
Message-ID: <1406318733-26754-1-git-send-email-nicolas.pitre@linaro.org> (raw)
This is v2 of the series initially posted here:
http://news.gmane.org/group/gmane.linux.kernel/thread=1750391
Steven / Ingo: Would you please merge those patches in your tree for some
linux-next exposure and mainline inclusion? Patches 1 to 4 may go in now.
I'm unsure about patch 5 so I'll leave it to your appreciation.
Changes since v1:
- added empty tracepoint_string when !CONFIG_TRACING, from Steven
- ipi_types[] is unconditionally marked with __tracepoint_string now
- added comment to arch/x86/kernel/smp.c justifying the #undef's
- collected ACKs, refined commit logs
diffstat:
arch/arm/kernel/smp.c | 70 ++++++++++++++++++------------
arch/arm64/kernel/smp.c | 65 +++++++++++++++++-----------
arch/x86/kernel/smp.c | 20 +++++++++
include/linux/ftrace_event.h | 10 +++++
include/trace/events/ipi.h | 89 ++++++++++++++++++++++++++++++++++++++
5 files changed, 200 insertions(+), 54 deletions(-)
Nicolas
next reply other threads:[~2014-07-25 20:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 20:05 Nicolas Pitre [this message]
2014-07-25 20:05 ` [PATCH v2 1/5] tracing: Do not do anything special with tracepoint_string when tracing is disabled Nicolas Pitre
2014-08-08 2:35 ` Steven Rostedt
2014-08-08 3:05 ` Nicolas Pitre
2014-07-25 20:05 ` [PATCH v2 2/5] tracepoint: add generic tracepoint definitions for IPI tracing Nicolas Pitre
2014-07-25 20:05 ` [PATCH v2 3/5] ARM: add IPI tracepoints Nicolas Pitre
2014-07-28 5:34 ` Daniel Lezcano
2014-08-06 19:51 ` Steven Rostedt
2014-07-25 20:05 ` [PATCH v2 4/5] ARM64: " Nicolas Pitre
2014-08-06 19:52 ` Steven Rostedt
2014-08-06 20:28 ` Nicolas Pitre
2014-08-07 9:18 ` Will Deacon
2014-08-07 15:18 ` Steven Rostedt
2014-07-25 20:05 ` [PATCH v2 5/5] X86: " Nicolas Pitre
2014-08-07 15:33 ` 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=1406318733-26754-1-git-send-email-nicolas.pitre@linaro.org \
--to=nicolas.pitre@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).