Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: H4C70pO/MhtBLrqTuPro3JIiGohP755jApeVaeXbUx3pAnT0DPADY3U+UpSh3TFwjG7nDoWQT2
 H5pXxalskVyBskIroM2U7SPEz7OROas9lPNMU4lVfK35kvTPMtCijp6+HhlV0JbDCnG2dNOPJo
 iXxxuP0IufZgk/uLm35wxkrI6qPLglOnWaRYUKJ8amvJCM1xRs0akDkZdkCHug09wWxs5aWm5Y
 nXzbjKWvip8ck6KctfZZDtOLRz+uoOLC2igbeP8IOQcFsZMFIwsUmIcRl9x8sZ366QNb92zbhy
 /H0=
IronPort-SDR: Jp42Rrun7hoDnfgaKI8QUfaF4RhkqdDOFH1s5vC1gbz1YG9+50nVGbBoOci3n50BcioYCNPrfq
 k0K8kjL+vHYImEjsmnqyiHg0O17Bd44ymmIVQATHRbQsGUbJhl3Ogk0930JHea7opJrJx9n/0B
 O6s58l2GhtStay9LYCJ4dsxuGlWYh/rgjrUXkeNI4Keo+vt8QOppo0/xnt7gYTRGKuVBeTA4EB
 fa8gAmWIG/OKF0llAr6qZ8ZJkYA8hmzfSer9/pcegb4Ub5XcFA/8QFRSKPuOSnEe254/bLgXpN
 RquS1yGBcQ6s40MbvGB0SCjt
IronPort-SDR: EQInO/9vri52nvmIWcEUHszD8BfL0SIUPoaYPJJMgKnCYS7YpuPA11r9okTng8jkPiD9/T4zoN
 nDK7ZZbZ+o35kmz5ht5VhN9IuKBxz8SQYNrHp620y6/g3erpMgJ0nxtzqxrRLqYuYqHeZePpMl
 0hjx8o4X9fXPR+AVpGucJCVncJeZDkbIRMH9B1+RFfcqurTCgEGYu3XXbfd5nhr4UF38mV2XPn
 bhX4YrOVKcarwsjP0C0bc6+moIW0MGVkGh0hxtrXMHFBa8vkaPDF3Qj5zKFdiNbT636BzWI/8U
 2hc=
WDCIronportException: Internal
From:   Atish Patra <atish.patra@wdc.com>
To:     linux-kernel@vger.kernel.org
Cc:     Atish Patra <atish.patra@wdc.com>,
        Albert Ou <aou@eecs.berkeley.edu>,
        Andrew Morton <akpm@linux-foundation.org>,
        Anup Patel <anup@brainfault.org>,
        Ard Biesheuvel <ardb@kernel.org>,
        linux-riscv@lists.infradead.org, Mike Rapoport <rppt@kernel.org>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        Paul Walmsley <paul.walmsley@sifive.com>
Subject: [PATCH v2 0/4] Assorted fixes for RV32
Date:   Mon, 11 Jan 2021 15:45:00 -0800
Message-Id: <20210111234504.3782179-1-atish.patra@wdc.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

This series fixes various issues observed in latest kernel on RV32.
The first two patches fixes an resource tree introduced in 5.11-rc1
while the last two fixes the case where 2GB physical memory is used
on RV32.

There are may be better way to fix the issue pointed out in PATCH 3
as it seems a generic kernel issue where kernel pointers can not use
last 4k of addressable memory. I am open to other better alternate
suggestions.

Changes from v1->v2:
1. Added Reviewed/Tested by tags.
2. Replaced PHYS_ADDR_MAX with explicit __pa(~(ulong)0).

Atish Patra (4):
RISC-V: Do not allocate memblock while iterating reserved memblocks
RISC-V: Set current memblock limit
RISC-V: Fix L1_CACHE_BYTES for RV32
RISC-V: Fix maximum allowed phsyical memory for RV32

arch/riscv/Kconfig             |  6 ++++--
arch/riscv/include/asm/cache.h |  4 ++++
arch/riscv/kernel/setup.c      | 24 +++++++++++++-----------
arch/riscv/mm/init.c           | 16 ++++++++++++++--
4 files changed, 35 insertions(+), 15 deletions(-)

--
2.25.1