Re: [PATCH v5 0/5] Provide infrastructure and examples for custom kernels and modules

[Alexander Smirnov <asmirnov@ilbers.de>]

On 02/15/2018 06:13 PM, Jan Kiszka wrote:
> On 2018-02-15 16:04, Alexander Smirnov wrote:
>>
>>
>> On 02/15/2018 06:00 PM, Jan Kiszka wrote:
>>> On 2018-02-15 15:43, Alexander Smirnov wrote:
>>>> On 02/14/2018 12:13 PM, Jan Kiszka wrote:
>>>>> This is now finally the promised patches to provide simple patterns for
>>>>> building custom kernels for Isar images that replace the distro
>>>>> kernels.
>>>>> It also provids the same pattern for custom out-of-tree kernel modules.
>>>>>
>>>>> Changes in v5:
>>>>>     - dropped merged patches
>>>>>     - reworked kernel packages naming and selection mechanism to use
>>>>>       flavor/arch rather them overwriting upstream names
>>>>>     - fixed rebuilds of the kernel (.version was causing problems)
>>>>>     - moved kernel build into script - and switched back to include
>>>>> pattern
>>>>>     - provided note on origin of exemplary defconfig
>>>>>     - add KERNEL_DEFCONFIG variable
>>>>>
>>>>> Jan
>>>>
>>>> $ start_vm -a arm -d jessie
>>>>
>>>> ...
>>>>
>>>> root@isar:~# modprobe example-module
>>>> [  110.444107] Just an example
>>>> modprobe: ERROR: could not insert 'example_module': No anode
>>>>
>>>>
>>>> The same for amd64:
>>>>
>>>>
>>>> root@isar:~# modprobe example-module
>>>> [   38.343926] example_module: loading out-of-tree module taints kernel.
>>>> [   38.353140] Just an example
>>>> modprobe: ERROR: could not insert 'example_module': No anode
>>>>
>>>> Please take a look.
>>>>
>>>
>>> static int __init example_module_init(void)
>>> {
>>>           printk("Just an example\n");
>>>           return -ENOANO;
>>> }
>>>
>>> module_init(example_module_init);
>>>
>>> :)
>>>
>>
>> Ouch, didn't notice this. :-(
>>
>> Do you have any specific reason to have module_init failed? Could we
>> have zero return code to test its probe-ability and loading-by-default
>> for CI?
> 
> I didn't think of CI for this module yet, but that may make more sense
> then. Do you plan to write some CI script for that? Then just change the
> module code to your needs. It's "just an example". :)

Ok, thanks!

Now there is simple automated which checks that each virtual machine has 
reached login prompt. You could see this in the bottom of console output:

http://isar-build.org:8080/job/isar_next/105/console

To be honest, I don't want to check this manually after each merge, so 
I'm thinking about test automation for everything new appears in Isar :-)

Alex