Re: [PATCH V6 RESEND 0/3] arm64/mm: Enable memory hot remove

2019-07-30 Thread Anshuman Khandual
On 07/25/2019 07:21 PM, Mark Rutland wrote: > On Wed, Jul 24, 2019 at 12:28:50PM +0530, Anshuman Khandual wrote: >> On 07/23/2019 04:26 PM, Mark Rutland wrote: >>> On Mon, Jul 15, 2019 at 11:47:47AM +0530, Anshuman Khandual wrote: This series enables memory hot remove on arm64 after fixing a

Re: [PATCH V6 RESEND 0/3] arm64/mm: Enable memory hot remove

2019-07-25 Thread Mark Rutland
On Wed, Jul 24, 2019 at 12:28:50PM +0530, Anshuman Khandual wrote: > On 07/23/2019 04:26 PM, Mark Rutland wrote: > > On Mon, Jul 15, 2019 at 11:47:47AM +0530, Anshuman Khandual wrote: > >> This series enables memory hot remove on arm64 after fixing a memblock > >> removal ordering problem in

Re: [PATCH V6 RESEND 0/3] arm64/mm: Enable memory hot remove

2019-07-24 Thread Anshuman Khandual
On 07/23/2019 04:26 PM, Mark Rutland wrote: > Hi Anshuman, Hello Mark, > > On Mon, Jul 15, 2019 at 11:47:47AM +0530, Anshuman Khandual wrote: >> This series enables memory hot remove on arm64 after fixing a memblock >> removal ordering problem in generic try_remove_memory() and a possible >>

Re: [PATCH V6 RESEND 0/3] arm64/mm: Enable memory hot remove

2019-07-23 Thread Mark Rutland
Hi Anshuman, On Mon, Jul 15, 2019 at 11:47:47AM +0530, Anshuman Khandual wrote: > This series enables memory hot remove on arm64 after fixing a memblock > removal ordering problem in generic try_remove_memory() and a possible > arm64 platform specific kernel page table race condition. This series

[PATCH V6 RESEND 0/3] arm64/mm: Enable memory hot remove

2019-07-15 Thread Anshuman Khandual
This series enables memory hot remove on arm64 after fixing a memblock removal ordering problem in generic try_remove_memory() and a possible arm64 platform specific kernel page table race condition. This series is based on linux-next (next-20190712). Concurrent vmalloc() and hot-remove conflict: