From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Ian Rogers <irogers@google.com>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
perry.taylor@intel.com, caleb.biggers@intel.com,
kshipra.bopardikar@intel.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>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v3 0/3] Remove bad uncore filter/events
Date: Tue, 9 Aug 2022 16:43:33 -0300 [thread overview]
Message-ID: <YvK45Ya+gs9hUwoy@kernel.org> (raw)
In-Reply-To: <3f85d0f9-921f-4f5c-7b5c-8a8e1773512a@linux.intel.com>
Em Fri, Aug 05, 2022 at 10:45:31AM -0400, Liang, Kan escreveu:
>
>
> On 2022-08-04 9:38 p.m., Ian Rogers wrote:
> > The event converter scripts at:
> > https://github.com/intel/event-converter-for-linux-perf
> > passes Filter values from data on 01.org that is bogus in a perf command
> > line and can cause perf to infinitely recurse in parse events. Remove
> > such events or filter using the updated patch:
> > https://github.com/intel/event-converter-for-linux-perf/pull/15/commits/afd779df99ee41aac646eae1ae5ae651cda3394d
> >
> > v3. Removed filters rather than events in some cases as Suggested-by:
> > Liang, Kan <kan.liang@linux.intel.com>
> > v2. Manually fixed a broken \\Inbound\\ ivytown event.
> >
> > Ian Rogers (3):
> > perf vendor events: Remove bad broadwellde uncore events
> > perf vendor events: Remove bad ivytown uncore events
> > perf vendor events: Remove bad jaketown uncore events
> >
>
> Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
Thanks, applied.
- Arnaldo
> Thanks,
> Kan
>
> > .../arch/x86/broadwellde/uncore-cache.json | 97 -------------------
> > .../arch/x86/broadwellde/uncore-other.json | 13 ---
> > .../arch/x86/ivytown/uncore-cache.json | 90 -----------------
> > .../arch/x86/ivytown/uncore-interconnect.json | 1 -
> > .../arch/x86/ivytown/uncore-other.json | 13 ---
> > .../arch/x86/ivytown/uncore-power.json | 19 ----
> > .../arch/x86/jaketown/uncore-cache.json | 30 ------
> > .../arch/x86/jaketown/uncore-other.json | 13 ---
> > .../arch/x86/jaketown/uncore-power.json | 11 ---
> > 9 files changed, 287 deletions(-)
> >
--
- Arnaldo
prev parent reply other threads:[~2022-08-09 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 1:38 [PATCH v3 0/3] Remove bad uncore filter/events Ian Rogers
2022-08-05 1:38 ` [PATCH v3 1/3] perf vendor events: Remove bad broadwellde uncore events Ian Rogers
2022-08-05 1:38 ` [PATCH v3 2/3] perf vendor events: Remove bad ivytown " Ian Rogers
2022-08-05 1:38 ` [PATCH v3 3/3] perf vendor events: Remove bad jaketown " Ian Rogers
2022-08-05 14:45 ` [PATCH v3 0/3] Remove bad uncore filter/events Liang, Kan
2022-08-09 19:43 ` 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=YvK45Ya+gs9hUwoy@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kshipra.bopardikar@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=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=zhengjun.xing@linux.intel.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).