linux-kernel - Re: [PATCH 2/2 -tip] perf_counter: parse-events.c introduce alias member in event

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: <1245765732.3776.17.camel@localhost.localdomain>
Date:	Tue, 23 Jun 2009 19:32:12 +0530
From:	Jaswinder Singh Rajput <jaswinder@...nel.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2 -tip] perf_counter: parse-events.c introduce alias
 member in event_symbol

On Tue, 2009-06-23 at 10:24 +0200, Ingo Molnar wrote:
> * Jaswinder Singh Rajput <jaswinder@...nel.org> wrote:
> 
> > 
> > perf test also need some command to execute otherwise it will also 
> > show long list of <inactive>
> 
> I think what it should do is to execute test-cases _internally_. Not 
> just execute some random command on the system and hope for events.
> 

Can you suggest some good test cases where we can get numbers for almost
all the events on each and every run.


> >  context-switches                                         7956
> >  CPU-migrations                                              7
> 
> this needs to be provoked intentionally via sched_setaffinity(): 
> first migrate to cpu0, then to cpu1.
> 

There should be some option from user or we test it each time.

> >  L1-data-Cache-Load-Referencees                      398303881
> >  L1-data-Cache-Load-Misses                             3552374
> >  L1-data-Cache-Store-Referencees                        270178
> >  L1-data-Cache-Store-Misses                         <inactive>
> 
> this is probably inactive due to AMD not having events for that and 
> the generic cache event being 0 there, right?
> 

Yes, it is not set for AMD.

Thanks,
--
JSR

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