From: Mark Rutland <mark.rutland@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: tglx@linutronix.de, "Vineet Gupta" <vgupta@synopsys.com>,
"Marc Zyngier" <marc.zyngier@arm.com>,
"Patrice Chotard" <patrice.chotard@st.com>,
"Kukjin Kim" <kgene@kernel.org>,
"Javier Martinez Canillas" <javier@osg.samsung.com>,
"Christoffer Dall" <christoffer.dall@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Russell King" <linux@armlinux.org.uk>,
"Carlo Caione" <carlo@caione.org>,
"Richard Cochran" <rcochran@linutronix.de>,
"Christoph Hellwig" <hch@lst.de>, "Jens Axboe" <axboe@kernel.dk>,
"Hannes Reinecke" <hare@suse.com>,
"moderated list:ARM PORT" <linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:SYNOPSYS ARC ARCH..." <linux-snps-arc@lists.inf>
Subject: Re: [PATCH V10 1/3] irq: Allow to pass the IRQF_TIMER flag with percpu irq request
Date: Wed, 17 May 2017 11:36:02 +0100 [thread overview]
Message-ID: <20170517103602.GD14654@leverpostej> (raw)
In-Reply-To: <1494963880-16160-1-git-send-email-daniel.lezcano@linaro.org>
On Tue, May 16, 2017 at 09:44:32PM +0200, Daniel Lezcano wrote:
> In the next changes, we track when the interrupts occur in order to
> statistically compute when is supposed to happen the next interrupt.
>
> In all the interruptions, it does not make sense to store the timer interrupt
> occurences and try to predict the next interrupt as when know the expiration
> time.
>
> The request_irq() has a irq flags parameter and the timer drivers use it to
> pass the IRQF_TIMER flag, letting us know the interrupt is coming from a timer.
> Based on this flag, we can discard these interrupts when tracking them.
>
> But, the API request_percpu_irq does not allow to pass a flag, hence specifying
> if the interrupt type is a timer.
>
> Add a function request_percpu_irq_flags() where we can specify the flags. The
> request_percpu_irq() function is changed to be a wrapper to
> request_percpu_irq_flags() passing a zero flag parameter.
>
> Change the timers using request_percpu_irq() to use request_percpu_irq_flags()
> instead with the IRQF_TIMER flag set.
>
> For now, in order to prevent a misusage of this parameter, only the IRQF_TIMER
> flag (or zero) is a valid parameter to be passed to the
> request_percpu_irq_flags() function.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Vineet Gupta <vgupta@synopsys.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Patrice Chotard <patrice.chotard@st.com>
> Cc: Kukjin Kim <kgene@kernel.org>
> Cc: Javier Martinez Canillas <javier@osg.samsung.com>
> Cc: Christoffer Dall <christoffer.dall@linaro.org>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Krčmář <rkrcmar@redhat.com>
> Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
> Changelog:
>
> V10:
> - Drop the change for arch arm virtual timer
> https://lkml.org/lkml/2017/4/25/184
> V9:
> - Clarified the patch description
> - Fixed EXPORT_SYMBOL_GPL(request_percpu_irq_flags)
> ---
> arch/arm/kernel/smp_twd.c | 3 ++-
> drivers/clocksource/arc_timer.c | 4 ++--
> drivers/clocksource/arm_arch_timer.c | 20 ++++++++++++--------
> drivers/clocksource/arm_global_timer.c | 4 ++--
> drivers/clocksource/exynos_mct.c | 7 ++++---
> drivers/clocksource/qcom-timer.c | 4 ++--
> drivers/clocksource/time-armada-370-xp.c | 9 +++++----
> drivers/clocksource/timer-nps.c | 6 +++---
> include/linux/interrupt.h | 11 ++++++++++-
> kernel/irq/manage.c | 15 ++++++++++-----
> 10 files changed, 52 insertions(+), 31 deletions(-)
As an aside, perhaps it would make more sense to move the
request_percpu_irq_flags() addition into a preparatory patch? That way
it's clearly separated from the mechanical clocksource changes, and it's
easy to see how it works.
Either way, for arm_arch_timer:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Thanks,
Mark.
> diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
> index 4bed671..22646b5 100644
> --- a/drivers/clocksource/arm_arch_timer.c
> +++ b/drivers/clocksource/arm_arch_timer.c
> @@ -980,25 +980,29 @@ static int __init arch_timer_register(void)
> ppi = arch_timer_ppi[arch_timer_uses_ppi];
> switch (arch_timer_uses_ppi) {
> case ARCH_TIMER_VIRT_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_virt,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_virt,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> break;
> case ARCH_TIMER_PHYS_SECURE_PPI:
> case ARCH_TIMER_PHYS_NONSECURE_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> if (!err && arch_timer_has_nonsecure_ppi()) {
> ppi = arch_timer_ppi[ARCH_TIMER_PHYS_NONSECURE_PPI];
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> if (err)
> free_percpu_irq(arch_timer_ppi[ARCH_TIMER_PHYS_SECURE_PPI],
> arch_timer_evt);
> }
> break;
> case ARCH_TIMER_HYP_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> break;
> default:
> BUG();
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH V10 1/3] irq: Allow to pass the IRQF_TIMER flag with percpu irq request
Date: Wed, 17 May 2017 11:36:02 +0100 [thread overview]
Message-ID: <20170517103602.GD14654@leverpostej> (raw)
In-Reply-To: <1494963880-16160-1-git-send-email-daniel.lezcano@linaro.org>
On Tue, May 16, 2017@09:44:32PM +0200, Daniel Lezcano wrote:
> In the next changes, we track when the interrupts occur in order to
> statistically compute when is supposed to happen the next interrupt.
>
> In all the interruptions, it does not make sense to store the timer interrupt
> occurences and try to predict the next interrupt as when know the expiration
> time.
>
> The request_irq() has a irq flags parameter and the timer drivers use it to
> pass the IRQF_TIMER flag, letting us know the interrupt is coming from a timer.
> Based on this flag, we can discard these interrupts when tracking them.
>
> But, the API request_percpu_irq does not allow to pass a flag, hence specifying
> if the interrupt type is a timer.
>
> Add a function request_percpu_irq_flags() where we can specify the flags. The
> request_percpu_irq() function is changed to be a wrapper to
> request_percpu_irq_flags() passing a zero flag parameter.
>
> Change the timers using request_percpu_irq() to use request_percpu_irq_flags()
> instead with the IRQF_TIMER flag set.
>
> For now, in order to prevent a misusage of this parameter, only the IRQF_TIMER
> flag (or zero) is a valid parameter to be passed to the
> request_percpu_irq_flags() function.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano at linaro.org>
> Cc: Mark Rutland <mark.rutland at arm.com>
> Cc: Vineet Gupta <vgupta at synopsys.com>
> Cc: Marc Zyngier <marc.zyngier at arm.com>
> Cc: Patrice Chotard <patrice.chotard at st.com>
> Cc: Kukjin Kim <kgene at kernel.org>
> Cc: Javier Martinez Canillas <javier at osg.samsung.com>
> Cc: Christoffer Dall <christoffer.dall at linaro.org>
> Cc: Paolo Bonzini <pbonzini at redhat.com>
> Cc: Radim Kr?m?? <rkrcmar at redhat.com>
> Acked-by: Krzysztof Kozlowski <krzk at kernel.org>
> ---
> Changelog:
>
> V10:
> - Drop the change for arch arm virtual timer
> https://lkml.org/lkml/2017/4/25/184
> V9:
> - Clarified the patch description
> - Fixed EXPORT_SYMBOL_GPL(request_percpu_irq_flags)
> ---
> arch/arm/kernel/smp_twd.c | 3 ++-
> drivers/clocksource/arc_timer.c | 4 ++--
> drivers/clocksource/arm_arch_timer.c | 20 ++++++++++++--------
> drivers/clocksource/arm_global_timer.c | 4 ++--
> drivers/clocksource/exynos_mct.c | 7 ++++---
> drivers/clocksource/qcom-timer.c | 4 ++--
> drivers/clocksource/time-armada-370-xp.c | 9 +++++----
> drivers/clocksource/timer-nps.c | 6 +++---
> include/linux/interrupt.h | 11 ++++++++++-
> kernel/irq/manage.c | 15 ++++++++++-----
> 10 files changed, 52 insertions(+), 31 deletions(-)
As an aside, perhaps it would make more sense to move the
request_percpu_irq_flags() addition into a preparatory patch? That way
it's clearly separated from the mechanical clocksource changes, and it's
easy to see how it works.
Either way, for arm_arch_timer:
Acked-by: Mark Rutland <mark.rutland at arm.com>
Thanks,
Mark.
> diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
> index 4bed671..22646b5 100644
> --- a/drivers/clocksource/arm_arch_timer.c
> +++ b/drivers/clocksource/arm_arch_timer.c
> @@ -980,25 +980,29 @@ static int __init arch_timer_register(void)
> ppi = arch_timer_ppi[arch_timer_uses_ppi];
> switch (arch_timer_uses_ppi) {
> case ARCH_TIMER_VIRT_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_virt,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_virt,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> break;
> case ARCH_TIMER_PHYS_SECURE_PPI:
> case ARCH_TIMER_PHYS_NONSECURE_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> if (!err && arch_timer_has_nonsecure_ppi()) {
> ppi = arch_timer_ppi[ARCH_TIMER_PHYS_NONSECURE_PPI];
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> if (err)
> free_percpu_irq(arch_timer_ppi[ARCH_TIMER_PHYS_SECURE_PPI],
> arch_timer_evt);
> }
> break;
> case ARCH_TIMER_HYP_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> break;
> default:
> BUG();
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V10 1/3] irq: Allow to pass the IRQF_TIMER flag with percpu irq request
Date: Wed, 17 May 2017 11:36:02 +0100 [thread overview]
Message-ID: <20170517103602.GD14654@leverpostej> (raw)
In-Reply-To: <1494963880-16160-1-git-send-email-daniel.lezcano@linaro.org>
On Tue, May 16, 2017 at 09:44:32PM +0200, Daniel Lezcano wrote:
> In the next changes, we track when the interrupts occur in order to
> statistically compute when is supposed to happen the next interrupt.
>
> In all the interruptions, it does not make sense to store the timer interrupt
> occurences and try to predict the next interrupt as when know the expiration
> time.
>
> The request_irq() has a irq flags parameter and the timer drivers use it to
> pass the IRQF_TIMER flag, letting us know the interrupt is coming from a timer.
> Based on this flag, we can discard these interrupts when tracking them.
>
> But, the API request_percpu_irq does not allow to pass a flag, hence specifying
> if the interrupt type is a timer.
>
> Add a function request_percpu_irq_flags() where we can specify the flags. The
> request_percpu_irq() function is changed to be a wrapper to
> request_percpu_irq_flags() passing a zero flag parameter.
>
> Change the timers using request_percpu_irq() to use request_percpu_irq_flags()
> instead with the IRQF_TIMER flag set.
>
> For now, in order to prevent a misusage of this parameter, only the IRQF_TIMER
> flag (or zero) is a valid parameter to be passed to the
> request_percpu_irq_flags() function.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Vineet Gupta <vgupta@synopsys.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Patrice Chotard <patrice.chotard@st.com>
> Cc: Kukjin Kim <kgene@kernel.org>
> Cc: Javier Martinez Canillas <javier@osg.samsung.com>
> Cc: Christoffer Dall <christoffer.dall@linaro.org>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Kr?m?? <rkrcmar@redhat.com>
> Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
> Changelog:
>
> V10:
> - Drop the change for arch arm virtual timer
> https://lkml.org/lkml/2017/4/25/184
> V9:
> - Clarified the patch description
> - Fixed EXPORT_SYMBOL_GPL(request_percpu_irq_flags)
> ---
> arch/arm/kernel/smp_twd.c | 3 ++-
> drivers/clocksource/arc_timer.c | 4 ++--
> drivers/clocksource/arm_arch_timer.c | 20 ++++++++++++--------
> drivers/clocksource/arm_global_timer.c | 4 ++--
> drivers/clocksource/exynos_mct.c | 7 ++++---
> drivers/clocksource/qcom-timer.c | 4 ++--
> drivers/clocksource/time-armada-370-xp.c | 9 +++++----
> drivers/clocksource/timer-nps.c | 6 +++---
> include/linux/interrupt.h | 11 ++++++++++-
> kernel/irq/manage.c | 15 ++++++++++-----
> 10 files changed, 52 insertions(+), 31 deletions(-)
As an aside, perhaps it would make more sense to move the
request_percpu_irq_flags() addition into a preparatory patch? That way
it's clearly separated from the mechanical clocksource changes, and it's
easy to see how it works.
Either way, for arm_arch_timer:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Thanks,
Mark.
> diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
> index 4bed671..22646b5 100644
> --- a/drivers/clocksource/arm_arch_timer.c
> +++ b/drivers/clocksource/arm_arch_timer.c
> @@ -980,25 +980,29 @@ static int __init arch_timer_register(void)
> ppi = arch_timer_ppi[arch_timer_uses_ppi];
> switch (arch_timer_uses_ppi) {
> case ARCH_TIMER_VIRT_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_virt,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_virt,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> break;
> case ARCH_TIMER_PHYS_SECURE_PPI:
> case ARCH_TIMER_PHYS_NONSECURE_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> if (!err && arch_timer_has_nonsecure_ppi()) {
> ppi = arch_timer_ppi[ARCH_TIMER_PHYS_NONSECURE_PPI];
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> if (err)
> free_percpu_irq(arch_timer_ppi[ARCH_TIMER_PHYS_SECURE_PPI],
> arch_timer_evt);
> }
> break;
> case ARCH_TIMER_HYP_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> break;
> default:
> BUG();
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: tglx@linutronix.de, "Vineet Gupta" <vgupta@synopsys.com>,
"Marc Zyngier" <marc.zyngier@arm.com>,
"Patrice Chotard" <patrice.chotard@st.com>,
"Kukjin Kim" <kgene@kernel.org>,
"Javier Martinez Canillas" <javier@osg.samsung.com>,
"Christoffer Dall" <christoffer.dall@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Russell King" <linux@armlinux.org.uk>,
"Carlo Caione" <carlo@caione.org>,
"Richard Cochran" <rcochran@linutronix.de>,
"Christoph Hellwig" <hch@lst.de>, "Jens Axboe" <axboe@kernel.dk>,
"Hannes Reinecke" <hare@suse.com>,
"moderated list:ARM PORT" <linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:SYNOPSYS ARC ARCH..."
<linux-snps-arc@lists.infradead.org>,
"open list:ARM/STI ARCHITECTURE" <kernel@stlinux.com>,
"moderated list:ARM/SAMSUNG EXYNO..."
<linux-samsung-soc@vger.kernel.org>
Subject: Re: [PATCH V10 1/3] irq: Allow to pass the IRQF_TIMER flag with percpu irq request
Date: Wed, 17 May 2017 11:36:02 +0100 [thread overview]
Message-ID: <20170517103602.GD14654@leverpostej> (raw)
In-Reply-To: <1494963880-16160-1-git-send-email-daniel.lezcano@linaro.org>
On Tue, May 16, 2017 at 09:44:32PM +0200, Daniel Lezcano wrote:
> In the next changes, we track when the interrupts occur in order to
> statistically compute when is supposed to happen the next interrupt.
>
> In all the interruptions, it does not make sense to store the timer interrupt
> occurences and try to predict the next interrupt as when know the expiration
> time.
>
> The request_irq() has a irq flags parameter and the timer drivers use it to
> pass the IRQF_TIMER flag, letting us know the interrupt is coming from a timer.
> Based on this flag, we can discard these interrupts when tracking them.
>
> But, the API request_percpu_irq does not allow to pass a flag, hence specifying
> if the interrupt type is a timer.
>
> Add a function request_percpu_irq_flags() where we can specify the flags. The
> request_percpu_irq() function is changed to be a wrapper to
> request_percpu_irq_flags() passing a zero flag parameter.
>
> Change the timers using request_percpu_irq() to use request_percpu_irq_flags()
> instead with the IRQF_TIMER flag set.
>
> For now, in order to prevent a misusage of this parameter, only the IRQF_TIMER
> flag (or zero) is a valid parameter to be passed to the
> request_percpu_irq_flags() function.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Vineet Gupta <vgupta@synopsys.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Patrice Chotard <patrice.chotard@st.com>
> Cc: Kukjin Kim <kgene@kernel.org>
> Cc: Javier Martinez Canillas <javier@osg.samsung.com>
> Cc: Christoffer Dall <christoffer.dall@linaro.org>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Krčmář <rkrcmar@redhat.com>
> Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
> Changelog:
>
> V10:
> - Drop the change for arch arm virtual timer
> https://lkml.org/lkml/2017/4/25/184
> V9:
> - Clarified the patch description
> - Fixed EXPORT_SYMBOL_GPL(request_percpu_irq_flags)
> ---
> arch/arm/kernel/smp_twd.c | 3 ++-
> drivers/clocksource/arc_timer.c | 4 ++--
> drivers/clocksource/arm_arch_timer.c | 20 ++++++++++++--------
> drivers/clocksource/arm_global_timer.c | 4 ++--
> drivers/clocksource/exynos_mct.c | 7 ++++---
> drivers/clocksource/qcom-timer.c | 4 ++--
> drivers/clocksource/time-armada-370-xp.c | 9 +++++----
> drivers/clocksource/timer-nps.c | 6 +++---
> include/linux/interrupt.h | 11 ++++++++++-
> kernel/irq/manage.c | 15 ++++++++++-----
> 10 files changed, 52 insertions(+), 31 deletions(-)
As an aside, perhaps it would make more sense to move the
request_percpu_irq_flags() addition into a preparatory patch? That way
it's clearly separated from the mechanical clocksource changes, and it's
easy to see how it works.
Either way, for arm_arch_timer:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Thanks,
Mark.
> diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
> index 4bed671..22646b5 100644
> --- a/drivers/clocksource/arm_arch_timer.c
> +++ b/drivers/clocksource/arm_arch_timer.c
> @@ -980,25 +980,29 @@ static int __init arch_timer_register(void)
> ppi = arch_timer_ppi[arch_timer_uses_ppi];
> switch (arch_timer_uses_ppi) {
> case ARCH_TIMER_VIRT_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_virt,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_virt,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> break;
> case ARCH_TIMER_PHYS_SECURE_PPI:
> case ARCH_TIMER_PHYS_NONSECURE_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> if (!err && arch_timer_has_nonsecure_ppi()) {
> ppi = arch_timer_ppi[ARCH_TIMER_PHYS_NONSECURE_PPI];
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> if (err)
> free_percpu_irq(arch_timer_ppi[ARCH_TIMER_PHYS_SECURE_PPI],
> arch_timer_evt);
> }
> break;
> case ARCH_TIMER_HYP_PPI:
> - err = request_percpu_irq(ppi, arch_timer_handler_phys,
> - "arch_timer", arch_timer_evt);
> + err = request_percpu_irq_flags(ppi, arch_timer_handler_phys,
> + IRQF_TIMER, "arch_timer",
> + arch_timer_evt);
> break;
> default:
> BUG();
next prev parent reply other threads:[~2017-05-17 10:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 19:44 [PATCH V10 1/3] irq: Allow to pass the IRQF_TIMER flag with percpu irq request Daniel Lezcano
2017-05-16 19:44 ` Daniel Lezcano
2017-05-16 19:44 ` Daniel Lezcano
2017-05-16 19:44 ` Daniel Lezcano
2017-05-16 19:44 ` [PATCH V10 2/3] irq: Track the interrupt timings Daniel Lezcano
2017-05-16 19:44 ` [PATCH V10 3/3] irq: Compute the periodic interval for interrupts Daniel Lezcano
[not found] ` <6b19caa8-2f75-362a-7ee1-977ead0619be@linaro.org>
2017-06-02 8:57 ` Daniel Lezcano
2017-05-17 10:36 ` Mark Rutland [this message]
2017-05-17 10:36 ` [PATCH V10 1/3] irq: Allow to pass the IRQF_TIMER flag with percpu irq request Mark Rutland
2017-05-17 10:36 ` Mark Rutland
2017-05-17 10:36 ` Mark Rutland
-- strict thread matches above, loose matches on Subject: below --
2017-06-12 13:51 [GIT PULL V10] irq: next irq tracking Daniel Lezcano
2017-06-12 13:52 ` [PATCH V10 1/3] irq: Allow to pass the IRQF_TIMER flag with percpu irq request Daniel Lezcano
2017-06-12 13:52 ` Daniel Lezcano
2017-06-12 13:52 ` Daniel Lezcano
2017-06-12 13:52 ` Daniel Lezcano
2017-06-20 14:05 ` Thomas Gleixner
2017-06-20 14:05 ` Thomas Gleixner
2017-06-20 14:05 ` Thomas Gleixner
2017-06-20 14:05 ` Thomas Gleixner
2017-06-20 20:25 ` Daniel Lezcano
2017-06-20 20:25 ` Daniel Lezcano
2017-06-20 20:25 ` Daniel Lezcano
2017-06-20 20:25 ` Daniel Lezcano
2017-06-20 20:29 ` Thomas Gleixner
2017-06-20 20:29 ` Thomas Gleixner
2017-06-20 20:29 ` Thomas Gleixner
2017-06-20 20:29 ` Thomas Gleixner
2017-06-20 20:30 ` Daniel Lezcano
2017-06-20 20:30 ` Daniel Lezcano
2017-06-20 20:30 ` Daniel Lezcano
2017-06-20 20:30 ` Daniel Lezcano
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=20170517103602.GD14654@leverpostej \
--to=mark.rutland@arm.com \
--cc=axboe@kernel.dk \
--cc=carlo@caione.org \
--cc=christoffer.dall@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.inf \
--cc=linux@armlinux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=patrice.chotard@st.com \
--cc=pbonzini@redhat.com \
--cc=rcochran@linutronix.de \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=vgupta@synopsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.