[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201114102853.GA8618@infradead.org>
Date: Sat, 14 Nov 2020 10:28:53 +0000
From: Christoph Hellwig <hch@...radead.org>
To: Sudarshan Rajagopalan <sudaraja@...eaurora.org>
Cc: Anshuman Khandual <anshuman.khandual@....com>,
David Hildenbrand <david@...hat.com>,
Mark Rutland <mark.rutland@....com>,
Steven Price <steven.price@....com>,
Will Deacon <will@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Suren Baghdasaryan <surenb@...gle.com>,
Pratik Patel <pratikp@...eaurora.org>
Subject: Re: [RFC] depopulate_range_driver_managed() for removing page-table
mappings for hot-added memory blocks
On Fri, Nov 13, 2020 at 06:41:22PM -0800, Sudarshan Rajagopalan wrote:
>
> Hello,
>
> When memory blocks are removed, along with removing the memmap entries,
> memory resource and memory block devices, the arch specific
> arch_remove_memory() is called which takes care of tearing down the
> page-tables.
>
> Suppose there???s a usecase where the removed memory blocks will be added
> back into the system at later point,
Stop this crap. If you have a use case post the actual use here,
including code and specs. If you don't have that don't waste peoples
time on your pipe dream.
Powered by blists - more mailing lists