Re: [v6 15/15] mm: debug for raw alloctor

2017-08-15 Thread Michal Hocko
On Mon 14-08-17 10:01:52, Pasha Tatashin wrote: > >>However, now thinking about it, I will change it to CONFIG_MEMBLOCK_DEBUG, > >>and let users decide what other debugging configs need to be enabled, as > >>this is also OK. > > > >Actually the more I think about it the more I am convinced that a

Re: [v6 15/15] mm: debug for raw alloctor

2017-08-15 Thread Michal Hocko
On Mon 14-08-17 10:01:52, Pasha Tatashin wrote: > >>However, now thinking about it, I will change it to CONFIG_MEMBLOCK_DEBUG, > >>and let users decide what other debugging configs need to be enabled, as > >>this is also OK. > > > >Actually the more I think about it the more I am convinced that a

Re: [v6 15/15] mm: debug for raw alloctor

2017-08-14 Thread Pasha Tatashin
However, now thinking about it, I will change it to CONFIG_MEMBLOCK_DEBUG, and let users decide what other debugging configs need to be enabled, as this is also OK. Actually the more I think about it the more I am convinced that a kernel boot parameter would be better because it doesn't need

Re: [v6 15/15] mm: debug for raw alloctor

2017-08-14 Thread Pasha Tatashin
However, now thinking about it, I will change it to CONFIG_MEMBLOCK_DEBUG, and let users decide what other debugging configs need to be enabled, as this is also OK. Actually the more I think about it the more I am convinced that a kernel boot parameter would be better because it doesn't need

Re: [v6 15/15] mm: debug for raw alloctor

2017-08-14 Thread Michal Hocko
On Fri 11-08-17 12:18:24, Pasha Tatashin wrote: > >>When CONFIG_DEBUG_VM is enabled, this patch sets all the memory that is > >>returned by memblock_virt_alloc_try_nid_raw() to ones to ensure that no > >>places excpect zeroed memory. > > > >Please fold this into the patch which introduces >

Re: [v6 15/15] mm: debug for raw alloctor

2017-08-14 Thread Michal Hocko
On Fri 11-08-17 12:18:24, Pasha Tatashin wrote: > >>When CONFIG_DEBUG_VM is enabled, this patch sets all the memory that is > >>returned by memblock_virt_alloc_try_nid_raw() to ones to ensure that no > >>places excpect zeroed memory. > > > >Please fold this into the patch which introduces >

Re: [v6 15/15] mm: debug for raw alloctor

2017-08-11 Thread Pasha Tatashin
When CONFIG_DEBUG_VM is enabled, this patch sets all the memory that is returned by memblock_virt_alloc_try_nid_raw() to ones to ensure that no places excpect zeroed memory. Please fold this into the patch which introduces memblock_virt_alloc_try_nid_raw. OK I am not sure CONFIG_DEBUG_VM is

Re: [v6 15/15] mm: debug for raw alloctor

2017-08-11 Thread Pasha Tatashin
When CONFIG_DEBUG_VM is enabled, this patch sets all the memory that is returned by memblock_virt_alloc_try_nid_raw() to ones to ensure that no places excpect zeroed memory. Please fold this into the patch which introduces memblock_virt_alloc_try_nid_raw. OK I am not sure CONFIG_DEBUG_VM is

Re: [v6 15/15] mm: debug for raw alloctor

2017-08-11 Thread Michal Hocko
On Mon 07-08-17 16:38:49, Pavel Tatashin wrote: > When CONFIG_DEBUG_VM is enabled, this patch sets all the memory that is > returned by memblock_virt_alloc_try_nid_raw() to ones to ensure that no > places excpect zeroed memory. Please fold this into the patch which introduces

Re: [v6 15/15] mm: debug for raw alloctor

2017-08-11 Thread Michal Hocko
On Mon 07-08-17 16:38:49, Pavel Tatashin wrote: > When CONFIG_DEBUG_VM is enabled, this patch sets all the memory that is > returned by memblock_virt_alloc_try_nid_raw() to ones to ensure that no > places excpect zeroed memory. Please fold this into the patch which introduces