Re: [PATCH 01/11] mm/page_isolation: prefer the node of the source page

2020-05-20 Thread Joonsoo Kim
2020년 5월 21일 (목) 오전 9:37, Roman Gushchin 님이 작성: > > On Mon, May 18, 2020 at 10:20:47AM +0900, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > For locality, it's better to migrate the page to the same node > > rather than the node of the current caller's cpu.

Re: [PATCH 05/18] mm: memcontrol: convert page cache to a new mem_cgroup_charge() API

2020-05-10 Thread Joonsoo Kim
On Fri, May 08, 2020 at 12:01:22PM -0400, Johannes Weiner wrote: > On Thu, Apr 23, 2020 at 02:25:06PM +0900, Joonsoo Kim wrote: > > On Wed, Apr 22, 2020 at 08:09:46AM -0400, Johannes Weiner wrote: > > > On Wed, Apr 22, 2020 at 03:40:41PM +0900, Joonsoo Kim wrote: > > > &

Re: [PATCH v2 03/10] kexec: separate PageHighMem() and PageHighMemZone() use case

2020-05-05 Thread Joonsoo Kim
On Mon, May 04, 2020 at 09:03:56AM -0500, Eric W. Biederman wrote: > > I have added in the kexec mailling list. > > Looking at the patch we are discussing it appears that the kexec code > could be doing much better in highmem situations today but is not. Sound great! >

Re: [PATCH v2 03/10] kexec: separate PageHighMem() and PageHighMemZone() use case

2020-05-03 Thread Joonsoo Kim
2020년 5월 1일 (금) 오후 11:06, Eric W. Biederman 님이 작성: > > js1...@gmail.com writes: > > > From: Joonsoo Kim > > > > Until now, PageHighMem() is used for two different cases. One is to check > > if there is a direct mapping for this page or not. The other is t

Re: [PATCH v2 00/10] change the implementation of the PageHighMem()

2020-05-03 Thread Joonsoo Kim
2020년 5월 1일 (금) 오후 9:34, Christoph Hellwig 님이 작성: > > On Fri, May 01, 2020 at 09:15:30PM +0900, Joonsoo Kim wrote: > > I think that PageHighMemZone() is long and complicated enough to have > > a macro. > > It is. But then again it also shouldn't really be used by anything

Re: [PATCH v2 07/10] mm: separate PageHighMem() and PageHighMemZone() use case

2020-05-03 Thread Joonsoo Kim
2020년 5월 1일 (금) 오후 9:30, Christoph Hellwig 님이 작성: > > On Wed, Apr 29, 2020 at 12:26:40PM +0900, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > Until now, PageHighMem() is used for two different cases. One is to check > > if there is a direct mapping f

Re: [PATCH v2 06/10] mm/hugetlb: separate PageHighMem() and PageHighMemZone() use case

2020-05-03 Thread Joonsoo Kim
2020년 5월 1일 (금) 오후 9:26, Christoph Hellwig 님이 작성: > > On Wed, Apr 29, 2020 at 12:26:39PM +0900, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > Until now, PageHighMem() is used for two different cases. One is to check > > if there is a direct mapping f

Re: [PATCH v2 05/10] mm/gup: separate PageHighMem() and PageHighMemZone() use case

2020-05-03 Thread Joonsoo Kim
2020년 5월 1일 (금) 오후 9:24, Christoph Hellwig 님이 작성: > > On Wed, Apr 29, 2020 at 12:26:38PM +0900, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > Until now, PageHighMem() is used for two different cases. One is to check > > if there is a direct mapping f

Re: [PATCH v2 04/10] power: separate PageHighMem() and PageHighMemZone() use case

