From: Will Deacon <will.deacon@arm.com>
To: "Leeder, Neil" <nleeder@codeaurora.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Mark Langsdorf <mlangsdo@redhat.com>,
Mark Salter <msalter@redhat.com>, Jon Masters <jcm@redhat.com>,
Timur Tabi <timur@codeaurora.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] perf: qcom_l2: fix column exclusion check
Date: Wed, 26 Jul 2017 09:27:11 +0100 [thread overview]
Message-ID: <20170726082710.GA31242@arm.com> (raw)
In-Reply-To: <95095f56-7b08-4ed9-f7e5-5d5768a75cc5@codeaurora.org>
On Tue, Jul 25, 2017 at 03:43:54PM -0400, Leeder, Neil wrote:
> On 7/25/2017 1:01 PM, Mark Rutland wrote:
> > On Mon, Jul 24, 2017 at 05:17:02PM -0400, Neil Leeder wrote:
> >> The check for column exclusion did not verify that the event being
> >> checked was an L2 event, and not a software event.
> >> Software events should not be checked for column exclusion.
> >> This resulted in a group with both software and L2 events sometimes
> >> incorrectly rejecting the L2 event for column exclusion and
> >> not counting it.
> >>
> >> Add a check for PMU type before applying column exclusion logic.
> >>
> >> Signed-off-by: Neil Leeder <nleeder@codeaurora.org>
> >
> > This looks correct, so:
> >
> > Acked-by: Mark Rutland <mark.rutland@arm.com>
> >
> > Should this have:
> >
> > Fixes: 21bdbb7102edeaeb ("perf: add qcom l2 cache perf events driver")
> >
> > ... ?
> >
> Thanks. I'll re-post with the Fixes tag.
No need, I'll pick it up and add it when I apply.
Cheers,
Will
prev parent reply other threads:[~2017-07-26 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 21:17 [PATCH] perf: qcom_l2: fix column exclusion check Neil Leeder
2017-07-25 17:01 ` Mark Rutland
2017-07-25 19:43 ` Leeder, Neil
2017-07-26 8:27 ` Will Deacon [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=20170726082710.GA31242@arm.com \
--to=will.deacon@arm.com \
--cc=broonie@kernel.org \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mlangsdo@redhat.com \
--cc=msalter@redhat.com \
--cc=nleeder@codeaurora.org \
--cc=timur@codeaurora.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).