Re: [PATCH] mm: free reserved area's memmap if possiable

On 2017/3/1 18:41, Jisheng Zhang wrote: Add Chen, Catalin On Thu, 16 Feb 2017 09:11:29 +0800 zhouxianrong wrote: On 2017/2/15 15:10, Ard Biesheuvel wrote: On 15 February 2017 at 01:44, zhouxianrong wrote: On 2017/2/14 17:03, Ard Biesheuvel wrote: On 14 February 2017 at 06:53,

Re: [PATCH] mm: free reserved area's memmap if possiable

On 2017/3/1 18:41, Jisheng Zhang wrote: Add Chen, Catalin On Thu, 16 Feb 2017 09:11:29 +0800 zhouxianrong wrote: On 2017/2/15 15:10, Ard Biesheuvel wrote: On 15 February 2017 at 01:44, zhouxianrong wrote: On 2017/2/14 17:03, Ard Biesheuvel wrote: On 14 February 2017 at 06:53,

Re: [PATCH] mm: free reserved area's memmap if possiable

Add Chen, Catalin On Thu, 16 Feb 2017 09:11:29 +0800 zhouxianrong wrote: > > > On 2017/2/15 15:10, Ard Biesheuvel wrote: > > On 15 February 2017 at 01:44, zhouxianrong wrote: > >> > >> > >> On 2017/2/14 17:03, Ard Biesheuvel wrote: > >>> > >>> On 14 February 2017 at 06:53,

Re: [PATCH] mm: free reserved area's memmap if possiable

Add Chen, Catalin On Thu, 16 Feb 2017 09:11:29 +0800 zhouxianrong wrote: > > > On 2017/2/15 15:10, Ard Biesheuvel wrote: > > On 15 February 2017 at 01:44, zhouxianrong wrote: > >> > >> > >> On 2017/2/14 17:03, Ard Biesheuvel wrote: > >>> > >>> On 14 February 2017 at 06:53, wrote: >

Re: [PATCH] mm: free reserved area's memmap if possiable

On 2017/2/15 15:10, Ard Biesheuvel wrote: On 15 February 2017 at 01:44, zhouxianrong wrote: On 2017/2/14 17:03, Ard Biesheuvel wrote: On 14 February 2017 at 06:53, wrote: From: zhouxianrong just like freeing

Re: [PATCH] mm: free reserved area's memmap if possiable

On 2017/2/15 15:10, Ard Biesheuvel wrote: On 15 February 2017 at 01:44, zhouxianrong wrote: On 2017/2/14 17:03, Ard Biesheuvel wrote: On 14 February 2017 at 06:53, wrote: From: zhouxianrong just like freeing no-map area's memmap (gaps of memblock.memory) we could free reserved

Re: [PATCH] mm: free reserved area's memmap if possiable

On 15 February 2017 at 01:44, zhouxianrong wrote: > > > On 2017/2/14 17:03, Ard Biesheuvel wrote: >> >> On 14 February 2017 at 06:53, wrote: >>> >>> From: zhouxianrong >>> >>> just like freeing no-map area's memmap

Re: [PATCH] mm: free reserved area's memmap if possiable