2020-05-03 Thread Joonsoo Kim
2020년 5월 1일 (금) 오후 9:22, Christoph Hellwig 님이 작성: > > On Wed, Apr 29, 2020 at 12:26:37PM +0900, js1...@gmail.com wrote: > > index 6598001..be759a6 100644 > > --- a/kernel/power/snapshot.c > > +++ b/kernel/power/snapshot.c > > @@ -1227,7 +1227,7 @@ static struct page *saveable_highmem_page(struct

Re: [PATCH v2 00/10] change the implementation of the PageHighMem()

2020-05-01 Thread Joonsoo Kim
2020년 5월 1일 (금) 오후 7:55, Christoph Hellwig 님이 작성: > > On Fri, May 01, 2020 at 07:52:35PM +0900, Joonsoo Kim wrote: > > > - New code will pop up which gets it wrong and nobody will notice for > > > a long time. > > > > Hmm... I think that it's not that hard t

Re: [PATCH v2 00/10] change the implementation of the PageHighMem()

2020-05-01 Thread Joonsoo Kim
2020년 4월 30일 (목) 오전 10:47, Andrew Morton 님이 작성: > > On Wed, 29 Apr 2020 12:26:33 +0900 js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > Changes on v2 > > - add "acked-by", "reviewed-by" tags > > - replace PageHighMem() with use

Re: [PATCH 16/18] mm: memcontrol: charge swapin pages on instantiation

2020-04-28 Thread Joonsoo Kim
2020년 4월 24일 (금) 오전 11:51, Johannes Weiner 님이 작성: > > On Fri, Apr 24, 2020 at 09:44:42AM +0900, Joonsoo Kim wrote: > > On Mon, Apr 20, 2020 at 06:11:24PM -0400, Johannes Weiner wrote: > > > @@ -412,31 +407,43 @@ struct page *__read_swap_cache_async(swp_entry_t > &

Re: + revert-mm-cma-manage-the-memory-of-the-cma-area-by-using-the-zone_movable.patch added to -mm tree

2018-05-22 Thread Joonsoo Kim
2018-05-23 9:07 GMT+09:00 : > > The patch titled > Subject: Revert "mm/cma: manage the memory of the CMA area by using the > ZONE_MOVABLE" > has been added to the -mm tree. Its filename is > >

Re: + revert-mm-cma-manage-the-memory-of-the-cma-area-by-using-the-zone_movable.patch added to -mm tree

2018-05-22 Thread Joonsoo Kim
2018-05-23 9:07 GMT+09:00 : > > The patch titled > Subject: Revert "mm/cma: manage the memory of the CMA area by using the > ZONE_MOVABLE" > has been added to the -mm tree. Its filename is > > revert-mm-cma-manage-the-memory-of-the-cma-area-by-using-the-zone_movable.patch > > This

Re: [PATCH] Revert "mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE"

2018-05-22 Thread Joonsoo Kim
2018-05-23 9:02 GMT+09:00 Andrew Morton <a...@linux-foundation.org>: > On Mon, 21 May 2018 15:16:33 +0900 Joonsoo Kim <js1...@gmail.com> wrote: > >> > (gdb) list *(dma_direct_alloc+0x22f) >> > 0x573fbf is in dma_direct_alloc (../lib/dma-direct.c:104). >>

Re: [PATCH] Revert "mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE"

2018-05-22 Thread Joonsoo Kim
2018-05-23 9:02 GMT+09:00 Andrew Morton : > On Mon, 21 May 2018 15:16:33 +0900 Joonsoo Kim wrote: > >> > (gdb) list *(dma_direct_alloc+0x22f) >> > 0x573fbf is in dma_direct_alloc (../lib/dma-direct.c:104). >> > 94 >> > 95 if (!page) >

Re: [PATCH] Revert "mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE"

2018-05-21 Thread Joonsoo Kim
On Sat, May 19, 2018 at 05:46:32PM +0300, Ville Syrjälä wrote: > On Fri, May 18, 2018 at 01:01:04PM +0900, Joonsoo Kim wrote: > > On Thu, May 17, 2018 at 10:53:32AM -0700, Laura Abbott wrote: > > > On 05/17/2018 10:08 AM, Michal Hocko wrote: > > > >On Thu 17-05-1

Re: [PATCH] Revert "mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE"

2018-05-21 Thread Joonsoo Kim
On Sat, May 19, 2018 at 05:46:32PM +0300, Ville Syrjälä wrote: > On Fri, May 18, 2018 at 01:01:04PM +0900, Joonsoo Kim wrote: > > On Thu, May 17, 2018 at 10:53:32AM -0700, Laura Abbott wrote: > > > On 05/17/2018 10:08 AM, Michal Hocko wrote: > > > >On Thu 17-05-1

Re: [PATCH] Revert "mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE"

2018-05-17 Thread Joonsoo Kim
with this configuration doesn't hit this bug > because highmem pages are freed via the memblock interface only instead > of iterating through each zone. It looks like the x86 highmem code > assumes only a single highmem zone and/or it's disjoint? Good point! Reason of the crash is that

Re: [PATCH] Revert "mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE"

2018-05-17 Thread Joonsoo Kim
doesn't hit this bug > because highmem pages are freed via the memblock interface only instead > of iterating through each zone. It looks like the x86 highmem code > assumes only a single highmem zone and/or it's disjoint? Good point! Reason of the crash is that the span of MOVABLE_ZONE is

Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG

2018-05-14 Thread Joonsoo Kim
Hello, Mikulas. On Tue, Apr 24, 2018 at 02:41:47PM -0400, Mikulas Patocka wrote: > > > On Tue, 24 Apr 2018, Matthew Wilcox wrote: > > > On Tue, Apr 24, 2018 at 08:29:14AM -0400, Mikulas Patocka wrote: > > > > > > > > > On Mon, 23 Apr 2018, Matthew Wilcox wrote: > > > > > > > On Mon, Apr 23,

Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG

2018-05-14 Thread Joonsoo Kim
Hello, Mikulas. On Tue, Apr 24, 2018 at 02:41:47PM -0400, Mikulas Patocka wrote: > > > On Tue, 24 Apr 2018, Matthew Wilcox wrote: > > > On Tue, Apr 24, 2018 at 08:29:14AM -0400, Mikulas Patocka wrote: > > > > > > > > > On Mon, 23 Apr 2018, Matthew Wilcox wrote: > > > > > > > On Mon, Apr 23,

Re: [PATCH] mm/page_alloc: use ac->high_zoneidx for classzone_idx

2018-05-07 Thread Joonsoo Kim
Hello, Mel. Thanks for precious input! 2018-05-04 19:33 GMT+09:00 Mel Gorman : > On Fri, May 04, 2018 at 09:03:02AM +0200, Vlastimil Babka wrote: >> > min watermark for NORMAL zone on node 0 >> > allocation initiated on node 0: 750 + 4096 = 4846 >> > allocation initiated on node

Re: [PATCH] mm/page_alloc: use ac->high_zoneidx for classzone_idx

2018-05-07 Thread Joonsoo Kim
Hello, Mel. Thanks for precious input! 2018-05-04 19:33 GMT+09:00 Mel Gorman : > On Fri, May 04, 2018 at 09:03:02AM +0200, Vlastimil Babka wrote: >> > min watermark for NORMAL zone on node 0 >> > allocation initiated on node 0: 750 + 4096 = 4846 >> > allocation initiated on node 1: 750 + 0 = 750

Re: [PATCH] mm/page_alloc: use ac->high_zoneidx for classzone_idx

2018-05-04 Thread Joonsoo Kim
2018-05-04 16:03 GMT+09:00 Vlastimil Babka <vba...@suse.cz>: > On 05/04/2018 06:30 AM, js1...@gmail.com wrote: >> From: Joonsoo Kim <iamjoonsoo@lge.com> >> >> Currently, we use the zone index of preferred_zone which represents >> the best matching zone f

Re: [PATCH] mm/page_alloc: use ac->high_zoneidx for classzone_idx

2018-05-04 Thread Joonsoo Kim
2018-05-04 16:03 GMT+09:00 Vlastimil Babka : > On 05/04/2018 06:30 AM, js1...@gmail.com wrote: >> From: Joonsoo Kim >> >> Currently, we use the zone index of preferred_zone which represents >> the best matching zone for allocation, as classzone_idx. It has

Re: [PATCH] mm/thp: don't count ZONE_MOVABLE as the target for freepage reserving

2018-04-05 Thread Joonsoo Kim
On Thu, Apr 05, 2018 at 05:05:39PM +0900, Joonsoo Kim wrote: > On Thu, Apr 05, 2018 at 09:57:53AM +0200, Michal Hocko wrote: > > On Thu 05-04-18 16:27:16, Joonsoo Kim wrote: > > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > > > ZONE_MOVABLE only

Re: [PATCH] mm/thp: don't count ZONE_MOVABLE as the target for freepage reserving

2018-04-05 Thread Joonsoo Kim
On Thu, Apr 05, 2018 at 05:05:39PM +0900, Joonsoo Kim wrote: > On Thu, Apr 05, 2018 at 09:57:53AM +0200, Michal Hocko wrote: > > On Thu 05-04-18 16:27:16, Joonsoo Kim wrote: > > > From: Joonsoo Kim > > > > > > ZONE_MOVABLE only has movable pages so we don't

Re: [PATCH] mm/thp: don't count ZONE_MOVABLE as the target for freepage reserving

2018-04-05 Thread Joonsoo Kim
On Thu, Apr 05, 2018 at 09:57:53AM +0200, Michal Hocko wrote: > On Thu 05-04-18 16:27:16, Joonsoo Kim wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > ZONE_MOVABLE only has movable pages so we don't need to keep enough > > freepages to avoid or d

Re: [PATCH] mm/thp: don't count ZONE_MOVABLE as the target for freepage reserving

2018-04-05 Thread Joonsoo Kim
On Thu, Apr 05, 2018 at 09:57:53AM +0200, Michal Hocko wrote: > On Thu 05-04-18 16:27:16, Joonsoo Kim wrote: > > From: Joonsoo Kim > > > > ZONE_MOVABLE only has movable pages so we don't need to keep enough > > freepages to avoid or deal with fra

Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression

2018-04-05 Thread Joonsoo Kim
Hello, sorry for bothering you. 2018-01-09 16:16 GMT+09:00 Joonsoo Kim <iamjoonsoo@lge.com>: > On Sat, Jan 06, 2018 at 05:26:31PM +0800, Ye Xiaolong wrote: >> Hi, >> >> On 01/03, Joonsoo Kim wrote: >> >Hello! >> > >> >On Tue, Jan

Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression

2018-04-05 Thread Joonsoo Kim
Hello, sorry for bothering you. 2018-01-09 16:16 GMT+09:00 Joonsoo Kim : > On Sat, Jan 06, 2018 at 05:26:31PM +0800, Ye Xiaolong wrote: >> Hi, >> >> On 01/03, Joonsoo Kim wrote: >> >Hello! >> > >> >On Tue, Jan 02, 2018 at 02:35:28PM +080

Re: [PATCH v1] mm: help the ALLOC_HARDER allocation pass the watermarki when CMA on

2018-04-05 Thread Joonsoo Kim
On Wed, Apr 04, 2018 at 03:37:03PM -0700, Andrew Morton wrote: > On Wed, 4 Apr 2018 09:31:10 +0900 Joonsoo Kim <iamjoonsoo@lge.com> wrote: > > > On Fri, Mar 23, 2018 at 01:04:08PM -0700, Andrew Morton wrote: > > > On Fri, 23 Mar 2018 10:33:27 +0100 Michal Hock

Re: [PATCH v1] mm: help the ALLOC_HARDER allocation pass the watermarki when CMA on

2018-04-05 Thread Joonsoo Kim
On Wed, Apr 04, 2018 at 03:37:03PM -0700, Andrew Morton wrote: > On Wed, 4 Apr 2018 09:31:10 +0900 Joonsoo Kim wrote: > > > On Fri, Mar 23, 2018 at 01:04:08PM -0700, Andrew Morton wrote: > > > On Fri, 23 Mar 2018 10:33:27 +0100 Michal Hocko wrote: > > > &g

Re: + mm-slabc-remove-duplicated-check-of-colour_next.patch added to -mm tree

2018-04-03 Thread Joonsoo Kim
ev <sunnydda...@gmail.com> > Acked-by: Christoph Lameter <c...@linux.com> > Acked-by: David Rientjes <rient...@google.com> > Reviewed-by: Andrew Morton <a...@linux-foundation.org> > Cc: Pekka Enberg <penb...@kernel.org> > Cc: Joonsoo Kim <iamjoonsoo@lg

Re: + mm-slabc-remove-duplicated-check-of-colour_next.patch added to -mm tree

2018-04-03 Thread Joonsoo Kim
ab.c: remove duplicated check of colour_next > > Remove check that offset greater than cachep->colour bacause this is > already checked in previous lines. > > Link: http://lkml.kernel.org/r/877eqilr71@gmail.com > Signed-off-by: Roman Lakeev > Acked-by: Christoph

Re: [PATCH v1] mm: help the ALLOC_HARDER allocation pass the watermarki when CMA on

2018-04-03 Thread Joonsoo Kim
On Fri, Mar 23, 2018 at 01:04:08PM -0700, Andrew Morton wrote: > On Fri, 23 Mar 2018 10:33:27 +0100 Michal Hocko wrote: > > > On Fri 23-03-18 17:19:26, Zhaoyang Huang wrote: > > > On Fri, Mar 23, 2018 at 4:38 PM, Michal Hocko wrote: > > > > On Fri 23-03-18

Re: [PATCH v1] mm: help the ALLOC_HARDER allocation pass the watermarki when CMA on

2018-04-03 Thread Joonsoo Kim
On Fri, Mar 23, 2018 at 01:04:08PM -0700, Andrew Morton wrote: > On Fri, 23 Mar 2018 10:33:27 +0100 Michal Hocko wrote: > > > On Fri 23-03-18 17:19:26, Zhaoyang Huang wrote: > > > On Fri, Mar 23, 2018 at 4:38 PM, Michal Hocko wrote: > > > > On Fri 23-03-18 15:57:32, Zhaoyang Huang wrote: > > >

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

2018-04-03 Thread Joonsoo Kim
Hello, Michal. Sorry for a really long delay. 2017-09-14 22:24 GMT+09:00 Michal Hocko <mho...@kernel.org>: > [Sorry for a later reply] > > On Wed 06-09-17 13:35:25, Joonsoo Kim wrote: >> From: Joonsoo Kim <iamjoonsoo@lge.com> >> >> Freepage on ZONE_HI

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

2018-04-03 Thread Joonsoo Kim
Hello, Michal. Sorry for a really long delay. 2017-09-14 22:24 GMT+09:00 Michal Hocko : > [Sorry for a later reply] > > On Wed 06-09-17 13:35:25, Joonsoo Kim wrote: >> From: Joonsoo Kim >> >> Freepage on ZONE_HIGHMEM doesn't work for kernel memory so it's not that >

Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression

2018-01-08 Thread Joonsoo Kim
On Sat, Jan 06, 2018 at 05:26:31PM +0800, Ye Xiaolong wrote: > Hi, > > On 01/03, Joonsoo Kim wrote: > >Hello! > > > >On Tue, Jan 02, 2018 at 02:35:28PM +0800, kernel test robot wrote: > >> > >> Greeting, > >> > >> FYI, w

Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression

2018-01-08 Thread Joonsoo Kim
On Sat, Jan 06, 2018 at 05:26:31PM +0800, Ye Xiaolong wrote: > Hi, > > On 01/03, Joonsoo Kim wrote: > >Hello! > > > >On Tue, Jan 02, 2018 at 02:35:28PM +0800, kernel test robot wrote: > >> > >> Greeting, > >> > >> FYI, w

Re: ACPI issues on cold power on [bisected]

2018-01-02 Thread Joonsoo Kim
On Tue, Jan 02, 2018 at 11:25:01AM +0100, Rafael J. Wysocki wrote: > On Tue, Jan 2, 2018 at 3:54 AM, Joonsoo Kim <iamjoonsoo@lge.com> wrote: > > On Fri, Dec 29, 2017 at 04:36:59PM +, Jonathan McDowell wrote: > >> On Fri, Dec 22, 2017 at 09:21:09AM +0900, Joonsoo

Re: ACPI issues on cold power on [bisected]

2018-01-02 Thread Joonsoo Kim
On Tue, Jan 02, 2018 at 11:25:01AM +0100, Rafael J. Wysocki wrote: > On Tue, Jan 2, 2018 at 3:54 AM, Joonsoo Kim wrote: > > On Fri, Dec 29, 2017 at 04:36:59PM +, Jonathan McDowell wrote: > >> On Fri, Dec 22, 2017 at 09:21:09AM +0900, Joonsoo Kim wrote: > >> >

Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression

2018-01-02 Thread Joonsoo Kim
Hello! On Tue, Jan 02, 2018 at 02:35:28PM +0800, kernel test robot wrote: > > Greeting, > > FYI, we noticed a -16.1% regression of fio.read_bw_MBps due to commit: > > > commit: 2b0f904a5a8781498417d67226fd12c5e56053ae ("mm/cma: manage the memory > of the CMA area by using the ZONE_MOVABLE")

Re: [lkp-robot] [mm/cma] 2b0f904a5a: fio.read_bw_MBps -16.1% regression

2018-01-02 Thread Joonsoo Kim
Hello! On Tue, Jan 02, 2018 at 02:35:28PM +0800, kernel test robot wrote: > > Greeting, > > FYI, we noticed a -16.1% regression of fio.read_bw_MBps due to commit: > > > commit: 2b0f904a5a8781498417d67226fd12c5e56053ae ("mm/cma: manage the memory > of the CMA area by using the ZONE_MOVABLE")

Re: ACPI issues on cold power on [bisected]

2018-01-01 Thread Joonsoo Kim
On Fri, Dec 29, 2017 at 04:36:59PM +, Jonathan McDowell wrote: > On Fri, Dec 22, 2017 at 09:21:09AM +0900, Joonsoo Kim wrote: > > On Fri, Dec 08, 2017 at 03:11:59PM +, Jonathan McDowell wrote: > > > I've been sitting on this for a while and should have spent time to

Re: ACPI issues on cold power on [bisected]

2018-01-01 Thread Joonsoo Kim
On Fri, Dec 29, 2017 at 04:36:59PM +, Jonathan McDowell wrote: > On Fri, Dec 22, 2017 at 09:21:09AM +0900, Joonsoo Kim wrote: > > On Fri, Dec 08, 2017 at 03:11:59PM +, Jonathan McDowell wrote: > > > I've been sitting on this for a while and should have spent time to

Re: [PATCH 00/18] introduce a new tool, valid access checker

2017-12-21 Thread Joonsoo Kim
On Tue, Nov 28, 2017 at 04:48:35PM +0900, js1...@gmail.com wrote: > From: Joonsoo Kim <iamjoonsoo@lge.com> > > Hello, > > This patchset introduces a new tool, valid access checker. > > Vchecker is a dynamic memory error detector. It provides a new debug featur

Re: [PATCH 00/18] introduce a new tool, valid access checker

2017-12-21 Thread Joonsoo Kim
On Tue, Nov 28, 2017 at 04:48:35PM +0900, js1...@gmail.com wrote: > From: Joonsoo Kim > > Hello, > > This patchset introduces a new tool, valid access checker. > > Vchecker is a dynamic memory error detector. It provides a new debug feature > that can find out an un-

Re: ACPI issues on cold power on [bisected]

2017-12-21 Thread Joonsoo Kim
On Fri, Dec 08, 2017 at 03:11:59PM +, Jonathan McDowell wrote: > I've been sitting on this for a while and should have spent time to > investigate sooner, but it's been an odd failure mode that wasn't quite > obvious. > > In 4.9 if I cold power on my laptop (Dell E7240) it fails to boot - I >

Re: ACPI issues on cold power on [bisected]

2017-12-21 Thread Joonsoo Kim
On Fri, Dec 08, 2017 at 03:11:59PM +, Jonathan McDowell wrote: > I've been sitting on this for a while and should have spent time to > investigate sooner, but it's been an odd failure mode that wasn't quite > obvious. > > In 4.9 if I cold power on my laptop (Dell E7240) it fails to boot - I >

Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

2017-12-21 Thread Joonsoo Kim
On Fri, Dec 08, 2017 at 02:37:19PM -0800, Andrew Morton wrote: > On Fri, 1 Dec 2017 16:53:03 +0900 js1...@gmail.com wrote: > > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > v2 > > o previous failure in linux-next turned out that it's not the problem

Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

2017-12-21 Thread Joonsoo Kim
On Fri, Dec 08, 2017 at 02:37:19PM -0800, Andrew Morton wrote: > On Fri, 1 Dec 2017 16:53:03 +0900 js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > v2 > > o previous failure in linux-next turned out that it's not the problem of > > this patchset. I

Re: [PATCH 02/18] vchecker: introduce the valid access checker

2017-12-01 Thread Joonsoo Kim
On Fri, Dec 01, 2017 at 01:08:13PM +0800, kbuild test robot wrote: > Hi Joonsoo, > > I love your patch! Yet something to improve: Thanks! I will fix all the error from kbuild bot on next spin. Thanks.

Re: [PATCH 02/18] vchecker: introduce the valid access checker

2017-12-01 Thread Joonsoo Kim
On Fri, Dec 01, 2017 at 01:08:13PM +0800, kbuild test robot wrote: > Hi Joonsoo, > > I love your patch! Yet something to improve: Thanks! I will fix all the error from kbuild bot on next spin. Thanks.

Re: [PATCH 00/18] introduce a new tool, valid access checker

2017-11-30 Thread Joonsoo Kim
On Wed, Nov 29, 2017 at 10:27:00AM +0100, Dmitry Vyukov wrote: > On Tue, Nov 28, 2017 at 8:48 AM, <js1...@gmail.com> wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > Hello, > > > > This patchset introduces a new tool, valid access checke

Re: [PATCH 00/18] introduce a new tool, valid access checker

2017-11-30 Thread Joonsoo Kim
On Wed, Nov 29, 2017 at 10:27:00AM +0100, Dmitry Vyukov wrote: > On Tue, Nov 28, 2017 at 8:48 AM, wrote: > > From: Joonsoo Kim > > > > Hello, > > > > This patchset introduces a new tool, valid access checker. > > > > Vchecker is a dynamic memory er

Re: [PATCH] mm, compaction: direct freepage allocation for async direct compaction

2017-11-28 Thread Joonsoo Kim
On Wed, Nov 22, 2017 at 03:52:55PM +0100, Vlastimil Babka wrote: > On 11/22/2017 03:33 PM, Johannes Weiner wrote: > > From: Vlastimil Babka > > > > The goal of direct compaction is to quickly make a high-order page available > > for the pending allocation. The free page scanner

Re: [PATCH] mm, compaction: direct freepage allocation for async direct compaction

2017-11-28 Thread Joonsoo Kim
On Wed, Nov 22, 2017 at 03:52:55PM +0100, Vlastimil Babka wrote: > On 11/22/2017 03:33 PM, Johannes Weiner wrote: > > From: Vlastimil Babka > > > > The goal of direct compaction is to quickly make a high-order page available > > for the pending allocation. The free page scanner can add

Re: [PATCH] mm, compaction: direct freepage allocation for async direct compaction

2017-11-28 Thread Joonsoo Kim
On Thu, Nov 23, 2017 at 02:08:43PM +, Mel Gorman wrote: > 3. Another reason a linear scanner was used was because we wanted to >clear entire pageblocks we were migrating from and pack the target >pageblocks as much as possible. This was to reduce the amount of >migration required

Re: [PATCH] mm, compaction: direct freepage allocation for async direct compaction

2017-11-28 Thread Joonsoo Kim
On Thu, Nov 23, 2017 at 02:08:43PM +, Mel Gorman wrote: > 3. Another reason a linear scanner was used was because we wanted to >clear entire pageblocks we were migrating from and pack the target >pageblocks as much as possible. This was to reduce the amount of >migration required

Re: [PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-28 Thread Joonsoo Kim
2 ("mm/cma: always check which page caused allocation > failure") > Cc: <sta...@vger.kernel.org> > Signed-off-by: Mike Kravetz <mike.krav...@oracle.com> Good catch!! Acked-by: Joonsoo Kim <iamjoonsoo@lge.com> Thanks.

Re: [PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

2017-11-28 Thread Joonsoo Kim
2 ("mm/cma: always check which page caused allocation > failure") > Cc: > Signed-off-by: Mike Kravetz Good catch!! Acked-by: Joonsoo Kim Thanks.

Re: [PATCH 02/18] vchecker: introduce the valid access checker

2017-11-28 Thread Joonsoo Kim
On Tue, Nov 28, 2017 at 11:41:08AM -0800, Andi Kleen wrote: > js1...@gmail.com writes: > > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > Looks useful. Essentially unlimited hardware break points, combined > with slab. Thanks!!! > > Didn't do a full revi

Re: [PATCH 02/18] vchecker: introduce the valid access checker

2017-11-28 Thread Joonsoo Kim
On Tue, Nov 28, 2017 at 11:41:08AM -0800, Andi Kleen wrote: > js1...@gmail.com writes: > > > From: Joonsoo Kim > > Looks useful. Essentially unlimited hardware break points, combined > with slab. Thanks!!! > > Didn't do a full review, but noticed some thin

Re: n900 in next-20170901

2017-11-14 Thread Joonsoo Kim
On Tue, Nov 14, 2017 at 06:04:00PM -0800, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171115 00:48]: > > On Tue, Nov 14, 2017 at 09:37:19AM -0800, Tony Lindgren wrote: > > > * Joonsoo Kim <iamjoonsoo@lge.com> [171114 06:34]: > > > >

Re: n900 in next-20170901

2017-11-14 Thread Joonsoo Kim
On Tue, Nov 14, 2017 at 06:04:00PM -0800, Tony Lindgren wrote: > * Joonsoo Kim [171115 00:48]: > > On Tue, Nov 14, 2017 at 09:37:19AM -0800, Tony Lindgren wrote: > > > * Joonsoo Kim [171114 06:34]: > > > > On Fri, Nov 10, 2017 at 07:36:20AM -0800, Tony Lindgren

Re: n900 in next-20170901

2017-11-14 Thread Joonsoo Kim
On Tue, Nov 14, 2017 at 09:37:19AM -0800, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171114 06:34]: > > On Fri, Nov 10, 2017 at 07:36:20AM -0800, Tony Lindgren wrote: > > > * Joonsoo Kim <iamjoonsoo@lge.com> [171110 06:34]: > > > >

Re: n900 in next-20170901

2017-11-14 Thread Joonsoo Kim
On Tue, Nov 14, 2017 at 09:37:19AM -0800, Tony Lindgren wrote: > * Joonsoo Kim [171114 06:34]: > > On Fri, Nov 10, 2017 at 07:36:20AM -0800, Tony Lindgren wrote: > > > * Joonsoo Kim [171110 06:34]: > > > > On Thu, Nov 09, 2017 at 07:26:10PM -0800, Tony Lind

Re: n900 in next-20170901

2017-11-13 Thread Joonsoo Kim
On Mon, Nov 13, 2017 at 01:15:30PM -0800, Tony Lindgren wrote: > * Tony Lindgren <t...@atomide.com> [171110 07:36]: > > * Joonsoo Kim <iamjoonsoo@lge.com> [171110 06:34]: > > > On Thu, Nov 09, 2017 at 07:26:10PM -0800, Tony Lindgren wrote: > > > >

Re: n900 in next-20170901

2017-11-13 Thread Joonsoo Kim
On Mon, Nov 13, 2017 at 01:15:30PM -0800, Tony Lindgren wrote: > * Tony Lindgren [171110 07:36]: > > * Joonsoo Kim [171110 06:34]: > > > On Thu, Nov 09, 2017 at 07:26:10PM -0800, Tony Lindgren wrote: > > > > +#define OMAP34XX_SRAM_PHYS 0x4020 >

Re: n900 in next-20170901

2017-11-13 Thread Joonsoo Kim
On Fri, Nov 10, 2017 at 07:36:20AM -0800, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171110 06:34]: > > On Thu, Nov 09, 2017 at 07:26:10PM -0800, Tony Lindgren wrote: > > > +#define OMAP34XX_SRAM_PHYS 0x4020 > > > +#define OM

Re: n900 in next-20170901

2017-11-13 Thread Joonsoo Kim
On Fri, Nov 10, 2017 at 07:36:20AM -0800, Tony Lindgren wrote: > * Joonsoo Kim [171110 06:34]: > > On Thu, Nov 09, 2017 at 07:26:10PM -0800, Tony Lindgren wrote: > > > +#define OMAP34XX_SRAM_PHYS 0x4020 > > > +#define OMAP34XX_SRAM_VIRT 0xd001 > &

Re: n900 in next-20170901

2017-11-09 Thread Joonsoo Kim
On Thu, Nov 09, 2017 at 10:23:40PM -0800, Tony Lindgren wrote: > * Tony Lindgren [171109 22:19]: > > * Tony Lindgren [171110 03:28]: > > > Then I'll follow up on cleaning up save_secure_ram_context later. > > > > Here's a better version, the static mapping

Re: n900 in next-20170901

2017-11-09 Thread Joonsoo Kim
On Thu, Nov 09, 2017 at 10:23:40PM -0800, Tony Lindgren wrote: > * Tony Lindgren [171109 22:19]: > > * Tony Lindgren [171110 03:28]: > > > Then I'll follow up on cleaning up save_secure_ram_context later. > > > > Here's a better version, the static mapping did not get used.. It > > just moved

Re: n900 in next-20170901

2017-11-09 Thread Joonsoo Kim
On Thu, Nov 09, 2017 at 07:26:10PM -0800, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171110 00:10]: > > On Thu, Nov 09, 2017 at 07:08:54AM -0800, Tony Lindgren wrote: > > > Hmm OK. Does your first patch above now have the initcall issue too? > >

