From: Mel Gorman <mgorman@techsingularity.net>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>
Subject: Translating perf events to raw event codes via sysfs
Date: Tue, 22 Mar 2016 10:31:21 +0000 [thread overview]
Message-ID: <20160322103121.GH31585@techsingularity.net> (raw)
Hi Sukadev,
I'm curious about commit e0728b50d480 ("powerpc/perf: Export Power8
generic and cache events to sysfs"). This commit translates perf
high-level event names into raw codes but only on one architecture for
one CPU.
While I can see how that is useful, I'm wondering why this was implemented
as being specific to a single processor family. Should this not be done
generically for all architectures? I accept that translating event names to
raw codes for perf can be difficult but there are also tools like evt2raw
whose output can then be used with perf.
--
Mel Gorman
SUSE Labs
next reply other threads:[~2016-03-22 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 10:31 Mel Gorman [this message]
2016-03-22 10:33 ` Translating perf events to raw event codes via sysfs Mel Gorman
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=20160322103121.GH31585@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=sukadev@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox