From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH v2 0/5] powerpc/64s: improve boot debugging
Date: Mon, 26 Sep 2022 15:56:15 +1000 [thread overview]
Message-ID: <20220926055620.2676869-1-npiggin@gmail.com> (raw)
This series provides a machine check handler to catch out of
bounds memory accesses in early boot before the MMU is enabled.
Since v1:
- 64e compile fix
Nicholas Piggin (5):
powerpc/64s/interrupt: move early boot ILE fixup into a macro
powerpc/64s: early boot machine check handler
powerpc/64: avoid using r13 in relocate
powerpc/64: don't set boot CPU's r13 to paca until the structure is
set up
powerpc/64s/interrupt: halt early boot interrupts if paca is not set
up
arch/powerpc/include/asm/asm-prototypes.h | 1 +
arch/powerpc/kernel/exceptions-64s.S | 117 +++++++++++++---------
arch/powerpc/kernel/head_64.S | 3 +
arch/powerpc/kernel/reloc_64.S | 14 +--
arch/powerpc/kernel/setup_64.c | 33 ++++--
arch/powerpc/kernel/traps.c | 14 +++
6 files changed, 120 insertions(+), 62 deletions(-)
--
2.37.2
next reply other threads:[~2022-09-26 5:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 5:56 Nicholas Piggin [this message]
2022-09-26 5:56 ` [PATCH v2 1/5] powerpc/64s/interrupt: move early boot ILE fixup into a macro Nicholas Piggin
2022-09-26 5:56 ` [PATCH v2 2/5] powerpc/64s: early boot machine check handler Nicholas Piggin
2022-09-26 5:56 ` [PATCH v2 3/5] powerpc/64: avoid using r13 in relocate Nicholas Piggin
2022-09-26 5:56 ` [PATCH v2 4/5] powerpc/64: don't set boot CPU's r13 to paca until the structure is set up Nicholas Piggin
2022-09-26 5:56 ` [PATCH v2 5/5] powerpc/64s/interrupt: halt early boot interrupts if paca is not " Nicholas Piggin
2022-10-04 13:25 ` [PATCH v2 0/5] powerpc/64s: improve boot debugging 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=20220926055620.2676869-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).