Re: n900 in next-20170901

2017-11-09 Thread Joonsoo Kim
On Thu, Nov 09, 2017 at 07:26:10PM -0800, Tony Lindgren wrote: > * Joonsoo Kim [171110 00:10]: > > On Thu, Nov 09, 2017 at 07:08:54AM -0800, Tony Lindgren wrote: > > > Hmm OK. Does your first patch above now have the initcall issue too? > > > It boots if I mak

Re: n900 in next-20170901

2017-11-09 Thread Joonsoo Kim
On Thu, Nov 09, 2017 at 07:08:54AM -0800, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171109 03:47]: > > Could you test following two commits on my updated branch? > > > > "arm/dma: vmalloc area allocation" > > Won't boot at this c

Re: n900 in next-20170901

2017-11-09 Thread Joonsoo Kim
On Thu, Nov 09, 2017 at 07:08:54AM -0800, Tony Lindgren wrote: > * Joonsoo Kim [171109 03:47]: > > Could you test following two commits on my updated branch? > > > > "arm/dma: vmalloc area allocation" > > Won't boot at this commit: > > [6.

Re: [PATCH] mm: page_ext: check if page_ext is not prepared

2017-11-08 Thread Joonsoo Kim
On Wed, Nov 08, 2017 at 03:21:06PM +0100, Michal Hocko wrote: > On Wed 08-11-17 16:59:56, Joonsoo Kim wrote: > > On Tue, Nov 07, 2017 at 10:47:30AM +0100, Michal Hocko wrote: > > > [CC Joonsoo] > > > > > > On Tue 07-11-17 18:41:31, Jaewon Kim wrote: >

