From: Jiri Olsa <jolsa@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: acme@ghostprotocols.net, linux-kernel@vger.kernel.org, mingo@kernel.org
Subject: Re: [PATCH 0/4] perf record: Cleanups and mmap-based output
Date: Thu, 7 Nov 2013 14:21:18 +0100 [thread overview]
Message-ID: <20131107132118.GD1251@krava.brq.redhat.com> (raw)
In-Reply-To: <1383763297-27066-1-git-send-email-dsahern@gmail.com>
On Wed, Nov 06, 2013 at 11:41:33AM -0700, David Ahern wrote:
> I know Jiri is working on cleanups of the output file, but had this
> sitting around for a couple of weeks now. Might as well push it out
> for the next baseline. The cleanups of perf-record can be taken
> independently.
>
> Ingo: I took a look at leveraging the copy_user_nocache and was not able
> to get it to work. I won't have time to come back to it for a while.
> Given that the mmap output already improves perf-trace a lot I would
> like to get the option into 3.13 and come back to the optimization
> later.
>
> David Ahern (4):
> perf record: Refactor feature handling into a separate function
> perf record: Remove advance_output function
> perf record: Remove post_processing_offset variable
> perf record: mmap output file - v3
>
> tools/perf/Documentation/perf-record.txt | 5 ++
> tools/perf/builtin-record.c | 137 ++++++++++++++++++++++++++-----
> 2 files changed, 123 insertions(+), 19 deletions(-)
>
hi,
got this on F19:
CC builtin-record.o
builtin-record.c: In function ‘do_mmap_output’:
builtin-record.c:118:13: error: ignoring return value of ‘ftruncate’, declared with attribute warn_unused_result [-Werror=unused-result]
ftruncate(file->fd, offset);
^
cc1: all warnings being treated as errors
jirka
next prev parent reply other threads:[~2013-11-07 13:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 18:41 [PATCH 0/4] perf record: Cleanups and mmap-based output David Ahern
2013-11-06 18:41 ` [PATCH 1/4] perf record: Refactor feature handling into a separate function David Ahern
2013-11-07 8:03 ` Ingo Molnar
2013-11-07 15:30 ` [tip:perf/core] " tip-bot for David Ahern
2013-11-06 18:41 ` [PATCH 2/4] perf record: Remove advance_output function David Ahern
2013-11-07 8:04 ` Ingo Molnar
2013-11-07 15:31 ` [tip:perf/core] " tip-bot for David Ahern
2013-11-06 18:41 ` [PATCH 3/4] perf record: Remove post_processing_offset variable David Ahern
2013-11-07 8:04 ` Ingo Molnar
2013-11-07 15:31 ` [tip:perf/core] " tip-bot for David Ahern
2013-11-06 18:41 ` [PATCH 4/4] perf record: mmap output file - v3 David Ahern
2013-11-07 8:03 ` Ingo Molnar
2013-11-07 16:06 ` David Ahern
2013-11-11 11:53 ` Ingo Molnar
2013-11-07 8:06 ` [PATCH 0/4] perf record: Cleanups and mmap-based output Ingo Molnar
2013-11-07 9:38 ` Jiri Olsa
2013-11-07 13:21 ` Jiri Olsa [this message]
2013-11-07 15:59 ` 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=20131107132118.GD1251@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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).