linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <bsingharora@gmail.com>
To: linuxppc-dev@ozlabs.org
Cc: Balbir Singh <bsingharora@gmail.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Nicholas Piggin <npiggin@gmail.com>
Subject: [powerpc/nmi: RFC 0/2] Support Soft NMI
Date: Mon, 12 Dec 2016 20:50:01 +1100	[thread overview]
Message-ID: <20161212095003.1885-1-bsingharora@gmail.com> (raw)

This patch is based on suggestions from paulus and benh.
The bugs are all mine. The idea was to implement soft
NMI(s) by keeping interrupts enabled in the soft-disabled
state, but to use the interrupt controller to gate posting
of new interrupts to the processor. This is still work in
progress and a preliminary RFC that needs testing.

Nick posted a more comprehensive version for soft NMI at
https://patchwork.ozlabs.org/patch/704605/, but it does
not work when interrupts are disabled

Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Nicholas Piggin <npiggin@gmail.com>

Balbir Singh (2):
  Merge IPI and DEFAULT priorities
  Keep interrupts enabled even on soft disable

 arch/powerpc/include/asm/paca.h      |  1 +
 arch/powerpc/include/asm/xics.h      |  8 ++------
 arch/powerpc/kernel/exceptions-64s.S | 17 ++++++++++-------
 arch/powerpc/kernel/irq.c            | 21 ++++++++++++++++++++-
 arch/powerpc/kernel/time.c           | 27 ++++++++++++++++++++++++++-
 5 files changed, 59 insertions(+), 15 deletions(-)

-- 
2.9.3

             reply	other threads:[~2016-12-12  9:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12  9:50 Balbir Singh [this message]
2016-12-12  9:50 ` [powerpc/nmi: RFC 1/2] Merge IPI and DEFAULT priorities Balbir Singh
2016-12-12  9:50 ` [powerpc/nmi: RFC 2/2] Keep interrupts enabled even on soft disable Balbir Singh
2016-12-12 13:31   ` Nicholas Piggin
2016-12-12 15:24     ` Benjamin Herrenschmidt
2016-12-13  3:28       ` Balbir Singh
2016-12-13 15:22         ` Benjamin Herrenschmidt
2016-12-13  5:36     ` Balbir Singh
2016-12-13  6:06       ` Nicholas Piggin
2016-12-13 15:27       ` Benjamin Herrenschmidt
2016-12-14  0:41         ` Balbir Singh
2016-12-15 15:15           ` Benjamin Herrenschmidt

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=20161212095003.1885-1-bsingharora@gmail.com \
    --to=bsingharora@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=paulus@samba.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).