Re: [PATCH] mm: page_ext: check if page_ext is not prepared

2017-11-08 Thread Joonsoo Kim
On Wed, Nov 08, 2017 at 03:21:06PM +0100, Michal Hocko wrote: > On Wed 08-11-17 16:59:56, Joonsoo Kim wrote: > > On Tue, Nov 07, 2017 at 10:47:30AM +0100, Michal Hocko wrote: > > > [CC Joonsoo] > > > > > > On Tue 07-11-17 18:41:31, Jaewon Kim wrote: >

Re: [PATCH] mm: page_ext: allocate page extension though first PFN is invalid

2017-11-08 Thread Joonsoo Kim
On Wed, Nov 08, 2017 at 10:33:51PM +0900, Jaewon Kim wrote: > 2017-11-08 16:52 GMT+09:00 Joonsoo Kim <iamjoonsoo@lge.com>: > > On Tue, Nov 07, 2017 at 06:44:47PM +0900, Jaewon Kim wrote: > >> online_page_ext and page_ext_init allocate page_ext for each section, but &

Re: [PATCH] mm: page_ext: allocate page extension though first PFN is invalid

2017-11-08 Thread Joonsoo Kim
On Wed, Nov 08, 2017 at 10:33:51PM +0900, Jaewon Kim wrote: > 2017-11-08 16:52 GMT+09:00 Joonsoo Kim : > > On Tue, Nov 07, 2017 at 06:44:47PM +0900, Jaewon Kim wrote: > >> online_page_ext and page_ext_init allocate page_ext for each section, but > >> they do no

