From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org, 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>,
Stephane Eranian <eranian@google.com>,
David Ahern <dsahern@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH 2/3] perf record: Use perf_data_file__write for output file
Date: Mon, 25 Nov 2013 16:31:37 -0300 [thread overview]
Message-ID: <20131125193137.GB27323@ghostprotocols.net> (raw)
In-Reply-To: <1385130268-10664-3-git-send-email-jolsa@redhat.com>
Em Fri, Nov 22, 2013 at 03:24:27PM +0100, Jiri Olsa escreveu:
> Changing the file output code to use the newly
> added perf_data_file__write interface.
So I like renaming write_output() to perf_record__write(), but then
you're lumping together this change and the other, which is to make
write_output, now renamed to perf_record__write() to use perf_data_file.
Can you please split it like that?
- Arnaldo
> No functional change intended.
>
> 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: Stephane Eranian <eranian@google.com>
> Cc: David Ahern <dsahern@gmail.com>
> Cc: Adrian Hunter <adrian.hunter@intel.com>
> ---
> tools/perf/builtin-record.c | 42 +++++++++++++-----------------------------
> 1 file changed, 13 insertions(+), 29 deletions(-)
>
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 65615a8..bc3c7be 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -76,42 +76,27 @@ struct perf_record {
> long samples;
> };
>
> -static int do_write_output(struct perf_record *rec, void *buf, size_t size)
> +static ssize_t perf_record__write(struct perf_record *rec,
> + void *buf, size_t size)
> {
> - struct perf_data_file *file = &rec->file;
> -
> - while (size) {
> - ssize_t ret = write(file->fd, buf, size);
> -
> - if (ret < 0) {
> - pr_err("failed to write perf data, error: %m\n");
> - return -1;
> - }
> -
> - size -= ret;
> - buf += ret;
> + struct perf_session *session = rec->session;
> + ssize_t ret;
>
> - rec->bytes_written += ret;
> - }
> + ret = perf_data_file__write(session->file, buf, size);
> + if (ret < 0)
> + return -1;
>
> + rec->bytes_written += ret;
> return 0;
> }
>
> -static int write_output(struct perf_record *rec, void *buf, size_t size)
> -{
> - return do_write_output(rec, buf, size);
> -}
> -
> static int process_synthesized_event(struct perf_tool *tool,
> union perf_event *event,
> struct perf_sample *sample __maybe_unused,
> struct machine *machine __maybe_unused)
> {
> struct perf_record *rec = container_of(tool, struct perf_record, tool);
> - if (write_output(rec, event, event->header.size) < 0)
> - return -1;
> -
> - return 0;
> + return perf_record__write(rec, event, event->header.size);
> }
>
> static int perf_record__mmap_read(struct perf_record *rec,
> @@ -136,7 +121,7 @@ static int perf_record__mmap_read(struct perf_record *rec,
> size = md->mask + 1 - (old & md->mask);
> old += size;
>
> - if (write_output(rec, buf, size) < 0) {
> + if (perf_record__write(rec, buf, size) < 0) {
> rc = -1;
> goto out;
> }
> @@ -146,7 +131,7 @@ static int perf_record__mmap_read(struct perf_record *rec,
> size = head - old;
> old += size;
>
> - if (write_output(rec, buf, size) < 0) {
> + if (perf_record__write(rec, buf, size) < 0) {
> rc = -1;
> goto out;
> }
> @@ -322,8 +307,7 @@ static struct perf_event_header finished_round_event = {
>
> static int perf_record__mmap_read_all(struct perf_record *rec)
> {
> - int i;
> - int rc = 0;
> + int i, rc = 0;
>
> for (i = 0; i < rec->evlist->nr_mmaps; i++) {
> if (rec->evlist->mmap[i].base) {
> @@ -335,7 +319,7 @@ static int perf_record__mmap_read_all(struct perf_record *rec)
> }
>
> if (perf_header__has_feat(&rec->session->header, HEADER_TRACING_DATA))
> - rc = write_output(rec, &finished_round_event,
> + rc = perf_record__write(rec, &finished_round_event,
> sizeof(finished_round_event));
>
> out:
> --
> 1.8.3.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2013-11-25 19:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 14:24 [PATCH 0/3] perf tools: Add data file write interface Jiri Olsa
2013-11-22 14:24 ` [PATCH 1/3] perf tools: Add perf_data_file__write interface Jiri Olsa
2013-11-25 19:29 ` Arnaldo Carvalho de Melo
2013-11-26 10:17 ` Jiri Olsa
2013-11-26 17:53 ` [PATCH] tools/perf/util: Document and clean up readn() a bit Ingo Molnar
2013-11-27 8:38 ` Adrian Hunter
2013-11-27 11:57 ` Ingo Molnar
2013-11-27 15:19 ` David Ahern
2013-11-27 15:50 ` Jiri Olsa
2013-11-27 15:54 ` Ingo Molnar
2013-11-22 14:24 ` [PATCH 2/3] perf record: Use perf_data_file__write for output file Jiri Olsa
2013-11-25 19:31 ` Arnaldo Carvalho de Melo [this message]
2013-11-26 10:16 ` Jiri Olsa
2013-11-22 14:24 ` [PATCH 3/3] perf inject: Handle output file via perf_data_file object Jiri Olsa
2013-11-25 19:40 ` Arnaldo Carvalho de Melo
2013-11-26 10:03 ` Jiri Olsa
2013-11-26 12:42 ` Arnaldo Carvalho de Melo
2013-11-26 13:07 ` Jiri Olsa
2013-11-22 15:01 ` [PATCH 0/3] perf tools: Add data file write interface David Ahern
2013-11-23 9:44 ` Jiri Olsa
2013-11-24 0:00 ` David Ahern
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=20131125193137.GB27323@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.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