From: Jiri Olsa <jolsa@redhat.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
linux-kernel@vger.kernel.org, Kan Liang <kan.liang@intel.com>
Subject: Re: [PATCH] perf tools: Add missing Intel CPU events to parser
Date: Wed, 25 Mar 2020 18:44:49 +0100 [thread overview]
Message-ID: <20200325174449.GB1934048@krava> (raw)
In-Reply-To: <fc3c4dee-981e-4c39-566a-4163ee0bcc02@intel.com>
On Wed, Mar 25, 2020 at 07:10:44PM +0200, Adrian Hunter wrote:
SNIP
> > ---
> > diff --git a/tools/perf/util/parse-events.l b/tools/perf/util/parse-events.l
> > index 7b1c8ee537cf..347eb3e6794a 100644
> > --- a/tools/perf/util/parse-events.l
> > +++ b/tools/perf/util/parse-events.l
> > @@ -342,11 +342,15 @@ bpf-output { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_BPF_OUT
> > * Because the prefix cycles is mixed up with cpu-cycles.
> > * loads and stores are mixed up with cache event
> > */
> > -cycles-ct { return str(yyscanner, PE_KERNEL_PMU_EVENT); }
> > -cycles-t { return str(yyscanner, PE_KERNEL_PMU_EVENT); }
> > -mem-loads { return str(yyscanner, PE_KERNEL_PMU_EVENT); }
> > -mem-stores { return str(yyscanner, PE_KERNEL_PMU_EVENT); }
> > -topdown-[a-z-]+ { return str(yyscanner, PE_KERNEL_PMU_EVENT); }
> > +cycles-ct |
> > +cycles-t |
> > +mem-loads |
> > +mem-stores |
> > +topdown-[a-z-]+ |
> > +tx-capacity-read |
> > +tx-capacity-write |
> > +el-capacity-read |
> > +el-capacity-write { return str(yyscanner, PE_KERNEL_PMU_EVENT); }
>
> Yes that works, as does
>
> tx-capacity-[a-z-]+
> el-capacity-[a-z-]+
>
> Do we have an explanation for why we cannot make it accept 3-part names
> without handling them as special cases?
check the pmu_str_check, I guess it could be more generic,
but it gets complicated later on, so I'm not sure there's
some other obstacle..
CC-ing Kan Liang, who wrote that
jirka
>
> I just tried but it didn't work.
>
next prev parent reply other threads:[~2020-03-25 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 15:04 [PATCH] perf tools: Add missing Intel CPU events to parser Adrian Hunter
2020-03-25 10:33 ` Jiri Olsa
2020-03-25 13:15 ` Arnaldo Carvalho de Melo
2020-03-25 13:53 ` Jiri Olsa
2020-03-25 14:22 ` Arnaldo Carvalho de Melo
2020-03-25 14:24 ` Adrian Hunter
2020-03-25 15:22 ` Jiri Olsa
2020-03-25 17:10 ` Adrian Hunter
2020-03-25 17:44 ` Jiri Olsa [this message]
2020-03-26 8:01 ` [PATCH V2] " Adrian Hunter
2020-03-26 9:25 ` Jiri Olsa
2020-03-31 19:13 ` Arnaldo Carvalho de Melo
2020-04-04 8:41 ` [tip: perf/urgent] perf events parser: " tip-bot2 for Adrian Hunter
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=20200325174449.GB1934048@krava \
--to=jolsa@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=kan.liang@intel.com \
--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