From: "Cédric Le Goater" <clg@kaod.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, "Greg Kurz" <groug@kaod.org>,
"Cédric Le Goater" <clg@kaod.org>
Subject: [PATCH 0/4] powerpc/xive: fixes and debug extensions
Date: Fri, 6 Mar 2020 16:01:39 +0100 [thread overview]
Message-ID: <20200306150143.5551-1-clg@kaod.org> (raw)
Hello,
First two patches are fixes for non-critical issues. I checked that
they applied on stable.
Last two are debug extensions, one for xmon and the other to dump XIVE
internal state under debugfs, which is easier than xmon.
Cheers,
C.
Cédric Le Goater (4):
powerpc/xive: Use XIVE_BAD_IRQ instead of zero to catch non configured
IPIs
powerpc/xive: Fix xmon support on the PowerNV platform
powerpc/xmon: Add source flags to output of XIVE interrupts
powerpc/xive: Add a debugfs file to dump internal XIVE state
arch/powerpc/sysdev/xive/xive-internal.h | 9 ++
arch/powerpc/sysdev/xive/common.c | 126 +++++++++++++++++++++--
arch/powerpc/sysdev/xive/native.c | 7 +-
arch/powerpc/sysdev/xive/spapr.c | 23 ++++-
4 files changed, 151 insertions(+), 14 deletions(-)
--
2.21.1
next reply other threads:[~2020-03-06 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 15:01 Cédric Le Goater [this message]
2020-03-06 15:01 ` [PATCH 1/4] powerpc/xive: Use XIVE_BAD_IRQ instead of zero to catch non configured IPIs Cédric Le Goater
2020-03-10 5:17 ` David Gibson
2020-03-10 15:09 ` Greg Kurz
2020-03-10 16:07 ` Cédric Le Goater
2020-04-01 12:53 ` Michael Ellerman
2020-03-06 15:01 ` [PATCH 2/4] powerpc/xive: Fix xmon support on the PowerNV platform Cédric Le Goater
2020-03-10 15:38 ` Greg Kurz
2020-03-06 15:01 ` [PATCH 3/4] powerpc/xmon: Add source flags to output of XIVE interrupts Cédric Le Goater
2020-03-10 15:43 ` Greg Kurz
2020-03-06 15:01 ` [PATCH 4/4] powerpc/xive: Add a debugfs file to dump internal XIVE state Cédric Le Goater
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=20200306150143.5551-1-clg@kaod.org \
--to=clg@kaod.org \
--cc=groug@kaod.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).