[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201031091846.GA30512@infradead.org>
Date: Sat, 31 Oct 2020 09:18:46 +0000
From: Christoph Hellwig <hch@...radead.org>
To: Mike Rapoport <rppt@...nel.org>
Cc: Sudarshan Rajagopalan <sudaraja@...eaurora.org>,
Mark Rutland <mark.rutland@....com>,
David Hildenbrand <david@...hat.com>,
Catalin Marinas <catalin.marinas@....com>,
Anshuman Khandual <anshuman.khandual@....com>,
linux-kernel@...r.kernel.org, Steven Price <steven.price@....com>,
Suren Baghdasaryan <surenb@...gle.com>,
Greg Kroah-Hartman <gregkh@...gle.com>,
Will Deacon <will@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
Pratik Patel <pratikp@...eaurora.org>
Subject: Re: mm/memblock: export memblock_{start/end}_of_DRAM
On Fri, Oct 30, 2020 at 10:38:42AM +0200, Mike Rapoport wrote:
>
> What do you mean by "system memory block"? There could be a lot of
> interpretations if you take into account memory hotplug, "mem=" option,
> reserved and firmware memory.
>
> I'd suggest you to describe the entire use case in more detail. Having
> the complete picture would help finding a proper solution.
I think we need the code for the driver trying to do this as an RFC
submission. Everything else is rather pointless.
Powered by blists - more mailing lists