Can we build-in lkrg module inside kernel for better lto performance and community grow?

[osevan]

Can we buildin lkrg inside kernel?

Any patches existing?

Its ok when we have config_lkrg=m as module

Thanks and

Best regards

[solardiz]

@sempervictus @0xC0ncord Maybe you'd help answer this one? I never really used our copy-builtin script myself.

[0xC0ncord]

As for usage, scripts/copy-builtin.sh needs at least KDIR= to be set, which will default to /usr/src/linux. Easiest way to do it:

# KDIR=/usr/src/linux-6.15.11 lkrg-main/scripts/copy-builtin.sh

After that, you can configure the kernel like normal, but now you'll have the ability to set CONFIG_SECURITY_LKRG in Security options.

You still need to have the same options configured in the kernel as though LKRG was out-of-tree, e.g. KPROBES and KALLSYMS.

[solardiz]

Thanks @0xC0ncord. I'm not sure, but maybe @osevan's question was on =m vs. =y - can you comment on that?

[solardiz]

@osevan Is your question here fully answered? If not, can you please ask it more specifically?

For example, I don't get what you mean by:

Its ok when we have config_lkrg=m as module

[solardiz]

The title here says "for better lto performance" - to that, I can answer that no, at least with our current copy-builtin script, there's no LTO performance improvement. If we ever add tighter integration into the kernel, there may be some extra exposure to LTO, but I wouldn't expect significant performance improvement from it even then.

As to "community grow[th]", I agree that having a wider variety of build options may expand the userbase. The existing copy-builtin script is already of some help here.