[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1386151791-4881-1-git-send-email-vkale@apm.com>
Date: Wed, 4 Dec 2013 15:39:49 +0530
From: Vinayak Kale <vkale@....com>
To: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Cc: tglx@...utronix.de, will.deacon@....com, patches@....com,
jcm@...hat.com, sboyd@...eaurora.org, marc.zyngier@....com,
Vinayak Kale <vkale@....com>
Subject: [PATCH V7 0/2] genirq: arm64: perf: support for percpu pmu interrupt
This patch series adds support to handle interrupt registration/deregistration
in arm64 pmu driver when pmu interrupt type is percpu.
Changelog:
V7:
* In arm64 pmu driver: Instead of passing 'struct arm_pmu' pointer, pass the
irq number directly to armpmu_[enable/disable]_percpu_irq().
Clean-up the percpu active irq cpumask set/clear.
V6:
* In arm64 pmu driver: Use macro 'IRQ_TYPE_NONE' while passing irq type value
to enable_percpu_irq(). Change 'irqs' etc variables as unsigned, modify the
check for 'irqs' inside armpmu_[release/reserve]_hardware().
V5:
* In irqdesc.h: Added Chris Smith's sign-off.
In arm64 pmu driver: Handle the invalid irq-0 case for platform_get_irq().
V4:
* In arm64 pmu driver: Avoid using irq_to_desc() to check validity of irq.
V3:
* Remove validity check for 'desc' from accessor function in irqdesc.h .
Instead, check the irq 'desc' validity in arm64 pmu driver.
V2:
* To determine whether an IRQ is percpu or not, added an accessor function in
irqdesc.h . This approach was used by Chris Smith here[1] for similar changes
in arm pmu driver.
* In arm64 pmu driver: Got rid of unnecessary pointer typecastings.
[1] http://lkml.indiana.edu/hypermail/linux/kernel/1207.3/02955.html
Vinayak Kale (2):
genirq: Add an accessor for IRQ_PER_CPU flag
arm64: perf: add support for percpu pmu interrupt
arch/arm64/kernel/perf_event.c | 108 +++++++++++++++++++++++++++++-----------
include/linux/irqdesc.h | 8 +++
2 files changed, 86 insertions(+), 30 deletions(-)
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists