From: chrubis@suse.cz
To: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 3/3] performance_counters: make performance_counters run default
Date: Wed, 9 Apr 2014 19:04:56 +0200 [thread overview]
Message-ID: <20140409170455.GA31198@rei> (raw)
In-Reply-To: <5344EA26.8010209@cn.fujitsu.com>
Hi!
Hi!
> The Number Hardware Counters is 7, But according to above ./perf_event_open02 in RHEL7.0beta, the output is 5.
> Whether two slots in PMU has been used, or the output of papi_avail is not correct :-) .
I would guess that these are used by kernel or system for something else.
> I tried to figure out how papi_avail gets the number of hardware counters, It seems that it just predefines some const values for
> specific cpus, but I am not very sure, I do not have much time to read the papi_library source code.
>
> And I afraid that this library does not support enough kinds of cpus. I also met some compilation errors in Fedora19 about this library.
>
> So whether we can use the first method I mentioned. I think it is more reasonable, at least according to perf_even_open()'s manpage
> and the intent of perf_event_open02 case.
Your method is better, because the testcase only cares if perf events
are multiplexed or not which is implied by different time_enabled and
time_running fields.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-04-09 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 8:13 [LTP] [PATCH 1/3] performance_counters/performance_counter01.c: cleanup Xiaoguang Wang
2014-03-17 8:13 ` [LTP] [PATCH 2/3] performance_counters/performance_counter02.c: cleanup Xiaoguang Wang
2014-03-17 8:13 ` [LTP] [PATCH 3/3] performance_counters: make performance_counters run default Xiaoguang Wang
2014-03-31 15:08 ` chrubis
[not found] ` <533A864A.4040109@cn.fujitsu.com>
2014-04-01 11:58 ` chrubis
[not found] ` <5344EA26.8010209@cn.fujitsu.com>
2014-04-09 17:04 ` chrubis [this message]
2014-03-31 14:59 ` [LTP] [PATCH 1/3] performance_counters/performance_counter01.c: cleanup chrubis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140409170455.GA31198@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=wangxg.fnst@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.