LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas-Mich Richter <tmricht@linux.ibm.com>
To: John Garry <john.garry@huawei.com>,
brueckner@linux.vnet.ibm.com, tmricht@linux.vnet.ibm.com
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Linuxarm <linuxarm@huawei.com>,
linux-kernel@vger.kernel.org, Will Deacon <will.deacon@arm.com>
Subject: Re: s390 perf events JSONs query
Date: Fri, 20 Apr 2018 15:25:05 +0200 [thread overview]
Message-ID: <c5dde055-de48-52c1-04d7-7ec22623d75f@linux.ibm.com> (raw)
In-Reply-To: <68e84967-ca29-0b86-027a-76307e003a55@huawei.com>
On 04/20/2018 12:51 PM, John Garry wrote:
> Hi Hendrik, Thomas,
>
> I noticed that in 4.17-rc1 support was included for s390 perf pmu-events. I also notice that the JSONs contain many common (identical actually) events between different chips for this arch.
>
> Support was added for factoring out common arch events in https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/tools/perf/pmu-events?h=next-20180420&id=e9d32c1bf0cd7a98358ec4aa1625bf2b3459b9ac
>
> ARM64 chips use this feature. I am not familiar with the s390 arch, but do you think you could also use this feature?
>
> Thanks,
> John
>
I have just played with this feature. I was caught off by this error message:
[root@s35lp76 pmu-events]# ./jevents s390 arch /tmp/xxx 100000
d 0 4096 s390 arch/s390
d 1 4096 cf_z14 arch/s390/cf_z14
f 2 1338 basic.json arch/s390/cf_z14/basic.json
....
jevents: Ignoring file arch/s390/archevent.json <---- confusing error message
jevents: Processing mapfile arch/s390/mapfile.csv
[root@s35lp76 pmu-events]#
I started debugging, until I realized this file is still processed.....
(Just a side remark).
Anyway the features is nice, but it does not save anything in the resulting
pmu-events.c file, correct? The events defined in the common archevent.json
files are just copied into the structures of a specific machine.
The feature saves time and space when you create the machine specific json
files because it allows you to refer to a common event by name. Cool!
On s390 we do not create the json files manually, but have some scripts to
create them based on s390 type/model hardware specific input files.
@Hendirk,
we could rework our internal tool chain to emit the new "ArchStdEvent"
keyword for common events, but in the end we do not save anything in the
resulting pmu-events.c file. And it requires considerable rework to
support it.
Given that, I would put it very low priority on your todo list, comments?
--
Thomas Richter, Dept 3303, IBM LTC Boeblingen Germany
--
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2018-04-20 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 10:51 John Garry
2018-04-20 11:44 ` Thomas-Mich Richter
2018-04-20 12:34 ` John Garry
2018-04-20 13:25 ` Thomas-Mich Richter [this message]
2018-04-20 13:53 ` John Garry
2018-04-20 14:13 ` Hendrik Brueckner
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=c5dde055-de48-52c1-04d7-7ec22623d75f@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tmricht@linux.vnet.ibm.com \
--cc=will.deacon@arm.com \
--subject='Re: s390 perf events JSONs query' \
/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
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).