With the #850 it is changed to two large text blobs: one config is for x86_64, another one is for aarch64.
While it works and provides us working kernel, it is hard to manage:
not clear which settings are customized comparing to the default kernel config for x86_64
not clear which of those custom settings should be also ported to the arm config during #850
(hypothesis): it is probably would be hard to update kernel to newer versions by the very same reasons as mentioned.
It would be great to store in the repo instead of the full config only the difference from the default one and use linux/scripts/kconfig/merge_config.sh from the kernel source tree.
Currently, difference with default x86_64 config (provided by make ARCH=x86_64 defconfig) is ~4k lines:
DoD: we have reliable way to manage kernel configuration for different architectures.
Implementation ideas
We should utilize them scripts and makefile targets in the linux kernel source tree, there are plenty of them to work with configuration management.
Option 1.
Store config only with those variables and values that are important for us, during build use make oldconfig or kconfig/merge_config.sh to merge our changes with default config.
Problem description / Motivation
Currently we store custom kernel config as one large text blob in the github https://github.com/neondatabase/autoscaling/blob/main/neonvm/hack/kernel/linux-config-6.1.92
With the #850 it is changed to two large text blobs: one config is for x86_64, another one is for aarch64.
While it works and provides us working kernel, it is hard to manage:
It would be great to store in the repo instead of the full config only the difference from the default one and use
linux/scripts/kconfig/merge_config.shfrom the kernel source tree.Currently, difference with default x86_64 config (provided by
make ARCH=x86_64 defconfig) is ~4k lines:Feature idea(s) / DoD
DoD: we have reliable way to manage kernel configuration for different architectures.
Implementation ideas
We should utilize them scripts and makefile targets in the linux kernel source tree, there are plenty of them to work with configuration management.
Option 1.
Store config only with those variables and values that are important for us, during build use
make oldconfigorkconfig/merge_config.shto merge our changes with default config.