All of lore.kernel.org
 help / color / mirror / Atom feed
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.patel@wdc.com>, 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>,
	Nick Kossifidis <mick@ics.forth.gr>
Subject: [PATCH 0/4] Assorted fixes for RV32
Date: Thu,  7 Jan 2021 01:26:48 -0800	[thread overview]
Message-ID: <20210107092652.3438696-1-atish.patra@wdc.com> (raw)

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(-)

--
2.25.1


WARNING: multiple messages have this Message-ID (diff)
From: Atish Patra <atish.patra@wdc.com>
To: linux-kernel@vger.kernel.org
Cc: Albert Ou <aou@eecs.berkeley.edu>,
	Anup Patel <anup.patel@wdc.com>,
	linux-riscv@lists.infradead.org,
	Atish Patra <atish.patra@wdc.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Nick Kossifidis <mick@ics.forth.gr>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ard Biesheuvel <ardb@kernel.org>, Mike Rapoport <rppt@kernel.org>
Subject: [PATCH 0/4] Assorted fixes for RV32
Date: Thu,  7 Jan 2021 01:26:48 -0800	[thread overview]
Message-ID: <20210107092652.3438696-1-atish.patra@wdc.com> (raw)

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(-)

--
2.25.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2021-01-07  9:28 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07  9:26 Atish Patra [this message]
2021-01-07  9:26 ` [PATCH 0/4] Assorted fixes for RV32 Atish Patra
2021-01-07  9:26 ` [PATCH 1/4] RISC-V: Do not allocate memblock while iterating reserved memblocks Atish Patra
2021-01-07  9:26   ` Atish Patra
2021-01-08 16:25   ` Geert Uytterhoeven
2021-01-08 16:25     ` Geert Uytterhoeven
2021-01-11  3:54   ` Anup Patel
2021-01-11  3:54     ` Anup Patel
2021-01-07  9:26 ` [PATCH 2/4] RISC-V: Set current memblock limit Atish Patra
2021-01-07  9:26   ` Atish Patra
2021-01-11  3:58   ` Anup Patel
2021-01-11  3:58     ` Anup Patel
2021-01-11 19:20     ` Atish Patra
2021-01-11 19:20       ` Atish Patra
2021-01-07  9:26 ` [PATCH 3/4] RISC-V: Fix L1_CACHE_BYTES for RV32 Atish Patra
2021-01-07  9:26   ` Atish Patra
2021-01-08 16:26   ` Geert Uytterhoeven
2021-01-08 16:26     ` Geert Uytterhoeven
2021-01-11  4:00   ` Anup Patel
2021-01-11  4:00     ` Anup Patel
2021-01-14  5:09   ` Palmer Dabbelt
2021-01-14  5:09     ` Palmer Dabbelt
2021-01-14 18:33     ` Atish Patra
2021-01-14 18:33       ` Atish Patra
2021-01-14 19:46       ` Palmer Dabbelt
2021-01-14 19:46         ` Palmer Dabbelt
2021-01-14 21:11         ` Atish Patra
2021-01-14 21:11           ` Atish Patra
2021-01-14 21:24           ` Palmer Dabbelt
2021-01-14 21:24             ` Palmer Dabbelt
2021-01-15  7:59           ` Geert Uytterhoeven
2021-01-15  7:59             ` Geert Uytterhoeven
2021-01-15 22:44             ` Palmer Dabbelt
2021-01-15 22:44               ` Palmer Dabbelt
2021-01-17 19:03               ` Geert Uytterhoeven
2021-01-17 19:03                 ` Geert Uytterhoeven
2021-01-20 10:59                 ` Geert Uytterhoeven
2021-01-20 10:59                   ` Geert Uytterhoeven
2021-01-16  1:39             ` Atish Patra
2021-01-16  1:39               ` Atish Patra
2021-01-17 18:55               ` Geert Uytterhoeven
2021-01-17 18:55                 ` Geert Uytterhoeven
2021-03-12 15:52       ` Geert Uytterhoeven
2021-03-12 15:52         ` Geert Uytterhoeven
2021-01-07  9:26 ` [PATCH 4/4] RISC-V: Fix maximum allowed phsyical memory " Atish Patra
2021-01-07  9:26   ` Atish Patra
2021-01-11  4:04   ` Anup Patel
2021-01-11  4:04     ` Anup Patel
2021-01-11  4:05 ` [PATCH 0/4] Assorted fixes " Anup Patel
2021-01-11  4:05   ` Anup Patel
2021-01-14  5:09 ` Palmer Dabbelt
2021-01-14  5:09   ` Palmer Dabbelt
2021-01-14  5:12   ` Palmer Dabbelt
2021-01-14  5:12     ` Palmer Dabbelt

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=20210107092652.3438696-1-atish.patra@wdc.com \
    --to=atish.patra@wdc.com \
    --cc=akpm@linux-foundation.org \
    --cc=anup.patel@wdc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=ardb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mick@ics.forth.gr \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rppt@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 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.