On 15 February 2017 at 01:44, zhouxianrong wrote: > > > On 2017/2/14 17:03, Ard Biesheuvel wrote: >> >> On 14 February 2017 at 06:53, wrote: >>> >>> From: zhouxianrong >>> >>> just like freeing no-map area's memmap (gaps of memblock.memory) >>> we could free reserved area's memmap (areas of

Re: [PATCH] mm: free reserved area's memmap if possiable

On 2017/2/14 17:03, Ard Biesheuvel wrote: On 14 February 2017 at 06:53, wrote: From: zhouxianrong just like freeing no-map area's memmap (gaps of memblock.memory) we could free reserved area's memmap (areas of memblock.reserved) as well

Re: [PATCH] mm: free reserved area's memmap if possiable

On 2017/2/14 17:03, Ard Biesheuvel wrote: On 14 February 2017 at 06:53, wrote: From: zhouxianrong just like freeing no-map area's memmap (gaps of memblock.memory) we could free reserved area's memmap (areas of memblock.reserved) as well only when user of reserved area indicate that we can

Re: [PATCH] mm: free reserved area's memmap if possiable

On 14 February 2017 at 06:53, wrote: > From: zhouxianrong > > just like freeing no-map area's memmap (gaps of memblock.memory) > we could free reserved area's memmap (areas of memblock.reserved) > as well only when user of reserved area indicate

Re: [PATCH] mm: free reserved area's memmap if possiable

On 14 February 2017 at 06:53, wrote: > From: zhouxianrong > > just like freeing no-map area's memmap (gaps of memblock.memory) > we could free reserved area's memmap (areas of memblock.reserved) > as well only when user of reserved area indicate that we can do > this in drivers. that is, user

Re: [PATCH] mm: free reserved area's memmap if possiable

if the reserved area by user were so big which caused the memmap big, and the reserved area's memamp did not be used by kernel, then user could free the the reserved area's memamp by memblock_mark_raw_pfn interface which is added by me. On 2017/2/14 14:53, zhouxianr...@huawei.com wrote: From:

Re: [PATCH] mm: free reserved area's memmap if possiable

if the reserved area by user were so big which caused the memmap big, and the reserved area's memamp did not be used by kernel, then user could free the the reserved area's memamp by memblock_mark_raw_pfn interface which is added by me. On 2017/2/14 14:53, zhouxianr...@huawei.com wrote: From:

[PATCH] mm: free reserved area's memmap if possiable

From: zhouxianrong just like freeing no-map area's memmap (gaps of memblock.memory) we could free reserved area's memmap (areas of memblock.reserved) as well only when user of reserved area indicate that we can do this in drivers. that is, user of reserved area know how

[PATCH] mm: free reserved area's memmap if possiable

From: zhouxianrong just like freeing no-map area's memmap (gaps of memblock.memory) we could free reserved area's memmap (areas of memblock.reserved) as well only when user of reserved area indicate that we can do this in drivers. that is, user of reserved area know how to use the reserved area

Re: [PATCH] mm: free reserved area's memmap if possiable

Hi zhouxianrong, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.10-rc8 next-20170213] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] mm: free reserved area's memmap if possiable

Hi zhouxianrong, [auto build test ERROR on arm64/for-next/core] [also build test ERROR on v4.10-rc8 next-20170213] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] mm: free reserved area's memmap if possiable

On Mon, Feb 13, 2017 at 12:17:00PM +, Will Deacon wrote: > Adding linux-arm-kernel and devicetree (look for "raw-pfn"), since this > impacts directly on those. > > On Mon, Feb 13, 2017 at 08:02:29PM +0800, zhouxianr...@huawei.com wrote: > > From: zhouxianrong > > >

Re: [PATCH] mm: free reserved area's memmap if possiable

On Mon, Feb 13, 2017 at 12:17:00PM +, Will Deacon wrote: > Adding linux-arm-kernel and devicetree (look for "raw-pfn"), since this > impacts directly on those. > > On Mon, Feb 13, 2017 at 08:02:29PM +0800, zhouxianr...@huawei.com wrote: > > From: zhouxianrong > > > > just like freeing

Re: [PATCH] mm: free reserved area's memmap if possiable

Adding linux-arm-kernel and devicetree (look for "raw-pfn"), since this impacts directly on those. On Mon, Feb 13, 2017 at 08:02:29PM +0800, zhouxianr...@huawei.com wrote: > From: zhouxianrong > > just like freeing no-map area's memmap we could free reserved > area's

Re: [PATCH] mm: free reserved area's memmap if possiable

Adding linux-arm-kernel and devicetree (look for "raw-pfn"), since this impacts directly on those. On Mon, Feb 13, 2017 at 08:02:29PM +0800, zhouxianr...@huawei.com wrote: > From: zhouxianrong > > just like freeing no-map area's memmap we could free reserved > area's memmap as well only when

[PATCH] mm: free reserved area's memmap if possiable

From: zhouxianrong just like freeing no-map area's memmap we could free reserved area's memmap as well only when user of reserved area indicate that we can do this in dts or drivers. that is, user of reserved area know how to use the reserved area who could not

[PATCH] mm: free reserved area's memmap if possiable

From: zhouxianrong just like freeing no-map area's memmap we could free reserved area's memmap as well only when user of reserved area indicate that we can do this in dts or drivers. that is, user of reserved area know how to use the reserved area who could not memblock_free or free_reserved_xxx