Re: n900 in next-20170901

2017-11-08 Thread Joonsoo Kim
On Thu, Nov 09, 2017 at 09:36:39AM +0900, Joonsoo Kim wrote: > On Wed, Nov 08, 2017 at 04:11:13PM -0800, Tony Lindgren wrote: > > * Joonsoo Kim <iamjoonsoo@lge.com> [171109 00:05]: > > > On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote: > >

Re: n900 in next-20170901

2017-11-08 Thread Joonsoo Kim
On Thu, Nov 09, 2017 at 09:36:39AM +0900, Joonsoo Kim wrote: > On Wed, Nov 08, 2017 at 04:11:13PM -0800, Tony Lindgren wrote: > > * Joonsoo Kim [171109 00:05]: > > > On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote: > > > > * Joonsoo Kim [171108 07

Re: n900 in next-20170901

2017-11-08 Thread Joonsoo Kim
On Wed, Nov 08, 2017 at 04:11:13PM -0800, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171109 00:05]: > > On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote: > > > * Joonsoo Kim <iamjoonsoo@lge.com> [171108 07:43]: > > > >

Re: n900 in next-20170901

2017-11-08 Thread Joonsoo Kim
On Wed, Nov 08, 2017 at 04:11:13PM -0800, Tony Lindgren wrote: > * Joonsoo Kim [171109 00:05]: > > On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote: > > > * Joonsoo Kim [171108 07:43]: > > > > On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgre

