From: Will Deacon <will.deacon@arm.com>
To: Chris Smith <chris.smith@st.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>,
"srinidhi.kasagar@stericsson.com"
<srinidhi.kasagar@stericsson.com>
Subject: Re: [PATCH 2/2] arm: pmu: add support for per-cpu PMU interrupts.
Date: Mon, 30 Jul 2012 17:37:02 +0100 [thread overview]
Message-ID: <20120730163701.GH15195@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1343658732-31080-2-git-send-email-chris.smith@st.com>
Hi Chris,
On Mon, Jul 30, 2012 at 03:32:12PM +0100, Chris Smith wrote:
> We have systems where the PMU interrupts are PPIs, and so per-cpu. This
> patch adds support for per-cpu PMU interrupts to the perf event code.
>
> Note that because the dev_id passed to request_percpu_irq has to be
> percpu data, we now pass cpu_hw_events as the dev_id rather than armpmu.
> This only place the dev_id was used was in armpmu_platform_irq, which is
> fixed up accordingly.
>
> Signed-off-by: Chris Smith <chris.smith@st.com>
> ---
I'm actually in the process of moving request/free IRQ into an armpmu
callback, so this patch would fit more neatly into that.
I should have something available this week that you can take a look at.
Will
next prev parent reply other threads:[~2012-07-30 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 14:32 [PATCH 1/2] genirq: Provide an accessor for IRQ_PER_CPU flag Chris Smith
2012-07-30 14:32 ` [PATCH 2/2] arm: pmu: add support for per-cpu PMU interrupts Chris Smith
2012-07-30 16:37 ` Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-30 14:12 [PATCH 1/2] genirq: Provide an accessor for IRQ_PER_CPU flag y
2012-07-30 14:12 ` [PATCH 2/2] arm: pmu: add support for per-cpu PMU interrupts y
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=20120730163701.GH15195@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=chris.smith@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinidhi.kasagar@stericsson.com \
--cc=tglx@linutronix.de \
/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®