[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.21.2010081628100.866917@eddie.linux-mips.org>
Date: Thu, 8 Oct 2020 16:30:35 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...ux-mips.org>
To: Serge Semin <fancer.lancer@...il.com>
cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Hauke Mehrtens <hauke@...ke-m.de>,
Rafał Miłecki <zajec5@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
bcm-kernel-feedback-list@...adcom.com,
Jiaxun Yang <jiaxun.yang@...goat.com>,
Keguang Zhang <keguang.zhang@...il.com>,
John Crispin <john@...ozen.org>, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] MIPS: replace add_memory_region with memblock
On Thu, 8 Oct 2020, Serge Semin wrote:
> At least I don't see a decent reason to preserve them. The memory registration
> method does nearly the same sanity checks. The memory reservation function
> defers a bit in adding the being reserved memory first. That seems redundant,
> since the reserved memory won't be available for the system anyway. Do I miss
> something?
At the very least it serves informational purposes as it shows up in
/proc/iomem.
Maciej
Powered by blists - more mailing lists