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.
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:
> > > &
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!
>
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
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
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
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
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
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
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
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
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
> &
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
>
>
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
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).
>>
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)
>
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
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
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
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
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,
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,
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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:
> > >
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
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
>
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
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
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
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:
> >> >
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")
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")
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
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
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
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-
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
>
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
>
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
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
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.
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.
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
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
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
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
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
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
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.
2 ("mm/cma: always check which page caused allocation
> failure")
> Cc:
> Signed-off-by: Mike Kravetz
Good catch!!
Acked-by: Joonsoo Kim
Thanks.
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
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
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]:
> > > >
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
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]:
> > > >
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
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:
> > > >
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
>
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
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
> &
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
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
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?
> >
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
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
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.
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:
>
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:
>
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
&
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
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:
> >
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
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]:
> > > >
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
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
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?
> >
> &
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
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
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
>
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
>
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
> >
&
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
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
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
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
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
101 - 200 of 4538 matches
Mail list logo