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>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf vendor events intel: Add umasks to PCU events.
Date: Fri, 15 Mar 2024 17:29:52 -0300 [thread overview]
Message-ID: <ZfSvwBQRBhfWGb98@x1> (raw)
In-Reply-To: <CAP-5=fURvd4nx_-QLgRBWSoJbXDUqO=WbsLkqMgjiyucXHVrjw@mail.gmail.com>
On Wed, Feb 28, 2024 at 08:12:10AM -0800, Ian Rogers wrote:
> On Wed, Feb 28, 2024 at 6:55 AM Liang, Kan <kan.liang@linux.intel.com> wrote:
> > On 2024-02-27 9:12 p.m., Ian Rogers wrote:
> > > Kan, what's the right way to deal with this?
> >
> > There is no umask in the uncore spec. Please see P120 of the spec.
> > https://www.intel.com/content/www/us/en/develop/download/intel-xeon-processor-e5-2600-v2-product-family-uncore-performance-monitoring-reference.html
> >
> > It should be occ_sel.
> > The occ_sel = (the umask from the event list >> 6) & 0x3.
> >
> > I don't think we want to change either the kernel or the perf tool.
> > There is nothing to help either if we add the occ_sel in the original
> > event list. So it seems the only choice should be handling it in the
> > convertor tool.
> >
> > Is it possible to check the UNC_P_POWER_STATE_OCCUPANCY.CORES_C0 in IVT
> > and use "Filter": "occ_sel=0x1" to replace "UMask": "0x40"?
> >
> > It seems everything in the filter will directly be appended. Is my
> > understanding correct?
>
> Yep. From the manual:
> C0 = 1
> C3 = 2
> C6= 3
> So I'll need to fix all 3 events during the conversion to perf json.
> The same problem exists for haswell and broadwell, so I'll do the fix
> on those architectures too. I was able to test on a jaketown but the
> kernel source makes me think the same fix is necessary there too. I'll
> send out a new patch with this.
Please clarify if this remains reviewed and should be merged as-is.
- Arnaldo
next prev parent reply other threads:[~2024-03-15 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 20:15 [PATCH v1] perf vendor events intel: Add umasks to PCU events Ian Rogers
2024-02-27 14:12 ` Liang, Kan
2024-02-28 2:12 ` Ian Rogers
2024-02-28 14:54 ` Liang, Kan
2024-02-28 16:12 ` Ian Rogers
2024-03-15 20:29 ` Arnaldo Carvalho de Melo [this message]
2024-03-17 23:04 ` Ian Rogers
2024-03-18 14:08 ` Arnaldo Carvalho de Melo
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=ZfSvwBQRBhfWGb98@x1 \
--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 \
/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).