Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 13 Feb 2019 20:05:58 +0200
From:   Mike Rapoport <rppt@linux.ibm.com>
To:     Christoph Hellwig <hch@infradead.org>
Cc:     Anup Patel <Anup.Patel@wdc.com>,
        Palmer Dabbelt <palmer@sifive.com>,
        Albert Ou <aou@eecs.berkeley.edu>,
        Atish Patra <Atish.Patra@wdc.com>,
        Paul Walmsley <paul.walmsley@sifive.com>,
        "linux-riscv@lists.infradead.org" <linux-riscv@lists.infradead.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Laura Abbott <labbott@redhat.com>,
        CHANDAN VN <chandan.vn@samsung.com>,
        Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH v4 6/6] RISC-V: Free-up initrd in free_initrd_mem()
References: <20190213063127.28703-1-anup.patel@wdc.com>
 <20190213063127.28703-7-anup.patel@wdc.com>
 <20190213064419.GA27012@infradead.org>
 <20190213073835.GA18267@rapoport-lnx>
 <20190213175415.GA11635@infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190213175415.GA11635@infradead.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Message-Id: <20190213180557.GA15270@rapoport-lnx>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Feb 13, 2019 at 09:54:15AM -0800, Christoph Hellwig wrote:
> On Wed, Feb 13, 2019 at 09:38:36AM +0200, Mike Rapoport wrote:
> > memblock_free() is has no real effect at this point, no idea why arm64
> > calls it.
> 
> Looks like the call was added fairly recently by:
> 
> commit 05c58752f9dce11e396676eb731a620541590ed0
> Author: CHANDAN VN <chandan.vn@samsung.com>
> Date:   Mon Apr 30 09:50:18 2018 +0530
> 
>     arm64: To remove initrd reserved area entry from memblock
> 
> which claims it is to work around the initrd being displayed in
> /sys/kernel/debug/memblock/reserved.
> 
> I really think we need to have common behavior there - either do this
> for all architectures or none.  I've just sent a series that
> consolidates all but a handful of the free_initrd_mem, so implementing
> any common behavior on top of that would be good.

I've just started to look into it today :)
I'll reply on that thread.

-- 
Sincerely yours,
Mike.