linux-kernel - [PATCH 0/4] perf bench: Add new subsystem "mem" and new suite "memcpy"

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: <1258086186-32317-1-git-send-email-mitake@dcl.info.waseda.ac.jp>
Date:	Fri, 13 Nov 2009 13:23:02 +0900
From:	Hitoshi Mitake <mitake@....info.waseda.ac.jp>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org,
	Hitoshi Mitake <mitake@....info.waseda.ac.jp>
Subject: [PATCH 0/4] perf bench: Add new subsystem "mem" and new suite "memcpy"

This patch series adds new subysystem "mem"
and new suite "memcpy" for it.

I've not added the memcpy() of Nehalem oriented optimization
by Ling Ma. The original memcpy() contains a lot of
separated inline assembly, and label with name of single digit
caused conflict with other part of assembled code.
So I'll rewrite it for readability and post
the patch to add memcpy() by Ling later.

This is first version. Could you review this?

Hitoshi Mitake (4):
  perf bench: Add new subsystem and new suite, bench/mem-memcpy.c
  perf bench: Modify bench/bench.h for new prototype:
    bench_mem_memcpy()
  perf bench: Modify builtin-bench.c for new subsystem "mem"
  perf bench: Modify Makefile to build new subsystem "mem"

 tools/perf/Makefile           |    3 +-
 tools/perf/bench/bench.h      |    1 +
 tools/perf/bench/mem-memcpy.c |  258 +++++++++++++++++++++++++++++++++++++++++
 tools/perf/builtin-bench.c    |   14 ++-
 4 files changed, 274 insertions(+), 2 deletions(-)
 create mode 100644 tools/perf/bench/mem-memcpy.c

--
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/