Re: n900 in next-20170901

2017-11-08 Thread Joonsoo Kim
On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171108 07:43]: > > On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote: > > > So it seems the issue is currently at the atomic_pool_init() > > > rela

Re: n900 in next-20170901

2017-11-08 Thread Joonsoo Kim
On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote: > * Joonsoo Kim [171108 07:43]: > > On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote: > > > So it seems the issue is currently at the atomic_pool_init() > > > related code? > > > &

Re: [PATCH] mm: page_ext: check if page_ext is not prepared

2017-11-07 Thread Joonsoo Kim
On Tue, Nov 07, 2017 at 10:47:30AM +0100, Michal Hocko wrote: > [CC Joonsoo] > > On Tue 07-11-17 18:41:31, Jaewon Kim wrote: > > online_page_ext and page_ext_init allocate page_ext for each section, but > > they do not allocate if the first PFN is !pfn_present(pfn) or > > !pfn_valid(pfn). Then

Re: [PATCH] mm: page_ext: check if page_ext is not prepared

2017-11-07 Thread Joonsoo Kim
On Tue, Nov 07, 2017 at 10:47:30AM +0100, Michal Hocko wrote: > [CC Joonsoo] > > On Tue 07-11-17 18:41:31, Jaewon Kim wrote: > > online_page_ext and page_ext_init allocate page_ext for each section, but > > they do not allocate if the first PFN is !pfn_present(pfn) or > > !pfn_valid(pfn). Then

