Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
In-Reply-To: <tencent_FBB94CE615C5CCE7701CD39C15CCE0EE9706@qq.com>
References: <tencent_FBB94CE615C5CCE7701CD39C15CCE0EE9706@qq.com>
Subject: Re: [PATCH v3] riscv: move memblock_allow_resize() after linear
 mapping is ready
Message-Id: <168860030756.22647.2239697649687317403.b4-ty@rivosinc.com>
Date:   Wed, 05 Jul 2023 16:38:27 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Cc:     linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
From:   Palmer Dabbelt <palmer@rivosinc.com>
To:     Paul Walmsley <paul.walmsley@sifive.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        Albert Ou <aou@eecs.berkeley.edu>,
        Alexandre Ghiti <alexghiti@rivosinc.com>,
        Conor Dooley <conor.dooley@microchip.com>,
        Woody Zhang <woodylab@foxmail.com>
Precedence: bulk


On Wed, 14 Jun 2023 21:19:07 +0800, Woody Zhang wrote:
> The initial memblock metadata is accessed from kernel image mapping. The
> regions arrays need to "reallocated" from memblock and accessed through
> linear mapping to cover more memblock regions. So the resizing should
> not be allowed until linear mapping is ready. Note that there are
> memblock allocations when building linear mapping.
> 
> This patch is similar to 24cc61d8cb5a ("arm64: memblock: don't permit
> memblock resizing until linear mapping is up").
> 
> [...]

Applied, thanks!

[1/1] riscv: move memblock_allow_resize() after linear mapping is ready
      https://git.kernel.org/palmer/c/85fadc0d0411

Best regards,
-- 
Palmer Dabbelt <palmer@rivosinc.com>