From: Jiri Olsa <jolsa@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>,
Mike Galbraith <efault@gmx.de>, David Ahern <dsahern@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: [PATCHv2 0/7] perf tools: Add data file write interface
Date: Thu, 28 Nov 2013 11:30:12 +0100 [thread overview]
Message-ID: <1385634619-8129-1-git-send-email-jolsa@redhat.com> (raw)
hi,
adding perf_data_file__write function to centralize
output file writes. Using it in record and inject
commands.
v2 changes:
- changes for readn function, suggested by Ingo
- added writen function, suggested by Arnaldo
- spliting record change into 2 separated patches
- omiting some unnecessary changes in the inject change
thanks,
jirka
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Mike Galbraith <efault@gmx.de>
Cc: David Ahern <dsahern@gmail.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>
---
Jiri Olsa (7):
perf record: Unify data output code into perf_record__write function
perf tools: Use correct return type for readn function
perf tools: Fine tune readn function
perf tools: Add writen function
perf tools: Add perf_data_file__write interface
perf record: Use perf_data_file__write for output file
perf inject: Handle output file via perf_data_file object
tools/perf/builtin-inject.c | 65 +++++++++++++++++++++++++++--------------------------------------
tools/perf/builtin-record.c | 41 +++++++++++++----------------------------
tools/perf/util/data.c | 6 ++++++
tools/perf/util/data.h | 14 ++++++++------
tools/perf/util/header.c | 18 +++++++++---------
tools/perf/util/session.c | 2 +-
tools/perf/util/util.c | 32 ++++++++++++++++++++++++++------
tools/perf/util/util.h | 3 ++-
8 files changed, 92 insertions(+), 89 deletions(-)
next reply other threads:[~2013-11-28 10:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 10:30 Jiri Olsa [this message]
2013-11-28 10:30 ` [PATCH 1/7] perf record: Unify data output code into perf_record__write function Jiri Olsa
2013-12-04 15:40 ` [tip:perf/core] " tip-bot for Jiri Olsa
2013-11-28 10:30 ` [PATCH 2/7] perf tools: Use correct return type for readn function Jiri Olsa
2013-12-04 15:40 ` [tip:perf/core] " tip-bot for Jiri Olsa
2013-11-28 10:30 ` [PATCH 3/7] perf tools: Fine tune " Jiri Olsa
2013-11-28 15:19 ` David Ahern
2013-11-28 15:43 ` [PATCHv3 " Jiri Olsa
2013-11-28 16:03 ` David Ahern
2013-12-04 15:40 ` [tip:perf/core] " tip-bot for Jiri Olsa
2013-11-28 10:30 ` [PATCH 4/7] perf tools: Add writen function Jiri Olsa
2013-12-04 15:40 ` [tip:perf/core] " tip-bot for Jiri Olsa
2013-11-28 10:30 ` [PATCH 5/7] perf tools: Add perf_data_file__write interface Jiri Olsa
2013-12-04 15:40 ` [tip:perf/core] " tip-bot for Jiri Olsa
2013-11-28 10:30 ` [PATCH 6/7] perf record: Use perf_data_file__write for output file Jiri Olsa
2013-11-28 14:03 ` Arnaldo Carvalho de Melo
2013-11-28 15:21 ` [PATCHv3 " Jiri Olsa
2013-11-28 10:30 ` [PATCH 7/7] perf inject: Handle output file via perf_data_file object Jiri Olsa
2013-11-28 14:14 ` Arnaldo Carvalho de Melo
2013-11-28 15:30 ` Jiri Olsa
2013-11-28 10:36 ` [PATCHv2 0/7] perf tools: Add data file write interface Jiri Olsa
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=1385634619-8129-1-git-send-email-jolsa@redhat.com \
--to=jolsa@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@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
all inboxes | Powered by JetHome®