On Thu, 2025-02-20 at 21:06 -0800, Amery Hung wrote: > On Thu, Feb 20, 2025 at 7:02 PM Eduard Zingerman <eddyz87@xxxxxxxxx> wrote: [...] > > > > So, for this particular case there are only two options: resolve id > > dynamically, as you did, or use a kfunc internal to this module > > instead (which should simplify the test, imo). > > > > Currently, generating module kfunc in pro/epilogue is not supported > due to the complication in resolving insn->off of the kfunc call. I > have one patch that test how it can work. But after some discussion > with Martin, we think we can revisit it when there is a struct_ops > module that wants to do so. I will keep the current dynamic btf id > resolution in the next respin over using module kfunc unless people > think we should support it now. Fair enough. Sorry for the false trail with BTF_ID_LIST, this resolve_btfids corner case was a surprise for me.
