linux-kernel - Re: disabling group leader perf

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

Message-ID: <4C84E35B.4090600@redhat.com>
Date:	Mon, 06 Sep 2010 15:49:31 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	linux-perf-users@...r.kernel.org,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: disabling group leader perf_event

  On 09/06/2010 03:29 PM, Peter Zijlstra wrote:
>
>>> So what you're basically trying to do is create some histogram of
>>> exit_reason?
>> Yes, exactly.
> One thing I thought of, you can use the unfiltered kvm_exit event as
> leader, that will give you the total number of events, which, esp. when
> you create partial histograms, is useful to figure out how much you
> missed.

Yeah - and the aggregate kvm_exit count is the single most important 
metric for kvm.  We do count it regardless of whether we want the 
individual exit_reasons or not.

-- 
error compiling committee.c: too many arguments to function

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