linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: irq_work_run called from armv8pmu_handle_irq
Date: Thu, 2 Feb 2017 12:47:27 +0000	[thread overview]
Message-ID: <20170202124727.GA13839@arm.com> (raw)
In-Reply-To: <762e1210e12fbc693b3d0e27361df53f@codeaurora.org>

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

      reply	other threads:[~2017-02-02 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 20:15 irq_work_run called from armv8pmu_handle_irq Sodagudi Prasad
2017-02-02 12:47 ` Will Deacon [this message]

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=20170202124727.GA13839@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).