mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julien Thierry <julien.thierry@arm.com>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, peterz@infradead.org, marc.zyngier@arm.com,
	mingo@kernel.org, Julien Thierry <julien.thierry@arm.com>
Subject: [PATCH v6 0/4] Provide core API for NMIs
Date: Thu, 31 Jan 2019 14:53:57 +0000	[thread overview]
Message-ID: <1548946441-38546-1-git-send-email-julien.thierry@arm.com> (raw)

Hi,

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

Updating this series as it is needed for the arm64 pseudo-NMI which we
are considering to merge (I'll post a new version shortly).

Changes since v5[1]:
- Added Marc's Acked-by, Reviewed-by tags
- Fixed locking bug in ready_percpu_nmi()
- Renamed ready_percpu_nmi() to prepare_percpu_nmi()
- Added documentation prepare_percpu_nmi() and teardown_percpu_nmi()

Changes since v4[2]:
- Rebased on v5.0-rc4
- Modified comment for request_percpu_nmi() to detail
  the use of per CPU NMIs a bit more

Changes since v3[3]:
- Rebased on v4.20-rc2

Changes since v2[4]:
- Fix ARM build error reported by kbuild bot
- Fix documentation warnings reported by kbuild bot

Changes since v1[5]:
- Rebased to v4.19-rc1
- Fix some coding style issues

Changes since RFC[6]:
- Rebased to v4.18-rc6
- Remove disable_nmi, one should call disable_nmi_nosync instead
- Remove code related to affinity balancing from NMI functions
- Require PERCPU configuration for NMIs

[1] https://lkml.org/lkml/2019/1/28/541
[2] https://lkml.org/lkml/2018/11/12/2113
[3] https://lkml.org/lkml/2018/8/31/173
[4] https://lkml.org/lkml/2018/8/28/661
[5] https://lkml.org/lkml/2018/7/24/321
[6] https://lkml.org/lkml/2018/7/9/768

Cheers,

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 |  18 +++
 include/linux/irq.h       |  10 ++
 include/linux/irqdesc.h   |   5 +
 kernel/irq/chip.c         |  54 +++++++
 kernel/irq/debugfs.c      |   6 +-
 kernel/irq/internals.h    |   2 +
 kernel/irq/irqdesc.c      |  35 ++++
 kernel/irq/manage.c       | 405 +++++++++++++++++++++++++++++++++++++++++++++-
 8 files changed, 532 insertions(+), 3 deletions(-)

--
1.9.1

             reply	other threads:[~2019-01-31 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 14:53 Julien Thierry [this message]
2019-01-31 14:53 ` [PATCH v6 1/4] genirq: Provide basic NMI management for interrupt lines Julien Thierry
2019-01-31 14:53 ` [PATCH v6 2/4] genirq: Provide NMI management for percpu_devid interrupts Julien Thierry
     [not found]   ` <dc1334f6-f451-183a-758c-8f54da2bd952@huawei.com>
2019-02-13  9:57     ` Julien Thierry
2019-01-31 14:54 ` [PATCH v6 3/4] genirq: Provide NMI handlers Julien Thierry
2019-01-31 14:54 ` [PATCH v6 4/4] irqdesc: Add domain handler for NMIs Julien Thierry
2019-01-31 15:20 ` [PATCH v6 0/4] Provide core API " Julien Thierry
2019-02-05 14:56 ` Marc Zyngier

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=1548946441-38546-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=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

all inboxes | Powered by JetHome®