lkml.org 
[lkml]   [2017]   [Sep]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: n900 in next-20170901
On Wed, Sep 06, 2017 at 06:30:57AM -0700, Tony Lindgren wrote:
> Hi,
>
> * Joonsoo Kim <iamjoonsoo.kim@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 can
> > be *!highmem*. Could you check that your configuration have above
> > options?
>
> CONFIG_HIGHMEM is set yeah.
>
> > And, could you check that following patch works for you?
>
> Does not seem to help, tried against next with just 9caf25f996e8
> revert and also with 9caf25f996e8.

Oops. I misunderstood your problem. Could you test with
CONFIG_DEBUG_VIRTUAL?

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
and it then causes the use of wrong physical address.
CONFIG_DEBUG_VIRTUAL would catch this case.

If it doesn't help, is there a way to test n900 configuration in QEMU?

Thanks.

\
 
 \ /
  Last update: 2017-09-07 09:30    [W:0.139 / U:3.180 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site