From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: "Liang, Kan" <kan.liang@linux.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>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Edward Baker <edward.baker@intel.com>
Subject: Re: [PATCH v1] perf vendor events intel: Alderlake/sapphirerapids metric fixes
Date: Sat, 27 Jan 2024 16:30:35 -0300 [thread overview]
Message-ID: <ZbVZ2yeWTRKNS-1R@kernel.org> (raw)
In-Reply-To: <CAP-5=fXpkMP0yphYLAUFNwHjBZvapzkop41LGnKDc1QAOoi7qg@mail.gmail.com>
Em Fri, Jan 26, 2024 at 05:46:33PM -0800, Ian Rogers escreveu:
> On Fri, Jan 5, 2024 at 11:22 AM Liang, Kan <kan.liang@linux.intel.com> wrote:
> >
> >
> >
> > On 2024-01-04 6:19 p.m., Ian Rogers wrote:
> > > As events are deduplicated by name, ensure PMU prefixes are always
> > > used in metrics. Previously they may be missed on the first event in a
> > > formula.
> > >
> > > Update metric constraints for architectures with topdown l2 events.
> > >
> > > Conversion script updated in:
> > > https://github.com/intel/perfmon/pull/128
> > >
> > > Reported-by: Arnaldo Carvalho de Melo <acme@kernel.org>
> > > Closes: https://lore.kernel.org/lkml/ZZam-EG-UepcXtWw@kernel.org/
> > > Signed-off-by: Ian Rogers <irogers@google.com>
> >
> > Thanks Ian.
> >
> > Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
> >
> > Thanks,
> > Kan
>
> Ping.
Applied and it fixes the problem I just reported (perf test 103),
thanks!
- Arnaldo
prev parent reply other threads:[~2024-01-27 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 23:19 [PATCH v1] perf vendor events intel: Alderlake/sapphirerapids metric fixes Ian Rogers
2024-01-05 19:22 ` Liang, Kan
2024-01-27 1:46 ` Ian Rogers
2024-01-27 19:30 ` 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=ZbVZ2yeWTRKNS-1R@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=edward.baker@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 \
/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.