So just to verify, does this link have everything I need to set this variable?
Well it doesn’t spell out this exact scenario. But the general steps are there on how to create a patch or config file for out kernel and build it in Yocto. For a more “real” example you can see the recipe for our kernel recipe here: https://git.toradex.com/cgit/meta-toradex-nxp.git/tree/recipes-kernel/linux/linux-toradex_5.15-2.1.x.bb?h=kirkstone-6.x.y
In this recipe we add some PREEMPT RT related kernel configurations via the *.scc files defined in SRC_URI*. Basically you just need to provide a kernel fragment to the relevant kernel recipe’s SRC_URI to apply those kernel config options at build time.
Basically just create a *.cfg file like this: https://git.toradex.com/cgit/meta-toradex-nxp.git/tree/recipes-kernel/linux/linux-toradex-5.15-2.1.x/preempt-rt.cfg?h=kirkstone-6.x.y
Except with the kernel configs you want. Then add the name of this file to the SRC_URI of the relevant linux-toradex* recipe in Yocto. Then just build the image and it should apply your kernel config options listed in the fragment file.
We’re trying to track down some memory leaks in the kernel
Now with that said, what kind of memory leaks are you observing. Is it something on our side or something on your side?
Best Regards,
Jeremias