From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] arm64: relax Image placement requirement
Date: Mon, 23 Mar 2015 10:45:37 +0000 [thread overview]
Message-ID: <20150323104536.GA9724@red-moon> (raw)
In-Reply-To: <1427101646-465-1-git-send-email-ard.biesheuvel@linaro.org>
On Mon, Mar 23, 2015 at 09:07:23AM +0000, Ard Biesheuvel wrote:
> So as it turns out, the 512 MB alignment boundary restriction appears
> to have been introduced by accident when increasing the ID map to cover
> the entire kernel Image.
>
> So this reverts that change, by reducing the ID map to something that
> can never cross a 512 MB boundary by construction.
>
> Patch #1 removes some functions that are unused, so that I don't have
> to worry about them in patch #2
>
> Patch #2 introduces the reduced ID map, using a separate linker section
> that contains code the manipulates the state of the MMU.
>
> Patch #3 removes the sleep_idmap_phys global which always points to
> the ID map anyway
Patch 1 and 2 do not apply for me, what tree/commit are they based against ?
Please let me know so that I can give patch 3 a go.
Thanks,
Lorenzo
>
>
> Ard Biesheuvel (3):
> arm64: remove soft_restart() and friends
> arm64: reduce ID map to a single page
> arm64: drop sleep_idmap_phys
>
> arch/arm64/include/asm/mmu.h | 1 -
> arch/arm64/include/asm/proc-fns.h | 3 ---
> arch/arm64/include/asm/system_misc.h | 1 -
> arch/arm64/kernel/head.S | 13 +++++++------
> arch/arm64/kernel/process.c | 12 +-----------
> arch/arm64/kernel/sleep.S | 9 ++++-----
> arch/arm64/kernel/suspend.c | 3 ---
> arch/arm64/kernel/vmlinux.lds.S | 11 ++++++++++-
> arch/arm64/mm/mmu.c | 11 -----------
> arch/arm64/mm/proc.S | 33 ---------------------------------
> 10 files changed, 22 insertions(+), 75 deletions(-)
>
> --
> 1.8.3.2
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2015-03-23 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 17:02 [PATCH] arm64: relax Image placement requirement Ard Biesheuvel
2015-03-20 17:49 ` Ard Biesheuvel
2015-03-22 15:36 ` Ard Biesheuvel
2015-03-23 9:07 ` [PATCH v2 0/3] " Ard Biesheuvel
2015-03-23 9:07 ` [PATCH v2 1/3] arm64: remove soft_restart() and friends Ard Biesheuvel
2015-03-23 9:32 ` Ard Biesheuvel
2015-03-23 9:07 ` [PATCH v2 2/3] arm64: reduce ID map to a single page Ard Biesheuvel
2015-03-23 9:07 ` [PATCH v2 3/3] arm64: drop sleep_idmap_phys Ard Biesheuvel
2015-03-23 15:58 ` Lorenzo Pieralisi
2015-03-23 16:29 ` Ard Biesheuvel
2015-03-23 10:45 ` Lorenzo Pieralisi [this message]
2015-03-23 10:59 ` [PATCH v2 0/3] arm64: relax Image placement requirement Ard Biesheuvel
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=20150323104536.GA9724@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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.