From: Linus Walleij <linus.walleij@linaro.org>
To: Russell King <linux@armlinux.org.uk>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Arnd Bergmann <arnd@arndb.de>, Nicolas Pitre <nico@fluxnic.net>,
Linus Walleij <linus.walleij@linaro.org>,
Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] RFC: ARM section mapping debug prints
Date: Fri, 4 Sep 2020 10:19:46 +0200 [thread overview]
Message-ID: <20200904081949.5594-1-linus.walleij@linaro.org> (raw)
I just toss this out there to see if there is any general
interest. What the patches do is provide a printout of all
the very early section mappings right before the kernel
switches to execute from virtual memory.
I did this as part of troubleshooting KASan to see if the
problem was related to early boot and early section
mapping. It wasn't.
However if people find this useful I can polish it up with
your review comments and submit it to Russells patch tracker.
Linus Walleij (3):
RFC: ARM: head: Use non-conditional instructions
RFC: ARM: head: Save lr in r11 while setting up page tables
RFC: ARM: head: Debug prints for section mappings
arch/arm/Kconfig.debug | 13 ++++-
arch/arm/kernel/head.S | 129 ++++++++++++++++++++++++++++++++++++++---
2 files changed, 132 insertions(+), 10 deletions(-)
--
2.26.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-09-04 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 8:19 Linus Walleij [this message]
2020-09-04 8:19 ` [PATCH 1/3] RFC: ARM: head: Use non-conditional instructions Linus Walleij
2020-09-04 8:19 ` [PATCH 2/3] RFC: ARM: head: Save lr in r11 while setting up page tables Linus Walleij
2020-09-04 14:53 ` Nicolas Pitre
2020-09-04 8:19 ` [PATCH 3/3] RFC: ARM: head: Debug prints for section mappings Linus Walleij
2020-09-04 15:51 ` Nicolas Pitre
2020-09-04 18:33 ` Nicolas Pitre
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=20200904081949.5594-1-linus.walleij@linaro.org \
--to=linus.walleij@linaro.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=nico@fluxnic.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.