From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Rob Herring <robh@kernel.org>,
Ravi Bangoria <ravi.bangoria@amd.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Richter <tmricht@linux.ibm.com>
Subject: Re: [PATCH v2 0/4] Hybrid event parsing fixes
Date: Thu, 1 Jun 2023 14:39:02 -0300 [thread overview]
Message-ID: <ZHjXttVpQE6nUy8s@kernel.org> (raw)
In-Reply-To: <07b1f8d9-3839-81cd-0c46-3742f6273901@linux.intel.com>
Em Thu, Jun 01, 2023 at 09:59:20AM -0400, Liang, Kan escreveu:
>
>
> On 2023-06-01 4:29 a.m., Ian Rogers wrote:
> > Correct various issues that have come up in mailing list discussions,
> > the most impactful of which is the wildcard opening of events of type
> > PERF_TYPE_HARDWARE and PERF_TYPE_HW_CACHE. But also try to avoid a
> > parse-error without a warning, have more fall-back behaviors and be
> > liberal with the definition of software events.
> >
> > The majority of the change is in correcting the parse-event test to
> > match the new hybrid parsing.
> >
> > Ian Rogers (4):
> > perf pmu: Correct perf_pmu__auto_merge_stats affecting hybrid
> > perf evsel: Add verbose 3 print of evsel name when opening
> > perf parse-events: Wildcard most "numeric" events
> > perf test: Update parse-events expectations
>
> The patch set fixes the issues I found on a hybrid machine.
>
> Tested-by: Kan Liang <kan.liang@linux.intel.com>
Thanks, applied.
- Arnaldo
> It's better to fold the examples (especially for the patch 1) in the
> description. So we can understand what's it trying to fix and what's the
> expected result now.
>
> Thanks,
> Kan
>
> >
> > tools/perf/tests/parse-events.c | 1108 ++++++++++++++++---------------
> > tools/perf/util/evsel.c | 1 +
> > tools/perf/util/parse-events.c | 104 ++-
> > tools/perf/util/parse-events.y | 10 +-
> > tools/perf/util/pmu.c | 18 +-
> > tools/perf/util/pmu.h | 5 +
> > tools/perf/util/pmus.c | 5 +
> > tools/perf/util/pmus.h | 1 +
> > 8 files changed, 698 insertions(+), 554 deletions(-)
> >
--
- Arnaldo
prev parent reply other threads:[~2023-06-01 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 8:29 [PATCH v2 0/4] Hybrid event parsing fixes Ian Rogers
2023-06-01 8:29 ` [PATCH v2 1/4] perf pmu: Correct perf_pmu__auto_merge_stats affecting hybrid Ian Rogers
2023-06-01 13:52 ` Liang, Kan
2023-06-01 8:29 ` [PATCH v2 2/4] perf evsel: Add verbose 3 print of evsel name when opening Ian Rogers
2023-06-01 8:29 ` [PATCH v2 3/4] perf parse-events: Wildcard most "numeric" events Ian Rogers
2023-06-01 13:52 ` Liang, Kan
2023-06-01 8:29 ` [PATCH v2 4/4] perf test: Update parse-events expectations Ian Rogers
2023-06-01 13:59 ` [PATCH v2 0/4] Hybrid event parsing fixes Liang, Kan
2023-06-01 17:39 ` Arnaldo Carvalho de Melo [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=ZHjXttVpQE6nUy8s@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=robh@kernel.org \
--cc=tmricht@linux.ibm.com \
/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).