All of lore.kernel.org
 help / color / mirror / Atom feed
* irq_work_run called from armv8pmu_handle_irq
@ 2017-02-01 20:15 ` Sodagudi Prasad
  0 siblings, 0 replies; 4+ messages in thread
From: Sodagudi Prasad @ 2017-02-01 20:15 UTC (permalink / raw)
  To: peterz, mingo, acme, will.deacon, mark.rutland, catalin.marinas
  Cc: linux-kernel, linux-arm-kernel, tsoni, pfay

Hi All,

we would like to understand why irq_work_run() is getting called from 
armv8pmu_handle_irq() irq handler for arm SoC.

Is this irq_work frame work designed to run works from ARMPMU irq 
handlers?  If there are no of drivers using the IRQ WORK frame work,  we 
may see that ARMPMU irq handler taking long time, right?

-Thanks, Prasad

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora 
Forum,
Linux Foundation Collaborative Project

^ permalink raw reply	[flat|nested] 4+ messages in thread

* irq_work_run called from armv8pmu_handle_irq
@ 2017-02-01 20:15 ` Sodagudi Prasad
  0 siblings, 0 replies; 4+ messages in thread
From: Sodagudi Prasad @ 2017-02-01 20:15 UTC (permalink / raw)
  To: linux-arm-kernel

Hi All,

we would like to understand why irq_work_run() is getting called from 
armv8pmu_handle_irq() irq handler for arm SoC.

Is this irq_work frame work designed to run works from ARMPMU irq 
handlers?  If there are no of drivers using the IRQ WORK frame work,  we 
may see that ARMPMU irq handler taking long time, right?

-Thanks, Prasad

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora 
Forum,
Linux Foundation Collaborative Project

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: irq_work_run called from armv8pmu_handle_irq
  2017-02-01 20:15 ` Sodagudi Prasad
@ 2017-02-02 12:47   ` Will Deacon
  -1 siblings, 0 replies; 4+ messages in thread
From: Will Deacon @ 2017-02-02 12:47 UTC (permalink / raw)
  To: Sodagudi Prasad
  Cc: peterz, mingo, acme, mark.rutland, catalin.marinas, linux-kernel,
	linux-arm-kernel, tsoni, pfay

On Wed, Feb 01, 2017 at 12:15:01PM -0800, Sodagudi Prasad wrote:
> we would like to understand why irq_work_run() is getting called from
> armv8pmu_handle_irq() irq handler for arm SoC.
> 
> Is this irq_work frame work designed to run works from ARMPMU irq handlers?
> If there are no of drivers using the IRQ WORK frame work,  we may see that
> ARMPMU irq handler taking long time, right?

The perf_event_overflow callback can schedule IRQ work to e.g. disable the
PMU and want to make sure this runs before we EOI the PMU IRQ.

Will

^ permalink raw reply	[flat|nested] 4+ messages in thread

* irq_work_run called from armv8pmu_handle_irq
@ 2017-02-02 12:47   ` Will Deacon
  0 siblings, 0 replies; 4+ messages in thread
From: Will Deacon @ 2017-02-02 12:47 UTC (permalink / raw)
  To: linux-arm-kernel

On Wed, Feb 01, 2017 at 12:15:01PM -0800, Sodagudi Prasad wrote:
> we would like to understand why irq_work_run() is getting called from
> armv8pmu_handle_irq() irq handler for arm SoC.
> 
> Is this irq_work frame work designed to run works from ARMPMU irq handlers?
> If there are no of drivers using the IRQ WORK frame work,  we may see that
> ARMPMU irq handler taking long time, right?

The perf_event_overflow callback can schedule IRQ work to e.g. disable the
PMU and want to make sure this runs before we EOI the PMU IRQ.

Will

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-02-02 12:47 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-02-01 20:15 irq_work_run called from armv8pmu_handle_irq Sodagudi Prasad
2017-02-01 20:15 ` Sodagudi Prasad
2017-02-02 12:47 ` Will Deacon
2017-02-02 12:47   ` Will Deacon

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.