All kernel modules being built and shipped in images/modules-*.tgz

All kernel modules being built and shipped in images/modules-*.tgz

[Elvis Dowson]

Hi,
     I just noticed that with the recent poky master updates, my images/modules-3.3.1-r00-virtex5.tgz file has grown from 33.1 MB to 668.5MB. When I looked in the package, I saw that the kernel/drivers folder inside that package was nearly 1.5GB uncompressed!!

My kenel defconfig was tuned so that I only used a bare minimum of kernel modules, and nearly all except for 2 groups (one related to filesystem and the other for networking) was built as a module. The rest were all built into the kernel.

Isn't this a regression or an error? 

Also my build time has gone up from 40 minutes to 67 minutes, probably as a result of the increased number of kernel modules being built and shipped.

Best regards,

Elvis Dowson

Re: All kernel modules being built and shipped in images/modules-*.tgz

[Elvis Dowson]

Hi,

On Sep 15, 2012, at 7:29 AM, Elvis Dowson wrote:

> I just noticed that with the recent poky master updates, my images/modules-3.3.1-r00-virtex5.tgz file has grown from 33.1 MB to 668.5MB. When I looked in the package, I saw that the kernel/drivers folder inside that package was nearly 1.5GB uncompressed!!
> 
> My kenel defconfig was tuned so that I only used a bare minimum of kernel modules, and nearly all except for 2 groups (one related to filesystem and the other for networking) was built as a module. The rest were all built into the kernel.
> 
> Isn't this a regression or an error? 
> 
> Also my build time has gone up from 40 minutes to 67 minutes, probably as a result of the increased number of kernel modules being built and shipped.

Is there any way to prevent all the kernel modules from being built, when 99% of my kernel defconfig settings are set to 'y' and not to build any modules?

Elvis

Re: All kernel modules being built and shipped in images/modules-*.tgz

[Bruce Ashfield]

On 12-09-16 12:49 PM, Elvis Dowson wrote:
> Hi,
>
> On Sep 15, 2012, at 7:29 AM, Elvis Dowson wrote:
>
>> I just noticed that with the recent poky master updates, my images/modules-3.3.1-r00-virtex5.tgz file has grown from 33.1 MB to 668.5MB. When I looked in the package, I saw that the kernel/drivers folder inside that package was nearly 1.5GB uncompressed!!
>>
>> My kenel defconfig was tuned so that I only used a bare minimum of kernel modules, and nearly all except for 2 groups (one related to filesystem and the other for networking) was built as a module. The rest were all built into the kernel.
>>
>> Isn't this a regression or an error?
>>
>> Also my build time has gone up from 40 minutes to 67 minutes, probably as a result of the increased number of kernel modules being built and shipped.
>
> Is there any way to prevent all the kernel modules from being built, when 99% of my kernel defconfig settings are set to 'y' and not to build any modules?

You'll have to confirm in your kernel build directory and .config
that you really don't have these modules enabled.

Since there's no kernel recipe that I've seen that builds all modules,
they just the modules specified in your .config are built and packaged
by the kernel classes.

But maybe I've misunderstood the question, or what you are seeing.

Bruce



>
> Elvis
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: All kernel modules being built and shipped in images/modules-*.tgz

[Elvis Dowson]

Hi Bruce,

On Sep 17, 2012, at 7:18 AM, Bruce Ashfield wrote:

> On 12-09-16 12:49 PM, Elvis Dowson wrote:
>> Hi,
>> 
>> On Sep 15, 2012, at 7:29 AM, Elvis Dowson wrote:
>> 
>>> I just noticed that with the recent poky master updates, my images/modules-3.3.1-r00-virtex5.tgz file has grown from 4.6 MB to 668.5MB. When I looked in the package, I saw that the kernel/drivers folder inside that package was nearly 1.5GB uncompressed!!
>>> 
>>> My kenel defconfig was tuned so that I only used a bare minimum of kernel modules, and nearly all except for 2 groups (one related to filesystem and the other for networking) was built as a module. The rest were all built into the kernel.
>>> 
>>> Isn't this a regression or an error?
>>> 
>>> Also my build time has gone up from 40 minutes to 67 minutes, probably as a result of the increased number of kernel modules being built and shipped.
>> 
>> Is there any way to prevent all the kernel modules from being built, when 99% of my kernel defconfig settings are set to 'y' and not to build any modules?
> 
> You'll have to confirm in your kernel build directory and .config
> that you really don't have these modules enabled.
> 
> Since there's no kernel recipe that I've seen that builds all modules,
> they just the modules specified in your .config are built and packaged
> by the kernel classes.
> 
> But maybe I've misunderstood the question, or what you are seeing.

The problem that I'm seeing is that before, with the same defconfig file
the size of the kernel module image was only 4.6MB. Now with the latest
poky master, the same recipe generates a kernel module image that is 
668.5MB in size!! :-)

I looked at the .config file in the tmp/work/virtex5-poky-linux/linux-xilinx-3.3.0-r00/git folder
and find that a whole bunch of modules that were not enabled at all in my 
defconfig-3.0.0 file (that's the name given in the linux-xilinx_3.3.0.bb recipe), got enabled.

The original size of the defconfig-3.3.0 file was 43.4kb. the one in the 
tmp/work/virtex5-poky-linux/linux-xilinx-3.3.0-r00/git was over 124kb!

This is with poky master commit id 913944d904266bf90af0cad94b4f0fb3652bd29d.

This problem did not occur with poky master commit id 2dec760b79bb7e2e79c33c5127fa64685bd86a18

Best regards,

Elvis Dowson