Re: [PATCH] mm: page_ext: allocate page extension though first PFN is invalid

2017-11-07 Thread Joonsoo Kim
On Tue, Nov 07, 2017 at 06:44:47PM +0900, Jaewon Kim wrote: > online_page_ext and page_ext_init allocate page_ext for each section, but > they do not allocate if the first PFN is !pfn_present(pfn) or > !pfn_valid(pfn). > > Though the first page is not valid, page_ext could be useful for other >

Re: [PATCH] mm: page_ext: allocate page extension though first PFN is invalid

2017-11-07 Thread Joonsoo Kim
On Tue, Nov 07, 2017 at 06:44:47PM +0900, Jaewon Kim wrote: > online_page_ext and page_ext_init allocate page_ext for each section, but > they do not allocate if the first PFN is !pfn_present(pfn) or > !pfn_valid(pfn). > > Though the first page is not valid, page_ext could be useful for other >

Re: n900 in next-20170901

2017-11-07 Thread Joonsoo Kim
On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote: > Hi, > > * Joonsoo Kim <iamjoonsoo@lge.com> [171107 05:30]: > > Could you test follwing updated branch? > > > > https://github.com/JoonsooKim/linux/tree/cma-debug4-next-20180901 > > &

Re: n900 in next-20170901

2017-11-07 Thread Joonsoo Kim
On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote: > Hi, > > * Joonsoo Kim [171107 05:30]: > > Could you test follwing updated branch? > > > > https://github.com/JoonsooKim/linux/tree/cma-debug4-next-20180901 > > > > It has three relevant co

