From: John Garry <john.garry@huawei.com>
To: Will Deacon <will.deacon@arm.com>,
Ganapatrao Kulkarni <gklkml16@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
"Nair, Jayachandran" <Jayachandran.Nair@cavium.com>,
<Jan.Glauber@cavium.com>, Peter Zijlstra <peterz@infradead.org>,
<catalin.marinas@arm.com>, LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Robert Richter <Robert.Richter@cavium.com>,
Ingo Molnar <mingo@redhat.com>, <Vadim.Lomovtsev@cavium.com>,
Ganapatrao Kulkarni <Ganapatrao.Kulkarni@cavium.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm_pmu: Delete incorrect cache event mapping for some armv8_pmuv3 events.
Date: Fri, 5 Oct 2018 13:27:08 +0100 [thread overview]
Message-ID: <b04c43bd-5c90-cc06-e2cc-ce542981853a@huawei.com> (raw)
In-Reply-To: <20181004122207.GE4065@arm.com>
On 04/10/2018 13:22, Will Deacon wrote:
> Hi Ganapat,
>
> On Thu, Oct 04, 2018 at 11:12:09AM +0530, Ganapatrao Kulkarni wrote:
>> can you please pull this patch?
>
> I still don't like the idea of just removing events like this, especially
> when other architectures (including some x86 and Power CPUs afaict) playa
> similar games for generic events, and these events do actually appear in
> user code.
>
> I also don't understand why you remove the TLB events. I think that logic
> would imply we should remove all of the events, because we can't distinguish
> prefetches from reads either. If we want to be consistent, then I think
> we should just remove the OP_WRITE events for L1D and BPU -- would you be
> ok with that instead?
>
> Also, looking at the code, I think our PMCEID parsing is broken for 8.1
> parts, where the upper 32 bits of the register are offset by 0x4000 in the
> event numbering space.
>
Here's something I noticed:
static ssize_t
armv8pmu_events_sysfs_show(struct device *dev,
struct device_attribute *attr, char *page)
{
struct perf_pmu_events_attr *pmu_attr;
pmu_attr = container_of(attr, struct perf_pmu_events_attr, attr);
return sprintf(page, "event=0x%03llx\n", pmu_attr->id);
Should this be min width now be 4, since event width is now 16 bits
(even though I don't know why we need to specify this width at all)?
Cheers,
John
> Will
>
> _______________________________________________
> 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:[~2018-10-05 12:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 10:07 Kulkarni, Ganapatrao
2018-10-01 14:29 ` Will Deacon
2018-10-01 16:39 ` Ganapatrao Kulkarni
2018-10-04 5:42 ` Ganapatrao Kulkarni
2018-10-04 12:22 ` Will Deacon
2018-10-04 19:39 ` Ganapatrao Kulkarni
2018-10-05 13:34 ` Will Deacon
2018-10-05 12:27 ` John Garry [this message]
2018-10-05 12:39 ` Will Deacon
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=b04c43bd-5c90-cc06-e2cc-ce542981853a@huawei.com \
--to=john.garry@huawei.com \
--cc=Ganapatrao.Kulkarni@cavium.com \
--cc=Jan.Glauber@cavium.com \
--cc=Jayachandran.Nair@cavium.com \
--cc=Robert.Richter@cavium.com \
--cc=Vadim.Lomovtsev@cavium.com \
--cc=acme@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gklkml16@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®