Re: Re: [PATCH 1/1] arm/module: maximum utilization of module area.

2016-12-12 Thread Ard Biesheuvel
On 12 December 2016 at 15:28, Nicolas Pitre wrote: > On Mon, 12 Dec 2016, Vaneet Narang wrote: > >> Hi, >> >> >A PC24 relocation has a range of +/-32MB. This means that where-ever >> >the module is placed, it must be capable of reaching any function >> >within the kernel text, which may itself be

RE: Re: [PATCH 1/1] arm/module: maximum utilization of module area.

2016-12-12 Thread Nicolas Pitre
On Mon, 12 Dec 2016, Vaneet Narang wrote: > Hi, > > >A PC24 relocation has a range of +/-32MB. This means that where-ever > >the module is placed, it must be capable of reaching any function > >within the kernel text, which may itself be quite large (eg, 8MB, or > >possibly larger). The module

Re: Re: [PATCH 1/1] arm/module: maximum utilization of module area.

2016-12-12 Thread Russell King - ARM Linux
On Mon, Dec 12, 2016 at 11:22:30AM +, Vaneet Narang wrote: > Hi, > > >A PC24 relocation has a range of +/-32MB. This means that where-ever > >the module is placed, it must be capable of reaching any function > >within the kernel text, which may itself be quite large (eg, 8MB, or > >possibly l

RE: Re: [PATCH 1/1] arm/module: maximum utilization of module area.

2016-12-12 Thread Vaneet Narang
Hi, >A PC24 relocation has a range of +/-32MB. This means that where-ever >the module is placed, it must be capable of reaching any function >within the kernel text, which may itself be quite large (eg, 8MB, or >possibly larger). The module area exists to allow modules to be >located in an area

Re: [PATCH 1/1] arm/module: maximum utilization of module area.

2016-12-12 Thread Russell King - ARM Linux
On Tue, Dec 06, 2016 at 01:59:35PM +0530, Maninder Singh wrote: > This patch defines new macro MODULE_START to ensure kernel text > and module remains within 32 MB of address range. > > Tried this patch by inserting 20 MB size module on 4.1 kernel:- > > Earlier:- > == > sh# insmod size.ko

Re: [PATCH 1/1] arm/module: maximum utilization of module area.

2016-12-12 Thread Vaneet Narang
Hi Ard, >> +#ifndef CONFIG_THUMB2_KERNEL >> +#define MODULES_START ALIGN((unsigned long)_etext - SZ_32M, PAGE_SIZE) > >On a multi_v7_defconfig kernel, the text size is >8 MB, which means >you are only adding ~7 MB to the module area, while consuming 16 MB of >additional address space. I am not s

Re: [PATCH 1/1] arm/module: maximum utilization of module area.

2016-12-06 Thread Nicolas Pitre
On Tue, 6 Dec 2016, Maninder Singh wrote: > This patch defines new macro MODULE_START to ensure kernel text > and module remains within 32 MB of address range. > > Tried this patch by inserting 20 MB size module on 4.1 kernel:- > > Earlier:- > == > sh# insmod size.ko > > insmod: ERR

Re: [PATCH 1/1] arm/module: maximum utilization of module area.

2016-12-06 Thread Ard Biesheuvel
On 6 December 2016 at 08:29, Maninder Singh wrote: > This patch defines new macro MODULE_START to ensure kernel text > and module remains within 32 MB of address range. > > Tried this patch by inserting 20 MB size module on 4.1 kernel:- > > Earlier:- > == > sh# insmod size.ko > > insm

[PATCH 1/1] arm/module: maximum utilization of module area.

2016-12-06 Thread Maninder Singh
This patch defines new macro MODULE_START to ensure kernel text and module remains within 32 MB of address range. Tried this patch by inserting 20 MB size module on 4.1 kernel:- Earlier:- == sh# insmod size.ko insmod: ERROR: could not insert module size.ko: Cannot allocate memory sh#