Re: n900 in next-20170901

2017-11-06 Thread Joonsoo Kim
Hello, Sorry for dealy. I was on vacation during last week. On Thu, Oct 26, 2017 at 07:16:27AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171025 21:45]: > > On Wed, Oct 25, 2017 at 10:31:38AM -0700, Tony Lindgren wrote: > > > Great, this bra

Re: n900 in next-20170901

2017-11-06 Thread Joonsoo Kim
Hello, Sorry for dealy. I was on vacation during last week. On Thu, Oct 26, 2017 at 07:16:27AM -0700, Tony Lindgren wrote: > * Joonsoo Kim [171025 21:45]: > > On Wed, Oct 25, 2017 at 10:31:38AM -0700, Tony Lindgren wrote: > > > Great, this branch boots on n900! Early parts of

Re: n900 in next-20170901

2017-10-25 Thread Joonsoo Kim
On Wed, Oct 25, 2017 at 10:31:38AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171022 21:51]: > > On Fri, Oct 20, 2017 at 10:31:47AM -0700, Tony Lindgren wrote: > > > * Joonsoo Kim <iamjoonsoo@lge.com> [171019 18:53]: > > > &g

Re: n900 in next-20170901

2017-10-25 Thread Joonsoo Kim
On Wed, Oct 25, 2017 at 10:31:38AM -0700, Tony Lindgren wrote: > * Joonsoo Kim [171022 21:51]: > > On Fri, Oct 20, 2017 at 10:31:47AM -0700, Tony Lindgren wrote: > > > * Joonsoo Kim [171019 18:53]: > > > > Oops... I made a mistak. Could

<    1   2   3   4   5   6   7   8   9   10   >