From: Leo Yan <leo.yan@linaro.org>
To: Ali Saidi <alisaidi@amazon.com>
Cc: Al.Grant@arm.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, andrew.kilroy@arm.com,
benh@kernel.crashing.org, german.gomez@arm.com,
james.clark@arm.com, john.garry@huawei.com, jolsa@redhat.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
mark.rutland@arm.com, mathieu.poirier@linaro.org,
mingo@redhat.com, namhyung@kernel.org, peterz@infradead.org,
will@kernel.org
Subject: Re: [PATCH] perf arm-spe: Use SPE data source for neoverse cores
Date: Sat, 5 Feb 2022 10:18:07 +0800 [thread overview]
Message-ID: <20220205021807.GA2052922@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20220205000719.19986-1-alisaidi@amazon.com>
Hi Ali,
On Sat, Feb 05, 2022 at 12:07:19AM +0000, Ali Saidi wrote:
[...]
> >Alternatively, we can support HITM tag for L1/L2 cache levels in perf,
> >this can allow us to match memory topology on Arm64 arch, and it should
> >not introduce any regression on x86 arch.
> >
> >Could you confirm if below code can fix the issue or not?
>
> Yes, that should do it. Want me to repsin this with the changes we discussed?
Yes, please go ahead and thanks a lot for your effort.
Leo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-02-05 2:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 18:24 [PATCH] perf arm-spe: Use SPE data source for neoverse cores Ali Saidi
2022-01-24 17:24 ` James Clark
2022-01-24 22:53 ` Ali Saidi
2022-02-02 15:01 ` Leo Yan
2022-02-02 19:51 ` Ali Saidi
2022-02-03 9:19 ` Leo Yan
2022-02-05 0:07 ` Ali Saidi
2022-02-05 2:18 ` Leo Yan [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=20220205021807.GA2052922@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=Al.Grant@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alisaidi@amazon.com \
--cc=andrew.kilroy@arm.com \
--cc=benh@kernel.crashing.org \
--cc=german.gomez@arm.com \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--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=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--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