linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julien Thierry <julien.thierry@arm.com>
To: linux-kernel@vger.kernel.org
Cc: ricardo.neri-calderon@linux.intel.com, tglx@linutronix.de,
	marc.zyngier@arm.com, peterz@infradead.org, mingo@kernel.org,
	Julien Thierry <julien.thierry@arm.com>
Subject: [RFC PATCH 0/4] Provide core API for NMIs
Date: Mon,  9 Jul 2018 17:14:02 +0100	[thread overview]
Message-ID: <1531152846-19374-1-git-send-email-julien.thierry@arm.com> (raw)

Hi,

This patch series provides a way for irqchips to define some IRQs as NMIs.

For this to be possible, the irqchip must:
- be a root irqchip
- not require bus locking
- have the NMI support flag

Once these conditions are met, interrupt lines can be requested as NMIs.
These lines must not be shared and the IRQ handling must not be threaded.
Callbacks are added to the irqchip in order to set up (clean up) the
necessary resources for NMIs before enabling (before releasing) the
corresponding interrupt line.

For reference, see the examples of the support provided by GICv3 [1] and
for the request and management of an NMI in the arm_pmu driver [2]. (These
are not on the list yet as I'd like the focus of the discussion to be on
the API for now)

This work was motivated by a discussion on Ricardo Neri's patch [3]

Patches 1 & 2 provide functions necessary to request and manage NMIs.
Patches 3 & 4 provide functions for NMI handling.

[1] http://www.linux-arm.org/git?p=linux-jt.git;a=commitdiff;h=6401387983ce39a60a3cee12c8975dd18ac0b20e
[2] http://www.linux-arm.org/git?p=linux-jt.git;a=commitdiff;h=1e5105197ed20dc0f7061e4918e0fb6a84799908
[3] https://patchwork.kernel.org/patch/10461381/

Thanks,

Julien

-->

Julien Thierry (4):
  genirq: Provide basic NMI management for interrupt lines
  genirq: Provide NMI management for percpu_devid interrupts
  genirq: Provide NMI handlers
  irqdesc: Add domain handler for NMIs

 include/linux/interrupt.h |  19 +++
 include/linux/irq.h       |  10 ++
 include/linux/irqdesc.h   |   3 +
 kernel/irq/chip.c         |  54 +++++++
 kernel/irq/debugfs.c      |   6 +-
 kernel/irq/internals.h    |   1 +
 kernel/irq/irqdesc.c      |  33 ++++
 kernel/irq/manage.c       | 399 ++++++++++++++++++++++++++++++++++++++++++++++
 8 files changed, 523 insertions(+), 2 deletions(-)

--
1.9.1

             reply	other threads:[~2018-07-09 16:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09 16:14 Julien Thierry [this message]
2018-07-09 16:14 ` [RFC PATCH 1/4] genirq: Provide basic NMI management for interrupt lines Julien Thierry
2018-07-17  9:22   ` Thomas Gleixner
2018-07-17 11:13     ` Julien Thierry
2018-07-17 11:28       ` Peter Zijlstra
2018-07-17 12:25         ` Julien Thierry
2018-07-17 15:48       ` Julien Thierry
2018-07-17 15:51         ` Peter Zijlstra
2018-07-17 16:35           ` Julien Thierry
2018-07-17 19:46             ` Thomas Gleixner
2018-07-18  8:09               ` Julien Thierry
2018-07-17 19:42           ` Thomas Gleixner
2018-07-09 16:14 ` [RFC PATCH 2/4] genirq: Provide NMI management for percpu_devid interrupts Julien Thierry
2018-07-09 16:14 ` [RFC PATCH 3/4] genirq: Provide NMI handlers Julien Thierry
2018-07-09 16:14 ` [RFC PATCH 4/4] irqdesc: Add domain handler for NMIs Julien Thierry

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=1531152846-19374-1-git-send-email-julien.thierry@arm.com \
    --to=julien.thierry@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ricardo.neri-calderon@linux.intel.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;
as well as URLs for NNTP newsgroup(s).