linux-kernel - Re: [PATCH][RFC] Adding information of counts processes acquired how many spinlocks to schedstat

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]

Date:	Mon, 13 Jul 2009 15:06:12 +0900 (JST)
From:	Hitoshi Mitake <mitake@....info.waseda.ac.jp>
To:	a.p.zijlstra@...llo.nl
Cc:	andi@...stfloor.org, fweisbec@...il.com, mingo@...e.hu,
	acme@...hat.com, linux-kernel@...r.kernel.org,
	Jason Baron <jbaron@...hat.com>
Subject: Re: [PATCH][RFC] Adding information of counts processes acquired
 how many spinlocks to schedstat

From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH][RFC] Adding information of counts processes acquired how many spinlocks to schedstat
Date: Sun, 12 Jul 2009 15:24:05 +0200

> On Sun, 2009-07-12 at 16:23 +0900, Hitoshi Mitake wrote:
> 
> > Thanks, I understood your advice. Using infrastructure of ftrace is good idea, so I'll use it.
> > 
> > But I have a question.
> > I can't enable CONFIG_EVENT_PROFILE because it depends on CONFIG_EVENT_TRACER.
> > And CONFIG_EVENT_TRACER seems something never enabled.
> > 
> > % git grep EVENT_TRACER
> > arch/arm/configs/cm_x300_defconfig:# CONFIG_EVENT_TRACER is not set
> > arch/arm/configs/davinci_all_defconfig:# CONFIG_EVENT_TRACER is not set
> > arch/arm/configs/ep93xx_defconfig:# CONFIG_EVENT_TRACER is not set
> > ....
> > arch/x86/configs/i386_defconfig:# CONFIG_EVENT_TRACER is not set
> > arch/x86/configs/x86_64_defconfig:# CONFIG_EVENT_TRACER is not set
> > init/Kconfig:   depends on PERF_COUNTERS && EVENT_TRACER
> > 
> > In addition, this is the output of searching this on menuconfig
> >     Symbol: EVENT_TRACER [=EVENT_TRACER]          
> > and, there is a log in git
> > 
> > commit a7abe97fd8e7a6ccabba5a04a9f17be9211d418c
> > Author: Steven Rostedt <srostedt@...hat.com>
> > Date:   Mon Apr 20 10:59:34 2009 -0400
> > 
> >     tracing: rename EVENT_TRACER config to ENABLE_EVENT_TRACING
> > 
> >     Currently we have two configs: EVENT_TRACING and EVENT_TRACER.
> >     All tracers enable EVENT_TRACING. The EVENT_TRACER is only a
> >     convenience to enable the EVENT_TRACING when no other tracers
> >     are enabled.
> > 
> > Does EVENT_TRACER make any sense?
> > If doesn't, can I remove dependency of CONFIG_EVENT_PROFILE?
> 
> Yeah, steve broke it, but then Jason fixed it again, but his patches
> might not have made it in yet.
> 
>   http://lkml.org/lkml/2009/7/6/313
> 
> 

Wow! I can obtain lock_acquire with Jason's patch,

% perf stat -e lockdep:lock_acquire sleep 1

 Performance counter stats for 'sleep 1':

           1420  lockdep:lock_acquire

    1.004953591  seconds time elapsed

I wanted this.
So I don't have nothing to do.., but thanks Jason!
--
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/