linux-kernel - [PATCH 0/3] perf fixes

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]

Date:	Mon, 20 Jan 2014 15:39:37 +0400
From:	Stanislav Fomichev <stfomichev@...dex-team.ru>
To:	a.p.zijlstra@...llo.nl, paulus@...ba.org, mingo@...hat.com,
	acme@...stprotocols.net, stfomichev@...dex-team.ru,
	namhyung@...nel.org, jolsa@...hat.com, dsahern@...il.com,
	adrian.hunter@...el.com
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH 0/3] perf fixes

This series contains couple of unrelated changes. I already sent two of them
(perf util, perf tools) to the lkml but didn't get any response.
Thus resending them along with new perf timechart fix.

- perf timechart: fix wrong SVG height
  removes unused empty space from generated SVG when called with -p 0 option

- perf util: free cpu_map in perf_session__cpu_bitmap
  frees temporary cpu_map

- perf tools: bring back old behavior when NO_DEMAGLE doesn't link with libbfd
  this is a patch I'd like to get feedback on. The motivation behind it is to
  have a possibility to link without libbfd (because on 3.10 lts NO_DEMANGLE=1
  does not link with libbfd and I'd like to preserve this behavior).

Stanislav Fomichev (3):
  perf timechart: fix wrong SVG height
  perf util: free cpu_map in perf_session__cpu_bitmap
  perf tools: bring back old behavior when NO_DEMAGLE doesn't link with
    libbfd

 tools/perf/builtin-timechart.c | 3 +++
 tools/perf/config/Makefile     | 8 +++-----
 tools/perf/util/session.c      | 2 ++
 3 files changed, 8 insertions(+), 5 deletions(-)

-- 
1.8.3.2

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