From: Stefan Agner <stefan@agner.ch>
To: linux@arm.linux.org.uk
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Mark Salter <msalter@redhat.com>,
Kees Cook <keescook@chromium.org>,
Laura Abbott <lauraa@codeaurora.org>,
Arnd Bergmann <arnd@arndb.de>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v4] ARM: early fixmap support for earlycon
Date: Thu, 30 Jul 2015 23:02:38 +0200 [thread overview]
Message-ID: <00498073e34373292dd053cdb700ff25@agner.ch> (raw)
In-Reply-To: <1434491507-6208-1-git-send-email-stefan@agner.ch>
On 2015-06-16 23:51, Stefan Agner wrote:
> static void __init devicemaps_init(const struct machine_desc *mdesc)
> {
> @@ -1231,7 +1272,10 @@ static void __init devicemaps_init(const struct
> machine_desc *mdesc)
>
> early_trap_init(vectors);
>
> - for (addr = VMALLOC_START; addr; addr += PMD_SIZE)
> + /*
> + * Clear page table except top pmd used by early fixmaps
> + */
> + for (addr = VMALLOC_START; addr < (FIXADDR_TOP & PMD_MASK); addr += PMD_SIZE)
> pmd_clear(pmd_off_k(addr));
>
Hi Russel,
Checked this again, v4 does the right thing:
FIXADDR_TOP (0xffeff000) & PMD_MASK (0xffe00000) gives us the address of
the top PMD (0xFFE00000). We don't clear that since that is taken care
of by early fixmap support (early_fixmap_shutdown). v3 used
FIXADDR_START, which also left out the second to top PMD. The 3MiB of
fixmap spawns two PMD's however only the top PMD is handled by early
fixmap. Hence this was wrong in v3, but is fixed in v4.
Can you reconsider this patch?
--
Stefan
next prev parent reply other threads:[~2015-07-31 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 21:51 Stefan Agner
2015-06-16 22:32 ` Russell King - ARM Linux
2015-06-17 11:43 ` Stefan Agner
2015-06-17 19:43 ` Russell King - ARM Linux
2015-07-06 6:45 ` Stefan Agner
2015-06-16 23:22 ` Stephen Boyd
2015-06-17 9:33 ` Ard Biesheuvel
2015-06-30 12:33 ` Heiko Stübner
2015-07-30 21:02 ` Stefan Agner [this message]
2015-08-08 17:53 ` Russell King - ARM Linux
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=00498073e34373292dd053cdb700ff25@agner.ch \
--to=stefan@agner.ch \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=lauraa@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=msalter@redhat.com \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®