----- On Apr 16, 2019, at 3:17 PM, Mathieu Desnoyers mathieu.desnoyers@... wrote: The logic in my previous patch was bogus. Here is an updated version (untested): diff --git

----- On Apr 16, 2019, at 2:54 PM, Dan Williams dan.j.williams@... wrote: How large is your kernel image in memory ? Is it larger than 32MB by any chance ? On arm, the arch_static_branch()

On Thu, Apr 11, 2019 at 1:54 PM Guenter Roeck <groeck@...> wrote: [..] > > > Boot tests report > > > > > > Qemu test results: > > > total: 345 pass: 345 fail: 0 > > > > > > This is on top

Hello kernelci.org Things which didn’t exist a few years ago, such as social media promotion arenow given high importance in terms of the impact on rankings. Not building ahealthy content profile

... The issue was with an omap2 board and, AFAIK, qemu does not simulate those. -- Sincerely yours, Mike.

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

Yes, you are right. Because, with it enabled, I see: Kernel command line: rdinit=/sbin/init page_alloc.shuffle=1 panic=-1 console=ttyAMA0,115200 page_alloc.shuffle=1 ------------[ cut here

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. $ git log --oneline

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

Can someone send me a pointer to the series in question ? I would like to run it through my testbed. Thanks, Guenter

Hi! Any progress on this? Might it be possible to unblock this series for v5.2 by adding a temporary "not on ARM" flag? Thanks! -- Kees Cook

On Wed, Apr 10, 2019 at 10:47 AM Veronika Kabatova <vkabatov@...> wrote: [...] > Is there any page with details on how to join and what are the requirements > on us that I can pass along to

I'll get these added. If there's any concern about build capacity I will add GCE builders as required.

Linaro is paying for the core servers (the Hetzner boxes with the core servers are a combination of Linaro and Collabora, IIRC the boxes Collabora is paying for are all builders). As far as I'm aware

In theory that would be the Linux Foundation as part of the KernelCI project. Unfortunately, while companies and people do show interest in KernelCI, there seems to be little interest in actually

We just created the "dessert" kernels for the Android Q release, please add them to kernelci testing: repo: https://android.googlesource.com/kernel/common branches: android-4.9-q android-4.14-q

Hi, as we know from this list, there's plenty CI systems doing some testing on the upstream kernels (and maybe some others we don't know about). It would be great if there was a single common place