From: Balbir Singh <bsingharora@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH v3 0/3] Support Soft NMI
Date: Thu, 5 Jan 2017 15:55:35 +1100 [thread overview]
Message-ID: <20170105045538.32658-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
TODOs:
1. Integrate with
https://patchwork.ozlabs.org/patch/706983/
2. Remove the duplicate XIRR between KVM and the
paca's irq field. Will do this in a follow on
series, since that requires extensive testing
Changelog v3:
- Try to address kbuild failure
- Initialize paca->irq to a sane value
Changelog v2:
- Rename functions as suggested by Nick
- Move irq in paca down for better alignment
- Break the patches up further into interrupt disabling
and soft nmi patches
- Support only PPC_XICS for now
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 (3):
Merge IPI and DEFAULT priorities
Keep interrupts enabled even on soft disable
Enable soft nmi handler
arch/powerpc/include/asm/paca.h | 1 +
arch/powerpc/include/asm/xics.h | 8 ++----
arch/powerpc/kernel/exceptions-64s.S | 33 ++++++++++++++++------
arch/powerpc/kernel/irq.c | 55 ++++++++++++++++++++++++++++++++++--
arch/powerpc/kernel/paca.c | 1 +
arch/powerpc/kernel/time.c | 27 +++++++++++++++++-
6 files changed, 108 insertions(+), 17 deletions(-)
--
2.9.3
next reply other threads:[~2017-01-05 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 4:55 Balbir Singh [this message]
2017-01-05 4:55 ` [PATCH v3 1/3] Merge IPI and DEFAULT priorities Balbir Singh
2017-01-05 4:55 ` [PATCH v3 2/3] Keep interrupts enabled even on soft disable Balbir Singh
2017-01-05 5:12 ` Madhavan Srinivasan
2017-01-06 5:18 ` kbuild test robot
2017-01-05 4:55 ` [PATCH v3 3/3] Enable soft nmi handler Balbir Singh
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=20170105045538.32658-1-bsingharora@gmail.com \
--to=bsingharora@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.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).