From: Oreoluwa Babatunde <quic_obabatun@quicinc.com>
To: <chenhuacai@kernel.org>, <jonas@southpole.se>,
<stefan.kristiansson@saunalahti.fi>, <shorne@gmail.com>,
<ysato@users.sourceforge.jp>, <dalias@libc.org>,
<glaubitz@physik.fu-berlin.de>, <robh+dt@kernel.org>,
<frowand.list@gmail.com>
Cc: <linux-openrisc@vger.kernel.org>, <loongarch@lists.linux.dev>,
<linux-sh@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <kernel@quicinc.com>
Subject: Re: [PATCH 0/3] Restructure init sequence to set aside reserved memory earlier
Date: Tue, 5 Mar 2024 10:59:20 -0800 [thread overview]
Message-ID: <467b8479-dfd8-43a4-92eb-d19dc65989cd@quicinc.com> (raw)
In-Reply-To: <1707524971-146908-1-git-send-email-quic_obabatun@quicinc.com>
On 2/9/2024 4:29 PM, Oreoluwa Babatunde wrote:
> The loongarch, openric, and sh architectures allocate memory from
> memblock before it gets the chance to set aside reserved memory regions.
> This means that there is a possibility for memblock to allocate from
> memory regions that are supposed to be reserved.
>
> This series makes changes to the arch specific setup code to call the
> functions responsible for setting aside the reserved memory regions earlier
> in the init sequence.
> Hence, by the time memblock starts being used to allocate memory, the
> reserved memory regions should already be set aside, and it will no
> longer be possible for allocations to come from them.
>
> I am currnetly using an arm64 device, and so I will need assistance from
> the relevant arch maintainers to help check if this breaks anything from
> compilation to device bootup.
>
> Oreoluwa Babatunde (3):
> loongarch: Call arch_mem_init() before platform_init() in the init
> sequence
> openrisc: Call setup_memory() earlier in the init sequence
> sh: Call paging_init() earlier in the init sequence
>
> arch/loongarch/kernel/setup.c | 2 +-
> arch/openrisc/kernel/setup.c | 6 +++---
> arch/sh/kernel/setup.c | 4 ++--
> 3 files changed, 6 insertions(+), 6 deletions(-)
Hello,
Loongarch patch has already merged for this, but review is still pending
from openrisc and sh architectures.
Could someone please comment on these?
Regards,
Oreoluwa
next prev parent reply other threads:[~2024-03-05 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 0:29 [PATCH 0/3] Restructure init sequence to set aside reserved memory earlier Oreoluwa Babatunde
2024-02-10 0:29 ` [PATCH 1/3] loongarch: Call arch_mem_init() before platform_init() in the init sequence Oreoluwa Babatunde
2024-02-14 13:03 ` Huacai Chen
2024-02-14 21:31 ` Oreoluwa Babatunde
2024-02-15 9:37 ` Huacai Chen
2024-02-10 0:29 ` [PATCH 2/3] openrisc: Call setup_memory() earlier " Oreoluwa Babatunde
2024-03-08 22:27 ` Stafford Horne
2024-02-10 0:29 ` [PATCH 3/3] sh: Call paging_init() " Oreoluwa Babatunde
2024-03-11 16:02 ` Rob Herring
2024-03-05 18:59 ` Oreoluwa Babatunde [this message]
2024-03-08 22:20 ` [PATCH 0/3] Restructure init sequence to set aside reserved memory earlier Stafford Horne
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=467b8479-dfd8-43a4-92eb-d19dc65989cd@quicinc.com \
--to=quic_obabatun@quicinc.com \
--cc=chenhuacai@kernel.org \
--cc=dalias@libc.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jonas@southpole.se \
--cc=kernel@quicinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=ysato@users.sourceforge.jp \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox