linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf, tools, pmu-events: Fix fixed counters on Intel
Date: Wed, 9 Sep 2015 13:58:58 -0700	[thread overview]
Message-ID: <20150909205858.GA30739@us.ibm.com> (raw)
In-Reply-To: <1441391602-11580-1-git-send-email-andi@firstfloor.org>

Andi,

Andi Kleen [andi@firstfloor.org] wrote:
| From: Andi Kleen <ak@linux.intel.com>
| 
| [This patch is on top of Sukadev's json patchkit]

I removed this line from the commit log...

| 
| The JSON event lists use a different encoding for fixed counters
| than perf for instructions and cycles (ref-cycles is ok)
| 
| This lead to some common events like inst_retired.any
| or cpu_clk_unhalted.thread not counting, when specified with their
| JSON name.
| 
| Special case these events in the jevents conversion process.
| I prefer to not touch the JSON files for this, as it's intended
| that standard JSON files can be just dropped into the perf
| build without changes.
| 
| Signed-off-by: Andi Kleen <ak@linux.intel.com>
| ---
|  tools/perf/pmu-events/jevents.c | 25 +++++++++++++++++++++++--
|  1 file changed, 23 insertions(+), 2 deletions(-)
| 
| diff --git a/tools/perf/pmu-events/jevents.c b/tools/perf/pmu-events/jevents.c
| index 7347cca..f4e5903 100644
| --- a/tools/perf/pmu-events/jevents.c
| +++ b/tools/perf/pmu-events/jevents.c
| @@ -237,6 +237,28 @@ static void print_events_table_suffix(FILE *outfp)
|  	fprintf(outfp, "};\n");
|  }
| 
| +static struct fixed {
| +	const char *name;
| +	const char *event;
| +} fixed[] = {
| +	{ "inst_retired.any", "event=0xc0" },
| +	{ "cpu_clk_unhalted.thread", "event=0x3c" },
| +	{ "cpu_clk_unhalted.thread_any", "event=0x3c,any=1" },
| +	{},

...and replaced this line with:

	{NULL, NULL},

to fix the compile error:

pmu-events/jevents.c:247:2: error: missing initializer for field ‘name’ of ‘struct fixed’ [-Werror=missing-field-initializers]
  {},

After this I was able to get non-zero counts for the 'inst_retired.any'
event on my system. Without the patch, I get 0 count for the event.

I pushed this commit to the 'json-v16' branch.

I also noticed an "Unknown MSR" message when building 'jevents':

  CC       /root/suka/linux-acme.git/tools/perf/perf-obj/pmu-events/jevents.o
  LD       /root/suka/linux-acme.git/tools/perf/perf-obj/pmu-events/jevents-in.o
  LINK     /root/suka/linux-acme.git/tools/perf/perf-obj/pmu-events/jevents
  GEN      /root/suka/linux-acme.git/tools/perf/perf-obj/pmu-events/pmu-events.c
jevents: Unknown MSR in event file 0x3F7

The message is unrelated to the current patch and seems to show up when
processing:

	tools/perf/pmu-events/arch/x86/Skylake_core.json

(Note that you have to merge the 'json-files-7' branch with 'json-v16' to get
the JSON files and hence the error).

Thanks,

Sukadev


  reply	other threads:[~2015-09-09 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 18:33 [PATCH] perf, tools, pmu-events: Fix fixed counters on Intel Andi Kleen
2015-09-09 20:58 ` Sukadev Bhattiprolu [this message]
2015-09-09 21:24   ` Andi Kleen

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=20150909205858.GA30739@us.ibm.com \
    --to=sukadev@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@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).