On Sat, 20 Aug 2022 09:38:21 +0800And there is still something left to do, Qing will do that.
Jinyang He <hejinyang@xxxxxxxxxxx> wrote:
I think we have implemented CONFIG_FTRACE_WITH_ARGS in dynamic ftraceSorry, I must have missed it.
in the [Patch3/9].
Yes, it is clear.
But, for non dynamic ftrace, it is hardly toDon't bother implementing it for non-dynamic. I would just add a:
implement it. Because the LoongArch compiler gcc treats mount as a
config HAVE_FTRACE_WITH_ARGS if DYNAMIC_FTRACE
and be done with it.
Thanks for your detail answers.
really call, like 'call _mcount(__builtin_return_address(0))'. ThatRight, there's no point in implementing it for non dynamic. Like I said,
means, they decrease stack, save args to callee saved regs and may
do some optimization before calling mcount. It is difficult to find the
original args and apply changes from tracers.
non-dynamic is just a stepping stone for getting dynamic working. Once you
have dynamic working, it's up to you to throw out the non-dynamic. It's not
useful for anything other than porting to a new architecture or for
academic purposes.