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;
Message-ID: <tencent_72C3F44CD3565F83575F5632D9574C331208@qq.com>
Date:   Sun, 11 Jun 2023 07:31:03 +0800
From:   Woody Zhang <woodylab@foxmail.com>
To:     Conor Dooley <conor@kernel.org>
Cc:     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>,
        linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: move memblock_allow_resize() after lm is ready
References: <tencent_D656D683705F41324657ED3393C3384C7408@qq.com>
 <20230610-ultimate-moisture-630c7672358b@spud>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20230610-ultimate-moisture-630c7672358b@spud>
Precedence: bulk

On Sat, Jun 10, 2023 at 04:44:19PM +0100, Conor Dooley wrote:
>On Sat, Jun 10, 2023 at 07:43:20AM +0800, Woody Zhang wrote:
>$subject: "riscv: move memblock_allow_resize() after lm is ready"
>
>s/lm/linear map/ if you resubmit, please.

Thanks, will send a v2.

>
>> 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.
>> 
>> Signed-off-by: Woody Zhang <woodylab@foxmail.com>
>
>What commit does this fix?

Fixes: 671f9a3e2e24 ("RISC-V: Setup initial page tables in two stages")

Will add this tag in v2.

Woody