linux-kernel - [PATCH 0/4] perf record: Cleanups and mmap-based output

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1383763297-27066-1-git-send-email-dsahern@gmail.com>
Date:	Wed,  6 Nov 2013 11:41:33 -0700
From:	David Ahern <dsahern@...il.com>
To:	acme@...stprotocols.net, linux-kernel@...r.kernel.org
Cc:	mingo@...nel.org, jolsa@...hat.com, David Ahern <dsahern@...il.com>
Subject: [PATCH 0/4] perf record: Cleanups and mmap-based output

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(-)

-- 
1.8.3.4 (Apple Git-47)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/