linux-kernel - Re: [PATCH] perf timechart: Work around commit 42e59d7d19dc4b4

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-prev] [day] [month] [year] [list]

Date:	Mon, 12 Oct 2009 09:12:55 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Arjan van de Ven <arjan@...radead.org>,
	Mike Galbraith <efault@....de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf timechart: Work around commit 42e59d7d19dc4b4


* Arjan van de Ven <arjan@...radead.org> wrote:

> >From 07c039ee370f49a0c5fc690ba473d42d27ccb022 Mon Sep 17 00:00:00 2001
> From: Arjan van de Ven <arjan@...ux.intel.com>
> Date: Wed, 7 Oct 2009 12:27:07 -0700
> Subject: [PATCH] perf timechart: Work around commit 42e59d7d19dc4b4
> 
> Commit 42e59d7d19dc4b4 introduced a sample frequency framework..
> .. however it unfortunately changed how perf events get recorded,
> and caused timechart to miss events to the point that timechart
> became useless.
> 
> This patch causes the timechart code to use -F 0 to not use the
> new framework when recording timechart data.
> 
> Signed-off-by: Arjan van de Ven <arjan@...ux.intel.com>
> ---
>  tools/perf/builtin-timechart.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)

Could you please check latest -tip, does it work fine now?

Mike's commit:

  7e4ff9e: perf tools: Fix counter sample frequency breakage

should fix the breakage 42e59d7d19dc4b4 introduced in perf timechart.

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