From: John Garry <john.garry@huawei.com>
To: Nick Forrington <nick.forrington@arm.com>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <acme@kernel.org>
Cc: Will Deacon <will@kernel.org>, James Clark <james.clark@arm.com>,
"Mike Leach" <mike.leach@linaro.org>,
Leo Yan <leo.yan@linaro.org>, Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] perf vendor events arm64: Move REMOTE_ACCESS to "memory" category
Date: Thu, 8 Sep 2022 12:47:47 +0100 [thread overview]
Message-ID: <39abfee9-4a9b-ec44-9b02-a6cd34cfe64d@huawei.com> (raw)
In-Reply-To: <20220908112519.64614-1-nick.forrington@arm.com>
On 08/09/2022 12:25, Nick Forrington wrote:
> Move REMOTE_ACCESS event from other.json to memory.json for Neoverse
> CPUs. This is consistent with other Arm (Cortex) CPUs.
>
> Signed-off-by: Nick Forrington<nick.forrington@arm.com>
Reviewed-by: John Garry <john.garry@huawei.com>
WARNING: multiple messages have this Message-ID (diff)
From: John Garry <john.garry@huawei.com>
To: Nick Forrington <nick.forrington@arm.com>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <acme@kernel.org>
Cc: Will Deacon <will@kernel.org>, James Clark <james.clark@arm.com>,
"Mike Leach" <mike.leach@linaro.org>,
Leo Yan <leo.yan@linaro.org>, Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] perf vendor events arm64: Move REMOTE_ACCESS to "memory" category
Date: Thu, 8 Sep 2022 12:47:47 +0100 [thread overview]
Message-ID: <39abfee9-4a9b-ec44-9b02-a6cd34cfe64d@huawei.com> (raw)
In-Reply-To: <20220908112519.64614-1-nick.forrington@arm.com>
On 08/09/2022 12:25, Nick Forrington wrote:
> Move REMOTE_ACCESS event from other.json to memory.json for Neoverse
> CPUs. This is consistent with other Arm (Cortex) CPUs.
>
> Signed-off-by: Nick Forrington<nick.forrington@arm.com>
Reviewed-by: John Garry <john.garry@huawei.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-08 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 11:25 [PATCH] perf vendor events arm64: Move REMOTE_ACCESS to "memory" category Nick Forrington
2022-09-08 11:25 ` Nick Forrington
2022-09-08 11:47 ` John Garry [this message]
2022-09-08 11:47 ` John Garry
2022-09-08 15:20 ` Arnaldo Carvalho de Melo
2022-09-08 15:20 ` 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=39abfee9-4a9b-ec44-9b02-a6cd34cfe64d@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--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=namhyung@kernel.org \
--cc=nick.forrington@arm.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 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.