From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH 0/4] powerpc: misc interrupt and context tracking fixes
Date: Fri, 7 Oct 2022 00:04:09 +1000 [thread overview]
Message-ID: <20221006140413.126443-1-npiggin@gmail.com> (raw)
These are several fixes for regressions and bugs that can crash
the host.
Thanks,
Nick
Nicholas Piggin (4):
KVM: PPC: BookS PR-KVM and BookE do not support context tracking
powerpc/64s/interrupt: Perf NMI should not take normal exit path
powerpc/64e/interrupt: Prevent NMI PMI causing a dangerous warning
powerpc/64: Fix perf profiling asynchronous interrupt handlers
arch/powerpc/include/asm/hw_irq.h | 41 ++++++++++++++++++++--------
arch/powerpc/kernel/dbell.c | 2 +-
arch/powerpc/kernel/exceptions-64e.S | 7 +++++
arch/powerpc/kernel/exceptions-64s.S | 14 +++++++++-
arch/powerpc/kernel/interrupt.c | 13 +++++++--
arch/powerpc/kernel/irq.c | 2 +-
arch/powerpc/kernel/time.c | 2 +-
arch/powerpc/kernel/traps.c | 2 --
arch/powerpc/kvm/Kconfig | 4 +++
9 files changed, 66 insertions(+), 21 deletions(-)
--
2.37.2
next reply other threads:[~2022-10-06 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 14:04 Nicholas Piggin [this message]
2022-10-06 14:04 ` [PATCH 1/4] KVM: PPC: BookS PR-KVM and BookE do not support context tracking Nicholas Piggin
2022-10-06 14:04 ` [PATCH 2/4] powerpc/64s/interrupt: Perf NMI should not take normal exit path Nicholas Piggin
2022-10-06 14:04 ` [PATCH 3/4] powerpc/64e/interrupt: Prevent NMI PMI causing a dangerous warning Nicholas Piggin
2022-10-06 14:04 ` [PATCH 4/4] powerpc/64: Fix perf profiling asynchronous interrupt handlers Nicholas Piggin
2022-10-28 11:49 ` (subset) [PATCH 0/4] powerpc: misc interrupt and context tracking fixes Michael Ellerman
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=20221006140413.126443-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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).