> IIUC, constprop means const propagation. For example, function > "foo(int a, int b)" that is called as "foo(a, 10)" will be come > "foo(int a)" with a hard-coded b = 10 inside. > > .part.0 is part of the function, as the other part is inlined in > the caller. > > With binary-diff based toolchain (kpatch-build), I think these will be > handled automatically. > > Thanks, > Song Yep, Thanks for your explanation! I discuss here just for an interest. IMO, more people may use tools like 'kpatch-build' to build a livepatch for it will be more easy. But I think such tools should also be attention to such changes because when it trying to do section-level or symbol-level operations. Otherwise it may cause problems :) > However, if we write the livepatch manually, we > need to understand these behavior with .constprop and .part. Do you think it is wise to write a livepatch module manually? If we are trying to write a module manually, we should also take care of the klp_* function calling, while using a livepatch building tools will help handle it :) Thanks. Wardenjohn
