From: Will Deacon <will.deacon@arm.com>
To: Vinayak Kale <vkale@apm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"patches@apm.com" <patches@apm.com>,
"jcm@redhat.com" <jcm@redhat.com>,
"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
Marc Zyngier <Marc.Zyngier@arm.com>, Tuan Phan <tphan@apm.com>
Subject: Re: [PATCH V6 2/2] arm64: perf: add support for percpu pmu interrupt
Date: Tue, 3 Dec 2013 13:41:13 +0000 [thread overview]
Message-ID: <20131203134113.GI1169@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CAPrCYke4P2V47iG=1b_f3YHiTqC2hOG5yiKTUWuWG+pX8JauMQ@mail.gmail.com>
On Tue, Dec 03, 2013 at 11:49:11AM +0000, Vinayak Kale wrote:
> On Tue, Dec 3, 2013 at 5:00 PM, Will Deacon <will.deacon@arm.com> wrote:
> > On Mon, Dec 02, 2013 at 09:34:03AM +0000, Vinayak Kale wrote:
> >> Add support for irq registration when pmu interrupt is percpu.
> >>
> >> Signed-off-by: Vinayak Kale <vkale@apm.com>
> >> Signed-off-by: Tuan Phan <tphan@apm.com>
> >> ---
> >> arch/arm64/kernel/perf_event.c | 116 +++++++++++++++++++++++++++++-----------
> >> 1 file changed, 86 insertions(+), 30 deletions(-)
> >>
> >> diff --git a/arch/arm64/kernel/perf_event.c b/arch/arm64/kernel/perf_event.c
> >> index cea1594..d2d562f 100644
> >> --- a/arch/arm64/kernel/perf_event.c
> >> +++ b/arch/arm64/kernel/perf_event.c
> >> @@ -22,6 +22,7 @@
> >>
> >> #include <linux/bitmap.h>
> >> #include <linux/interrupt.h>
> >> +#include <linux/irq.h>
> >> #include <linux/kernel.h>
> >> #include <linux/export.h>
> >> #include <linux/perf_event.h>
> >> @@ -363,26 +364,61 @@ validate_group(struct perf_event *event)
> >> }
> >>
> >> static void
> >> +armpmu_disable_percpu_irq(void *data)
> >> +{
> >> + struct arm_pmu *armpmu = data;
> >> + struct platform_device *pmu_device = armpmu->plat_device;
> >> + int irq = platform_get_irq(pmu_device, 0);
> >> +
> >> + cpumask_test_and_clear_cpu(smp_processor_id(), &armpmu->active_irqs);
> >> + disable_percpu_irq(irq);
> >> +}
> >> +
> >> +static void
> >> armpmu_release_hardware(struct arm_pmu *armpmu)
> >> {
> >> - int i, irq, irqs;
> >> + int irq;
> >
> > Why did you not make this unsigned, like I suggested?
>
> Suggestion was to make 'irqs' variable unsigned and modify the check
> for 'irqs' to if (!irqs).
> This patch incorporates that suggestion.
>
> We have to keep 'irq' signed only. 'platform_get_irq()' can return error value.
Damn, yes, I see the issue there. Ok, I'll go back and take another look at
your patch...
Will
next prev parent reply other threads:[~2013-12-03 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 9:34 [PATCH V6 0/2] genirq: arm64: perf: " Vinayak Kale
2013-12-02 9:34 ` [PATCH V6 1/2] genirq: Add an accessor for IRQ_PER_CPU flag Vinayak Kale
2013-12-03 11:27 ` Will Deacon
2013-12-02 9:34 ` [PATCH V6 2/2] arm64: perf: add support for percpu pmu interrupt Vinayak Kale
2013-12-03 11:30 ` Will Deacon
2013-12-03 11:49 ` Vinayak Kale
2013-12-03 13:41 ` Will Deacon [this message]
2013-12-03 13:50 ` Will Deacon
2013-12-04 6:26 ` Vinayak Kale
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=20131203134113.GI1169@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@apm.com \
--cc=sboyd@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=tphan@apm.com \
--cc=vkale@apm.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®