From: tip-bot for Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, paulus@samba.org, hpa@zytor.com,
mingo@redhat.com, a.p.zijlstra@chello.nl,
mitake@dcl.info.waseda.ac.jp, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:perf/bench] perf bench: Add format constants to bench.h for unified output formatting
Date: Tue, 10 Nov 2009 04:22:04 GMT [thread overview]
Message-ID: <tip-242aa14a67f4e19453fc8a51cffc5ac5ee5bcbd1@git.kernel.org> (raw)
In-Reply-To: <1257808802-9420-2-git-send-email-mitake@dcl.info.waseda.ac.jp>
Commit-ID: 242aa14a67f4e19453fc8a51cffc5ac5ee5bcbd1
Gitweb: http://git.kernel.org/tip/242aa14a67f4e19453fc8a51cffc5ac5ee5bcbd1
Author: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
AuthorDate: Tue, 10 Nov 2009 08:19:59 +0900
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Tue, 10 Nov 2009 04:53:48 +0100
perf bench: Add format constants to bench.h for unified output formatting
This patch adds some constants and extern declaration to
bench.h. These are used for unified output formatting
of 'perf bench'.
Signed-off-by: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>
LKML-Reference: <1257808802-9420-2-git-send-email-mitake@dcl.info.waseda.ac.jp>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
tools/perf/bench/bench.h | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/tools/perf/bench/bench.h b/tools/perf/bench/bench.h
index 59adb27..42167ea 100644
--- a/tools/perf/bench/bench.h
+++ b/tools/perf/bench/bench.h
@@ -6,4 +6,13 @@ extern int bench_sched_messaging(int argc, const char **argv,
extern int bench_sched_pipe(int argc, const char **argv,
const char *prefix);
+#define BENCH_FORMAT_DEFAULT_STR "default"
+#define BENCH_FORMAT_DEFAULT 0
+#define BENCH_FORMAT_SIMPLE_STR "simple"
+#define BENCH_FORMAT_SIMPLE 1
+
+#define BENCH_FORMAT_UNKNOWN -1
+
+extern int bench_format;
+
#endif
next prev parent reply other threads:[~2009-11-10 4:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 23:19 [PATCH v2 0/4] perf bench: Common option for specifying style formatting Hitoshi Mitake
2009-11-09 23:19 ` [PATCH v2 1/4] perf bench: Add stuffs to bench.h for unified output formatting Hitoshi Mitake
2009-11-10 4:22 ` tip-bot for Hitoshi Mitake [this message]
2009-11-09 23:20 ` [PATCH v2 2/4] perf bench: Modify builtin-bench.c for processing common options Hitoshi Mitake
2009-11-10 4:22 ` [tip:perf/bench] " tip-bot for Hitoshi Mitake
2009-11-09 23:20 ` [PATCH v2 3/4] perf bench: Modified bench/bench-messaging.c to adopt unified output formatting Hitoshi Mitake
2009-11-10 4:22 ` [tip:perf/bench] perf bench: Modify " tip-bot for Hitoshi Mitake
2009-11-09 23:20 ` [PATCH v2 4/4] perf bench: Modify builtin-pipe.c for processing common options Hitoshi Mitake
2009-11-10 4:22 ` [tip:perf/bench] " tip-bot for Hitoshi Mitake
2009-11-10 3:58 ` [PATCH v2 0/4] perf bench: Common option for specifying style formatting Ingo Molnar
2009-11-10 7:51 ` Hitoshi Mitake
2009-11-10 8:01 ` Ingo Molnar
2009-11-10 8:23 ` Hitoshi Mitake
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=tip-242aa14a67f4e19453fc8a51cffc5ac5ee5bcbd1@git.kernel.org \
--to=mitake@dcl.info.waseda.ac.jp \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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