[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200916024927.3191-1-thunder.leizhen@huawei.com>
Date: Wed, 16 Sep 2020 10:49:25 +0800
From: Zhen Lei <thunder.leizhen@...wei.com>
To: Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Russell King <rmk+kernel@...linux.org.uk>,
Catalin Marinas <catalin.marinas@....com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
CC: Zhen Lei <thunder.leizhen@...wei.com>,
Libin <huawei.libin@...wei.com>,
Kefeng Wang <wangkefeng.wang@...wei.com>,
Jianguo Chen <chenjianguo3@...wei.com>
Subject: [PATCH v3 0/2] ARM: support PHYS_OFFSET minimum aligned at 64KiB boundary
v2 --> v3:
1. cancel send to "patches@...linux.org.uk", the patches should have been reviewed first.
2. drop the "default n" of the configuration option ARM_PATCH_PHYS_VIRT_RADICAL.
3. remove an unnecessary cast: below (unsigned long). "t" is already unsigned long.
__pv_stub((unsigned long) t, t, "sub", __PV_BITS_23_16);
v1 --> v2:
Nothing changed, but add mail list: patches@...linux.org.uk
v1:
Currently, only support the kernels where the base of physical memory is
at a 16MiB boundary. Because the add/sub instructions only contains 8bits
unrotated value. But we can use one more "add/sub" instructions to handle
bits 23-16, to support PHYS_OFFSET minimum aligned at 64KiB boundary.
This function is required at least by some Huawei boards, such as Hi1380
board. Becuase the kernel Image is loaded at 2MiB boundary.
Zhen Lei (2):
ARM: fix trivial comments in head.S
ARM: support PHYS_OFFSET minimum aligned at 64KiB boundary
arch/arm/Kconfig | 17 ++++++++++++++++-
arch/arm/include/asm/memory.h | 16 +++++++++++++---
arch/arm/kernel/head.S | 31 ++++++++++++++++++++++---------
3 files changed, 51 insertions(+), 13 deletions(-)
--
1.8.3
Powered by blists - more mailing lists