On Thu, Apr 11, 2019 at 1:08 PM Guenter Roeck <[email protected]> wrote: > > On Thu, Apr 11, 2019 at 10:35 AM Kees Cook <[email protected]> wrote: > > > > On Thu, Apr 11, 2019 at 9:42 AM Guenter Roeck <[email protected]> wrote: > > > > > > On Thu, Apr 11, 2019 at 9:19 AM Kees Cook <[email protected]> wrote: > > > > > > > > On Thu, Mar 7, 2019 at 7:43 AM Dan Williams <[email protected]> > > > > wrote: > > > > > I went ahead and acquired one of these boards to see if I can can > > > > > debug this locally. > > > > > > > > Hi! Any progress on this? Might it be possible to unblock this series > > > > for v5.2 by adding a temporary "not on ARM" flag? > > > > > > > > > > Can someone send me a pointer to the series in question ? I would like > > > to run it through my testbed. > > > > It's already in -mm and linux-next (",mm: shuffle initial free memory > > to improve memory-side-cache utilization") but it gets enabled with > > CONFIG_SHUFFLE_PAGE_ALLOCATOR=y (which was made the default briefly in > > -mm which triggered problems on ARM as was reverted). > > > > Boot tests report > > Qemu test results: > total: 345 pass: 345 fail: 0 > > This is on top of next-20190410 with CONFIG_SHUFFLE_PAGE_ALLOCATOR=y > and the known crashes fixed.
In addition to CONFIG_SHUFFLE_PAGE_ALLOCATOR=y you also need the kernel command line option "page_alloc.shuffle=1" ...so I doubt you are running with shuffling enabled. Another way to double check is: cat /sys/module/page_alloc/parameters/shuffle
