| Message ID | 20210107092652.3438696-1-atish.patra@wdc.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | Assorted fixes for RV32 | expand |
Hi Palmer, On Thu, Jan 7, 2021 at 2:57 PM Atish Patra <atish.patra@wdc.com> wrote: > > 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. > > 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 Please consider these fixes for Linux-5.11-rcX. > > 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 > > > _______________________________________________ > linux-riscv mailing list > linux-riscv@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-riscv Regards, Anup
On Thu, 07 Jan 2021 01:26:48 PST (-0800), Atish Patra wrote: > 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. > > 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(-) I took all of them but that L1_CACHE_BYTES one, which I had a comment on. Thanks!
On Wed, 13 Jan 2021 21:09:36 PST (-0800), Palmer Dabbelt wrote: > On Thu, 07 Jan 2021 01:26:48 PST (-0800), Atish Patra wrote: >> 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. >> >> 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(-) > > I took all of them but that L1_CACHE_BYTES one, which I had a comment on. > Thanks! Oops, I just saw the v2. I took those instead, the comment still applies.