From: Andi Kleen <andi@firstfloor.org>
To: Freehill Christopher-RAT063 <RAT063@freescale.com>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: perf event attrributes
Date: Wed, 27 Mar 2013 18:32:04 -0700 [thread overview]
Message-ID: <m2boa4ia23.fsf@firstfloor.org> (raw)
In-Reply-To: <0C53B16FB1F182409A7BA6DC928E7AFE1FDA4F@039-SN2MPN1-022.039d.mgd.msft.net> (Freehill Christopher-RAT's message of "Wed, 27 Mar 2013 15:40:38 +0000")
Freehill Christopher-RAT063 <RAT063@freescale.com> writes:
>
> Any info or suggestions are appreciated.
The perf model for this is to use bit fields in config/config1 and then
declare those in sysfs, so that they can be set as cpu/foo=1,bar=2/
The kernel driver then extracts those fields.
This only supports numerical values, not string enumerations.
You can see the Intel uncore drivers as a example doing this extensively.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2013-03-28 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 15:40 perf event attrributes Freehill Christopher-RAT063
2013-03-28 1:32 ` Andi Kleen [this message]
2013-04-01 16:09 ` Freehill Christopher-RAT063
2013-04-02 4:42 ` Namhyung Kim
2013-04-03 22:26 ` Freehill Christopher-RAT063
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=m2boa4ia23.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=RAT063@freescale.com \
--cc=linux-perf-users@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).