From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
linux-kernel@vger.kernel.org, Kan Liang <kan.liang@intel.com>
Subject: Re: [PATCH V2] perf tools: Add missing Intel CPU events to parser
Date: Tue, 31 Mar 2020 16:13:07 -0300 [thread overview]
Message-ID: <20200331191307.GM9917@kernel.org> (raw)
In-Reply-To: <20200326092545.GE1947699@krava>
Em Thu, Mar 26, 2020 at 10:25:45AM +0100, Jiri Olsa escreveu:
> On Thu, Mar 26, 2020 at 10:01:47AM +0200, Adrian Hunter wrote:
> > The parser would need significant change to rationalize all this, so
> > instead fix for now by adding missing Intel CPU events with 3-part names
> > to the event parser as tokens.
> > Missing events were found by using:
> > grep -r EVENT_ATTR_STR arch/x86/events/intel/core.c
> > Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
> Acked-by: Jiri Olsa <jolsa@redhat.com>
Thanks, applied.
- Arnaldo
next prev parent reply other threads:[~2020-03-31 19:13 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
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 [this message]
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=20200331191307.GM9917@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=jolsa@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.