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: [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-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 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-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/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 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: [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: [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: + 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: [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] 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: [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: [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: [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: 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 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] 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 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 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: 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 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-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 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-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 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: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: [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: 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 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 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: [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: 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-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-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: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

2017-10-25 Thread Joonsoo Kim
On Tue, Oct 24, 2017 at 10:12:58AM +0200, Vlastimil Babka wrote: > On 10/24/2017 06:44 AM, Joonsoo Kim wrote: > >>> I'm not sure what is the confusing semantic you mentioned. I think > >>> that set_migratetype_isolate() has confusing semantic and should be > >&g

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

2017-10-23 Thread Joonsoo Kim
On Mon, Oct 23, 2017 at 10:10:09AM +0200, Michal Hocko wrote: > On Mon 23-10-17 14:23:09, Joonsoo Kim wrote: > > On Fri, Oct 20, 2017 at 09:02:20AM +0200, Michal Hocko wrote: > > > On Fri 20-10-17 15:50:14, Joonsoo Kim wrote: > > > > On Fri, Oct 20, 2017 at 07:59:

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

2017-10-22 Thread Joonsoo Kim
On Fri, Oct 20, 2017 at 10:17:00AM +0200, Michal Hocko wrote: > On Fri 20-10-17 15:22:14, Xishi Qiu wrote: > > On 2017/10/20 10:13, Joonsoo Kim wrote: > > > > > On Thu, Oct 19, 2017 at 02:21:18PM +0200, Michal Hocko wrote: > [...] > > >> >From 8cbd811d7

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

2017-10-22 Thread Joonsoo Kim
On Fri, Oct 20, 2017 at 09:02:20AM +0200, Michal Hocko wrote: > On Fri 20-10-17 15:50:14, Joonsoo Kim wrote: > > On Fri, Oct 20, 2017 at 07:59:22AM +0200, Michal Hocko wrote: > > > On Fri 20-10-17 11:13:29, Joonsoo Kim wrote: > > > > On Thu, Oct 19, 2017 at 02:21:

Re: n900 in next-20170901

2017-10-22 Thread Joonsoo Kim
On Fri, Oct 20, 2017 at 10:31:47AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171019 18:53]: > > Oops... I made a mistak. Could you test with reverting commit > > c977ee2803787363187d6aca9cebdabc793c6531 ("omap: forcibly call > > sa

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

2017-10-20 Thread Joonsoo Kim
On Fri, Oct 20, 2017 at 07:59:22AM +0200, Michal Hocko wrote: > On Fri 20-10-17 11:13:29, Joonsoo Kim wrote: > > On Thu, Oct 19, 2017 at 02:21:18PM +0200, Michal Hocko wrote: > > > On Thu 19-10-17 10:20:41, Michal Hocko wrote: > > > > On Thu 19-10-17 16:33:56, Joons

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

2017-10-19 Thread Joonsoo Kim
On Thu, Oct 19, 2017 at 02:21:18PM +0200, Michal Hocko wrote: > On Thu 19-10-17 10:20:41, Michal Hocko wrote: > > On Thu 19-10-17 16:33:56, Joonsoo Kim wrote: > > > On Thu, Oct 19, 2017 at 09:15:03AM +0200, Michal Hocko wrote: > > > > On Thu 19-10-

Re: n900 in next-20170901

2017-10-19 Thread Joonsoo Kim
On Thu, Oct 19, 2017 at 11:30:34AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171018 01:27]: > > On Mon, Sep 25, 2017 at 07:54:37AM -0700, Tony Lindgren wrote: > > > * Joonsoo Kim <iamjoonsoo@lge.com> [170925 01:06]: > > > >

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

2017-10-19 Thread Joonsoo Kim
On Thu, Oct 19, 2017 at 09:15:03AM +0200, Michal Hocko wrote: > On Thu 19-10-17 11:51:11, Joonsoo Kim wrote: > > On Fri, Oct 13, 2017 at 02:00:12PM +0200, Michal Hocko wrote: > > > From: Michal Hocko <mho...@suse.com> > > > > > > Michael has noticed that

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

2017-10-18 Thread Joonsoo Kim
On Fri, Oct 13, 2017 at 02:00:12PM +0200, Michal Hocko wrote: > From: Michal Hocko > > Michael has noticed that the memory offline tries to migrate kernel code > pages when doing > echo 0 > /sys/devices/system/memory/memory0/online > > The current implementation will fail the

Re: [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel

2017-10-18 Thread Joonsoo Kim
On Wed, Oct 18, 2017 at 03:15:03PM +0200, Thomas Gleixner wrote: > On Wed, 18 Oct 2017, Linus Torvalds wrote: > > On Tue, Oct 17, 2017 at 3:33 AM, Joonsoo Kim <iamjoonsoo@lge.com> wrote: > > > > > > It looks like a compiler bug. The code of slob_un

Re: n900 in next-20170901

2017-10-18 Thread Joonsoo Kim
On Mon, Sep 25, 2017 at 07:54:37AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [170925 01:06]: > > On Thu, Sep 21, 2017 at 10:28:11AM -0700, Tony Lindgren wrote: > > > * Joonsoo Kim <iamjoonsoo@lge.com> [170914 23:55]: > > > >

Re: [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel

2017-10-18 Thread Joonsoo Kim
On Tue, Oct 17, 2017 at 09:50:04AM +0200, Thomas Gleixner wrote: > On Tue, 17 Oct 2017, Joonsoo Kim wrote: > > On Wed, Oct 11, 2017 at 12:01:20PM -0500, Josh Poimboeuf wrote: > > > > Looking at the panic, the code in slob_free() was: > > > > > > &g

Re: [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel

2017-10-17 Thread Joonsoo Kim
On Wed, Oct 11, 2017 at 12:01:20PM -0500, Josh Poimboeuf wrote: > I failed to add the slab maintainers to CC on the last attempt. Trying > again. > > On Tue, Oct 10, 2017 at 09:31:06PM -0500, Josh Poimboeuf wrote: > > On Tue, Oct 10, 2017 at 08:15:13PM +0800, kernel test robot wrote: > > > > >

Re: n900 in next-20170901

2017-09-25 Thread Joonsoo Kim
On Thu, Sep 21, 2017 at 10:28:11AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [170914 23:55]: > > On Wed, Sep 13, 2017 at 09:31:27AM -0700, Tony Lindgren wrote: > > > Yes I disabled CONFIG_HIGHMEM and n900 boots. To disable it, > > > yo

Re: n900 in next-20170901

2017-09-17 Thread Joonsoo Kim
Hello, On Fri, Sep 15, 2017 at 03:28:44PM +0200, Pali Rohár wrote: > On Thursday 07 September 2017 16:30:38 Joonsoo Kim wrote: > > If it doesn't help, is there a way to test n900 configuration in QEMU? > > Hi Joonsoo, linaro version of QEMU has support for n900 machine. For >

Re: n900 in next-20170901

2017-09-17 Thread Joonsoo Kim
On Fri, Sep 15, 2017 at 03:18:18PM +0200, Pavel Machek wrote: > Hi! > > > > After commit 9caf25f996e8, user for CMA memory should use to check > > > PageHighmem in order to get proper virtual address of the page. If > > > someone doesn't use it, it is possible to use wrong virtual address > > >

Re: n900 in next-20170901

2017-09-15 Thread Joonsoo Kim
On Wed, Sep 13, 2017 at 09:31:27AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [170913 00:54]: > > On Thu, Sep 07, 2017 at 09:16:51AM -0700, Tony Lindgren wrote: > > > I doubt that QEMU n900 boots in secure mode but instead shows > > > the

Re: n900 in next-20170901

2017-09-13 Thread Joonsoo Kim
On Thu, Sep 07, 2017 at 09:16:51AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [170907 00:30]: > > On Wed, Sep 06, 2017 at 06:30:57AM -0700, Tony Lindgren wrote: > > > Hi, > > > > > > * Joonsoo Kim <iamjoonsoo@lge.com

Re: n900 in next-20170901

2017-09-07 Thread Joonsoo Kim
On Wed, Sep 06, 2017 at 06:30:57AM -0700, Tony Lindgren wrote: > Hi, > > * Joonsoo Kim <iamjoonsoo@lge.com> [170905 16:32]: > > I think that I made a mistake for configuration CONFIG_HIGHMEM=y and > > CONFIG_HAVE_MEMBLOCK_NODE_MAP=y. In this case, the MOVABLE_ZONE c

Re: n900 in next-20170901

2017-09-05 Thread Joonsoo Kim
On Tue, Sep 05, 2017 at 01:13:15PM -0700, Tony Lindgren wrote: > * Pavel Machek [170903 13:38]: > > Hi! > > > > It compiles ok, but it hangs on boot; black screen, so sometime before > > display is initialized. > > Thanks for reporting it. Based on git bisect, the regression

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

2017-08-30 Thread Joonsoo Kim
On Tue, Aug 29, 2017 at 03:39:45PM +0200, Michal Hocko wrote: > On Tue 29-08-17 09:45:47, Joonsoo Kim wrote: > > On Mon, Aug 28, 2017 at 11:56:16AM +0200, Michal Hocko wrote: > > > On Mon 28-08-17 09:15:52, Joonsoo Kim wrote: > > > > On Fri, Aug 25, 2017 at 09:38:

Re: [PATCH 2/2] mm/slub: don't use reserved highatomic pageblock for optimistic try

2017-08-30 Thread Joonsoo Kim
On Tue, Aug 29, 2017 at 09:33:44AM +0900, Joonsoo Kim wrote: > On Mon, Aug 28, 2017 at 03:08:29PM +0200, Michal Hocko wrote: > > On Mon 28-08-17 13:29:29, Vlastimil Babka wrote: > > > On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > > > > From: Joons

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

2017-08-30 Thread Joonsoo Kim
On Tue, Aug 29, 2017 at 11:16:18AM +0200, Vlastimil Babka wrote: > On 08/24/2017 08:36 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > 0. History > > > > This patchset is the follow-up of the discussion about the &g

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

2017-08-28 Thread Joonsoo Kim
On Mon, Aug 28, 2017 at 11:56:16AM +0200, Michal Hocko wrote: > On Mon 28-08-17 09:15:52, Joonsoo Kim wrote: > > On Fri, Aug 25, 2017 at 09:38:42AM +0200, Michal Hocko wrote: > > > On Fri 25-08-17 09:20:31, Joonsoo Kim wrote: > > > > On Thu, Aug 24, 2017 at 11:41:58A

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

2017-08-28 Thread Joonsoo Kim
On Mon, Aug 28, 2017 at 08:45:07AM +0200, Vlastimil Babka wrote: > +CC linux-api > > On 08/28/2017 02:28 AM, Joonsoo Kim wrote: > > On Fri, Aug 25, 2017 at 09:56:10AM +0200, Vlastimil Babka wrote: > >> On 08/25/2017 02:20 AM, Joonsoo Kim wrote: > >>> On T

Re: [PATCH 2/2] mm/slub: don't use reserved highatomic pageblock for optimistic try

2017-08-28 Thread Joonsoo Kim
On Mon, Aug 28, 2017 at 03:08:29PM +0200, Michal Hocko wrote: > On Mon 28-08-17 13:29:29, Vlastimil Babka wrote: > > On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > > > High-order atomic allocati

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

2017-08-28 Thread Joonsoo Kim
On Mon, Aug 28, 2017 at 12:04:41PM +0200, Vlastimil Babka wrote: > On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > slub uses higher order allocation than it actually needs. In this case, > > we don't

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

2017-08-27 Thread Joonsoo Kim
On Fri, Aug 25, 2017 at 09:56:10AM +0200, Vlastimil Babka wrote: > On 08/25/2017 02:20 AM, Joonsoo Kim wrote: > > On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote: > > > > Hmm, this is already pointed by Minchan and I have answered that. > > > >

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

2017-08-27 Thread Joonsoo Kim
On Fri, Aug 25, 2017 at 02:32:13PM -0700, Andrew Morton wrote: > On Thu, 24 Aug 2017 15:36:30 +0900 js1...@gmail.com wrote: > > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > This patchset is the follow-up of the discussion about the > > "Intro

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

2017-08-27 Thread Joonsoo Kim
On Fri, Aug 25, 2017 at 09:38:42AM +0200, Michal Hocko wrote: > On Fri 25-08-17 09:20:31, Joonsoo Kim wrote: > > On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote: > > > On 08/24/2017 07:45 AM, js1...@gmail.com wrote: > > > > From: Joons

Re: [PATCH] zram: add zstd to the supported algorithms list

2017-08-24 Thread Joonsoo Kim
On Fri, Aug 25, 2017 at 01:35:35AM +, Nick Terrell wrote: > On 8/24/17, 5:49 PM, "Joonsoo Kim" <iamjoonsoo@lge.com> wrote: > > On Thu, Aug 24, 2017 at 09:33:54PM +, Nick Terrell wrote: > > > On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey S

Re: [PATCH] zram: add zstd to the supported algorithms list

2017-08-24 Thread Joonsoo Kim
On Thu, Aug 24, 2017 at 09:33:54PM +, Nick Terrell wrote: > On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey Senozhatsky wrote: > > Add ZSTD to the list of supported compression algorithms. > > > > Official benchmarks [1]: > > Awesome! Let me know if you need anything from me. > Hello,

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

2017-08-24 Thread Joonsoo Kim
On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote: > On 08/24/2017 07:45 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > Freepage on ZONE_HIGHMEM doesn't work for kernel memory so it's not that > > important to r

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

2017-08-24 Thread Joonsoo Kim
On Thu, Aug 24, 2017 at 11:30:50AM +0200, Michal Hocko wrote: > On Thu 24-08-17 14:45:46, Joonsoo Kim wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > Freepage on ZONE_HIGHMEM doesn't work for kernel memory so it's not that > > important to r

Re: [PATCH] mm/mlock: use page_zone() instead of page_zone_id()

2017-08-24 Thread Joonsoo Kim
On Thu, Aug 24, 2017 at 01:05:15PM +0200, Vlastimil Babka wrote: > +CC Mel > > On 08/24/2017 09:20 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > page_zone_id() is a specialized function to compare the zone for the pages >

Re: "mm: use early_pfn_to_nid in page_ext_init" broken on some configurations?

2017-07-03 Thread Joonsoo Kim
On Mon, Jul 03, 2017 at 04:18:01PM +0200, Vlastimil Babka wrote: > On 07/03/2017 01:48 PM, Vlastimil Babka wrote: > > On 06/30/2017 04:18 PM, Michal Hocko wrote: > >> fe53ca54270a ("mm: use early_pfn_to_nid in page_ext_init") seem > >> to silently depend on CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID resp.

Re: "mm: use early_pfn_to_nid in page_ext_init" broken on some configurations?

2017-07-03 Thread Joonsoo Kim
On Mon, Jul 03, 2017 at 01:48:05PM +0200, Vlastimil Babka wrote: > On 06/30/2017 04:18 PM, Michal Hocko wrote: > > fe53ca54270a ("mm: use early_pfn_to_nid in page_ext_init") seem > > to silently depend on CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID resp. > > CONFIG_HAVE_MEMBLOCK_NODE_MAP. early_pfn_to_nid

Re: "mm: use early_pfn_to_nid in page_ext_init" broken on some configurations?

2017-07-03 Thread Joonsoo Kim
On Fri, Jun 30, 2017 at 05:44:16PM +0200, Michal Hocko wrote: > On Fri 30-06-17 17:42:24, Michal Hocko wrote: > [...] > > diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h > > index 16532fa0bb64..894697c1e6f5 100644 > > --- a/include/linux/mmzone.h > > +++ b/include/linux/mmzone.h > >

Re: [PATCH 2/2] mm, memory_hotplug: remove zone restrictions

2017-06-29 Thread Joonsoo Kim
llows only offline > nodes already. The original default_zone_for_pfn will become > default_kernel_zone_for_pfn. New default_zone_for_pfn implements the > above semantic. zone_for_pfn_range is slightly reorganized to implement > kernel and movable online type explicitly and MMOP_ONLINE_KEEP becomes > a catch all default behavior. > > Signed-off-by: Michal Hocko <mho...@suse.com> I appreaciate your help! Acked-by: Joonsoo Kim <iamjoonsoo@lge.com> Thanks.

Re: [PATCH 1/2] mm, memory_hotplug: display allowed zones in the preferred ordering

2017-06-29 Thread Joonsoo Kim
ault online zone is not > duplicated. > > Signed-off-by: Michal Hocko <mho...@suse.com> > Acked-by: Joonsoo Kim <iamjoonsoo@lge.com> Thanks.

Re: [RFC][PATCH] slub: Introduce 'alternate' per cpu partial lists

2017-06-13 Thread Joonsoo Kim
d-off-by: Laura Abbott <labb...@redhat.com> > --- > This is a follow up to my previous proposal to speed up slub_debug=P > https://marc.info/?l=linux-mm=145920558822958=2 . The current approach > is hopelessly slow and can't really be used outside of limited debugging. > The goal is to

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-06-13 Thread Joonsoo Kim
On Tue, Jun 13, 2017 at 07:49:47PM +0300, Andrey Ryabinin wrote: > On 06/08/2017 05:40 AM, Joonsoo Kim wrote: > >>> > >>> I don't understand why we trying to invent some hacky/complex schemes > >>> when we already have > >>> a simple one - scalin

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-06-07 Thread Joonsoo Kim
On Wed, May 31, 2017 at 07:31:53PM +0300, Andrey Ryabinin wrote: > On 05/31/2017 08:50 AM, Joonsoo Kim wrote: > >>> But the main win as I see it is that that's basically complete support > >>> for 32-bit arches. People do ask about arm32 support: > >>> ht

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-06-07 Thread Joonsoo Kim
On Thu, Jun 01, 2017 at 08:06:02PM +0200, Dmitry Vyukov wrote: > On Tue, May 30, 2017 at 4:16 PM, Andrey Ryabinin > wrote: > > On 05/29/2017 06:29 PM, Dmitry Vyukov wrote: > >> Joonsoo, > >> > >> I guess mine (and Andrey's) main concern is the amount of additional > >>

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-05-30 Thread Joonsoo Kim
On Tue, May 30, 2017 at 05:16:56PM +0300, Andrey Ryabinin wrote: > On 05/29/2017 06:29 PM, Dmitry Vyukov wrote: > > Joonsoo, > > > > I guess mine (and Andrey's) main concern is the amount of additional > > complexity (I am still struggling to understand how it all works) and > > more

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-05-24 Thread Joonsoo Kim
On Wed, May 24, 2017 at 06:31:04PM +0200, Dmitry Vyukov wrote: > On Wed, May 24, 2017 at 8:04 AM, Joonsoo Kim <js1...@gmail.com> wrote: > >> >> > From: Joonsoo Kim <iamjoonsoo@lge.com> > >> >> > > >> >> > Hello, all. > &g

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-05-24 Thread Joonsoo Kim
On Wed, May 24, 2017 at 07:19:50PM +0200, Dmitry Vyukov wrote: > On Wed, May 24, 2017 at 9:45 AM, Joonsoo Kim <js1...@gmail.com> wrote: > >> > What does make your current patch work then? > >> > Say we map a new shadow page, update the page shadow to say t

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-05-24 Thread Joonsoo Kim
On Wed, May 24, 2017 at 08:57:23AM +0200, Dmitry Vyukov wrote: > On Tue, May 16, 2017 at 10:49 PM, Dmitry Vyukov <dvyu...@google.com> wrote: > > On Mon, May 15, 2017 at 11:23 PM, Joonsoo Kim <js1...@gmail.com> wrote: > >>> > > >>> > Hello, all.

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-05-24 Thread Joonsoo Kim
On Mon, May 22, 2017 at 05:00:29PM +0300, Andrey Ryabinin wrote: > > > On 05/19/2017 04:53 AM, Joonsoo Kim wrote: > > On Wed, May 17, 2017 at 03:17:13PM +0300, Andrey Ryabinin wrote: > >> On 05/16/2017 04:16 AM, js1...@gmail.com wrote: > >>> From:

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-05-24 Thread Joonsoo Kim
On Mon, May 22, 2017 at 08:02:36AM +0200, Dmitry Vyukov wrote: > On Fri, May 19, 2017 at 3:53 AM, Joonsoo Kim <js1...@gmail.com> wrote: > > On Wed, May 17, 2017 at 03:17:13PM +0300, Andrey Ryabinin wrote: > >> On 05/16/2017 04:16 AM, js1...@gmail.com wrote: > >>

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-05-18 Thread Joonsoo Kim
On Wed, May 17, 2017 at 03:17:13PM +0300, Andrey Ryabinin wrote: > On 05/16/2017 04:16 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > Hello, all. > > > > This is an attempt to recude memory consumption of KASAN. Plea

Re: [PATCH v7 0/7] Introduce ZONE_CMA

2017-05-17 Thread Joonsoo Kim
> > > > Okay. We did a lot of discussion so it's better to summarise it. > > > > 1. ZONE_CMA might be a nicer solution than MIGRATETYPE. > > 2. Additional bit in page flags would cause another kind of > > maintenance problem so it's better to avoid it as much as possible. > > 3. Abusing

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-05-17 Thread Joonsoo Kim
On Wed, May 17, 2017 at 04:23:17PM +0900, Joonsoo Kim wrote: > > However, I see some very significant slowdowns with inline > > instrumentation. I did 3 tests: > > 1. Boot speed, I measured time for a particular message to appear on > > console. Before: > > [2.

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-05-17 Thread Joonsoo Kim
On Tue, May 16, 2017 at 01:49:10PM -0700, Dmitry Vyukov wrote: > > Anyway, I have missed inline instrumentation completely. > > > > I will attach the fix in the bottom. It doesn't look beautiful > > since it breaks layer design (some check will be done at report > > function). However, I think

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

2017-05-16 Thread Joonsoo Kim
On Mon, May 15, 2017 at 09:34:17PM -0700, Dmitry Vyukov wrote: > On Mon, May 15, 2017 at 6:16 PM, <js1...@gmail.com> wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > Hello, all. > > > > This is an attempt to recude memory consumption o

  1   2   3   4   5   6   7   8   9   10   >