Re: [PATCH 0/3] ARM/ARM64: silence large module first time allocation

2017-04-25 Thread Florian Fainelli
On 04/25/2017 03:33 PM, Florian Fainelli wrote: > With kernels built with CONFIG_ARM{,64}_MODULES_PLTS=y, the first allocation > done from module space will fail, produce a general OOM allocation and also a > vmap warning. The second allocation from vmalloc space may or may not be > successful,

Re: [PATCH 0/3] ARM/ARM64: silence large module first time allocation

2017-04-25 Thread Florian Fainelli
On 04/25/2017 03:33 PM, Florian Fainelli wrote: > With kernels built with CONFIG_ARM{,64}_MODULES_PLTS=y, the first allocation > done from module space will fail, produce a general OOM allocation and also a > vmap warning. The second allocation from vmalloc space may or may not be > successful,

[PATCH 0/3] ARM/ARM64: silence large module first time allocation

2017-04-25 Thread Florian Fainelli
With kernels built with CONFIG_ARM{,64}_MODULES_PLTS=y, the first allocation done from module space will fail, produce a general OOM allocation and also a vmap warning. The second allocation from vmalloc space may or may not be successful, but is actually the one we are interested about in these

[PATCH 0/3] ARM/ARM64: silence large module first time allocation

2017-04-25 Thread Florian Fainelli
With kernels built with CONFIG_ARM{,64}_MODULES_PLTS=y, the first allocation done from module space will fail, produce a general OOM allocation and also a vmap warning. The second allocation from vmalloc space may or may not be successful, but is actually the one we are interested about in these