Re: [PATCH V4 4/4] arm64/mm: Enable memory hot remove

2019-05-27 Thread David Hildenbrand
On 27.05.19 10:09, Anshuman Khandual wrote: > > > On 05/21/2019 03:50 PM, David Hildenbrand wrote: >> On 20.05.19 07:18, Anshuman Khandual wrote: >>> The arch code for hot-remove must tear down portions of the linear map and >>> vmemmap corresponding to memory being removed. In both cases the pag

Re: [PATCH V4 4/4] arm64/mm: Enable memory hot remove

2019-05-27 Thread David Hildenbrand
On 27.05.19 10:09, Anshuman Khandual wrote: > > > On 05/21/2019 03:50 PM, David Hildenbrand wrote: >> On 20.05.19 07:18, Anshuman Khandual wrote: >>> The arch code for hot-remove must tear down portions of the linear map and >>> vmemmap corresponding to memory being removed. In both cases the pag

Re: [PATCH V4 4/4] arm64/mm: Enable memory hot remove

2019-05-27 Thread Anshuman Khandual
On 05/21/2019 03:50 PM, David Hildenbrand wrote: > On 20.05.19 07:18, Anshuman Khandual wrote: >> The arch code for hot-remove must tear down portions of the linear map and >> vmemmap corresponding to memory being removed. In both cases the page >> tables mapping these regions must be freed, and

Re: [PATCH V4 4/4] arm64/mm: Enable memory hot remove

2019-05-21 Thread David Hildenbrand
On 20.05.19 07:18, Anshuman Khandual wrote: > The arch code for hot-remove must tear down portions of the linear map and > vmemmap corresponding to memory being removed. In both cases the page > tables mapping these regions must be freed, and when sparse vmemmap is in > use the memory backing the v

[PATCH V4 4/4] arm64/mm: Enable memory hot remove

2019-05-19 Thread Anshuman Khandual
The arch code for hot-remove must tear down portions of the linear map and vmemmap corresponding to memory being removed. In both cases the page tables mapping these regions must be freed, and when sparse vmemmap is in use the memory backing the vmemmap must also be freed. This patch adds a new re