linux-kernel - Re: Question about resetting a sampling counter in kernel

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]

Message-ID: <1329310854.2293.79.camel@twins>
Date:	Wed, 15 Feb 2012 14:00:54 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	heechul Yun <heechul@...inois.edu>
Cc:	linux-kernel@...r.kernel.org, Vince Weaver <vweaver1@...s.utk.edu>
Subject: Re: Question about resetting a sampling counter in kernel

On Sun, 2012-02-12 at 12:37 -0600, heechul Yun wrote:
> Hello,
> 
> I have a question about controlling performance counter in kernel.
> 
> I created a kernel counter which generates an interrupt at every
> 10000 cache-misses as shown below.
> 
> struct perf_event_attr sched_perf_hw_attr = {
>      .type = PERF_TYPE_HARDWARE,
>      .config = PERF_COUNT_HW_CACHE_MISSES,
>      .sample_period = 10000,
>      .size = sizeof(struct perf_event_attr),
>      .pinned = 1,
>      .disbled = 1,
> }
> 
> event = perf_event_create_kernel_counter(&sched_perf_hw_attr, cpu,
>        NULL, event_overflow_callback, NULL);
> 
> What I would like to do is to "reset" the counter before the
> overflow interrupt occurs (e.g, reset at 5000th event),
> and then to restart the sampling from 0.
> 
> I found perf_event_enable() and perf_event_disable() only
> start/stop the counting but couln't figure out how to reset the
> sampling as I described above.
> 
> I would be really thankful if you explain how I can efficiently reset the
> sampling counter.

Expose and use perf_event_reset().
--
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/