From: Jiri Olsa <jolsa@redhat.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Vince Weaver <vincent.weaver@maine.edu>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@linux.intel.com>,
linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>,
Borislav Petkov <bp@suse.de>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH RFC] perf: Let PMUs provide supplementary information
Date: Sun, 26 Jul 2015 18:36:39 +0200 [thread overview]
Message-ID: <20150726163639.GC17020@krava.brq.redhat.com> (raw)
In-Reply-To: <1437723969-19558-1-git-send-email-adrian.hunter@intel.com>
On Fri, Jul 24, 2015 at 10:46:09AM +0300, Adrian Hunter wrote:
> This is a follow-up to "[RFC PATCH] perf: Provide status of known PMUs" i.e.
>
> https://lkml.kernel.org/r/1436428080-3098-1-git-send-email-adrian.hunter@intel.com
>
> There are 3 main changes:
> - uses debugfs not sysfs
> - doesn't require a PMU to be on the list of known PMU's
> - renamed from 'known_pmus' to 'pmu_supplementary_info'
do you plan any perf tool related change?
'perf list' could display this info
tested..
[root@ibm-x3650m4-01 pmu_supplementary_info]# pwd
/sys/kernel/debug/perf/pmu_supplementary_info
[root@ibm-x3650m4-01 pmu_supplementary_info]# ll
total 0
-r--r--r--. 1 root root 0 Jul 26 18:22 intel_bts
-r--r--r--. 1 root root 0 Jul 26 18:22 intel_pt
[root@ibm-x3650m4-01 pmu_supplementary_info]# cat *
Enabled
Disabled: Not supported by the hardware
jirka
prev parent reply other threads:[~2015-07-26 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 7:46 Adrian Hunter
2015-07-26 16:36 ` Jiri Olsa [this message]
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=20150726163639.GC17020@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@suse.de \
--cc=eranian@google.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vincent.weaver@maine.edu \
/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
all inboxes | Powered by JetHome®