From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: James Clark <james.clark@arm.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-perf-users@vger.kernel.org, renyu.zj@linux.alibaba.com,
john.g.garry@oracle.com, namhyung@kernel.org,
Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.org>,
Leo Yan <leo.yan@linaro.org>,
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>,
Adrian Hunter <adrian.hunter@intel.com>,
Nick Forrington <nick.forrington@arm.com>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Kajol Jain <kjain@linux.ibm.com>,
Sumanth Korikkar <sumanthk@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 4/5] perf vendor events arm64: Update N2-r0p3 and V2 metrics and events using Arm telemetry repo
Date: Tue, 1 Aug 2023 15:20:10 -0300 [thread overview]
Message-ID: <ZMlM2rTqggT+0iGJ@kernel.org> (raw)
In-Reply-To: <CAP-5=fU1z2+ZUFP0BdQyvy0DK_am9p=9p3goeB44M2cLiF7y7g@mail.gmail.com>
Em Tue, Aug 01, 2023 at 08:56:35AM -0700, Ian Rogers escreveu:
> On Tue, Aug 1, 2023 at 3:55 AM James Clark <james.clark@arm.com> wrote:
> > On 12/07/2023 09:33, James Clark wrote:
> > > On 12/07/2023 02:04, Ian Rogers wrote:
> > >> It might be nice to add "beat" to the glossary:
> > >> https://perf.wiki.kernel.org/index.php/Glossary
> > > I requested an account and I will add it. There is a definition in the
> > > Arm glossary here if, like me, you weren't sure:
> > I'm not sure if my wiki account request worked. I didn't get a response,
> > and I also get a "your IP is blocked from editing" on the password reset
> > page (this is an Arm internal IP).
> > Do you know anything about the account request procedure?
> The wiki is run by RedHat and Arnaldo is able to give permissions.
> Arnaldo could you take a look?
Lemme check.
- Arnaldo
next prev parent reply other threads:[~2023-08-01 18:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 10:02 [PATCH v3 0/5] perf vendor events arm64: Update N2 and V2 metrics and events using Arm telemetry repo James Clark
2023-07-11 10:02 ` [PATCH v3 1/5] perf: cs-etm: Don't duplicate FIELD_GET() James Clark
2023-07-11 10:02 ` [PATCH v3 2/5] perf jevents: Match on highest version of Arm json file available James Clark
2023-07-12 0:39 ` Ian Rogers
2023-07-12 13:38 ` James Clark
2023-07-11 10:02 ` [PATCH v3 3/5] perf vendor events arm64: Update scale units and descriptions of common topdown metrics James Clark
2023-07-12 0:43 ` Ian Rogers
2023-07-11 10:02 ` [PATCH v3 4/5] perf vendor events arm64: Update N2-r0p3 and V2 metrics and events using Arm telemetry repo James Clark
2023-07-12 1:04 ` Ian Rogers
2023-07-12 8:33 ` James Clark
2023-07-12 9:20 ` James Clark
2023-08-01 10:55 ` James Clark
2023-08-01 15:56 ` Ian Rogers
2023-08-01 18:20 ` Arnaldo Carvalho de Melo [this message]
2023-08-02 9:21 ` James Clark
2023-07-11 10:02 ` [PATCH v3 5/5] perf vendor events arm64: Update N2-r0p0 " James Clark
2023-07-12 1:08 ` Ian Rogers
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=ZMlM2rTqggT+0iGJ@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ilkka@os.amperecomputing.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nick.forrington@arm.com \
--cc=peterz@infradead.org \
--cc=renyu.zj@linux.alibaba.com \
--cc=sumanthk@linux.ibm.com \
--cc=tmricht@linux.ibm.com \
--cc=will@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 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).