Re: [RFC PATCH 1/5] mm: print more information about mapping in __dump_page

2018-11-25 Thread Michal Hocko
On Fri 23-11-18 16:04:04, Andrew Morton wrote: > On Wed, 7 Nov 2018 11:18:26 +0100 Michal Hocko wrote: > > > From: Michal Hocko > > > > __dump_page prints the mapping pointer but that is quite unhelpful > > for many reports because the pointer itself only helps to distinguish > > anon/ksm

Re: [RFC PATCH 1/5] mm: print more information about mapping in __dump_page

2018-11-25 Thread Michal Hocko
On Fri 23-11-18 16:04:04, Andrew Morton wrote: > On Wed, 7 Nov 2018 11:18:26 +0100 Michal Hocko wrote: > > > From: Michal Hocko > > > > __dump_page prints the mapping pointer but that is quite unhelpful > > for many reports because the pointer itself only helps to distinguish > > anon/ksm

Re: [RFC PATCH 1/5] mm: print more information about mapping in __dump_page

2018-11-23 Thread Andrew Morton
On Wed, 7 Nov 2018 11:18:26 +0100 Michal Hocko wrote: > From: Michal Hocko > > __dump_page prints the mapping pointer but that is quite unhelpful > for many reports because the pointer itself only helps to distinguish > anon/ksm mappings from other ones (because of lowest bits > set).

Re: [RFC PATCH 1/5] mm: print more information about mapping in __dump_page

2018-11-23 Thread Andrew Morton
On Wed, 7 Nov 2018 11:18:26 +0100 Michal Hocko wrote: > From: Michal Hocko > > __dump_page prints the mapping pointer but that is quite unhelpful > for many reports because the pointer itself only helps to distinguish > anon/ksm mappings from other ones (because of lowest bits > set).