From: Nishanth Menon <nm@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
santosh.shilimkar@oracle.com,
Russell King <linux@armlinux.org.uk>,
Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: Map the lowmem and kernel separately
Date: Fri, 30 Jul 2021 15:22:59 -0500 [thread overview]
Message-ID: <20210730202259.dbifugsvry5vjdr7@earthen> (raw)
In-Reply-To: <20210517145719.110966-4-linus.walleij@linaro.org>
On 16:57-20210517, Linus Walleij wrote:
> Using our knowledge of where the physical kernel sections start
> and end we can split mapping of lowmem and kernel apart.
>
[...]
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
We noticed a regression in k2g platforms with this patch.
commit 6e121df14ccd ("ARM: 9090/1: Map the lowmem and kernel
separately")
Boot log: https://pastebin.ubuntu.com/p/Sf3r28D8MR/
Bisect log: https://pastebin.ubuntu.com/p/6PTYpNVFDy/
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-30 20:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 14:57 [PATCH 0/3] Split lowmem and kernel mappings Linus Walleij
2021-05-17 14:57 ` [PATCH 1/3] ARM: Split KERNEL_OFFSET from PAGE_OFFSET Linus Walleij
2021-05-17 14:57 ` [PATCH 2/3] ARM: Define kernel physical section start and end Linus Walleij
2021-05-17 14:57 ` [PATCH 3/3] ARM: Map the lowmem and kernel separately Linus Walleij
2021-07-30 20:22 ` Nishanth Menon [this message]
2021-07-30 22:40 ` Linus Walleij
2021-08-03 10:27 ` Grygorii Strashko
2021-08-03 10:49 ` Russell King (Oracle)
2021-08-03 11:34 ` Linus Walleij
2021-08-04 10:05 ` Linus Walleij
2021-08-04 10:36 ` Russell King (Oracle)
2021-08-04 13:12 ` Linus Walleij
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=20210730202259.dbifugsvry5vjdr7@earthen \
--to=nm@ti.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=santosh.shilimkar@oracle.com \
/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).