On Sat, 17 Apr 2021 00:03:04 +0900 Masami Hiramatsu <mhiramat@xxxxxxxxxx> wrote: > > Anyway, IIRC, Masami wasn't sure that the full regs was ever needed for the > > return (who cares about the registers on return, except for the return > > value?) > > I think kretprobe and ftrace are for a bit different usage. kretprobe can be > used for something like debugger. In that case, accessing full regs stack > will be more preferrable. (BTW, what the not "full regs" means? Does that > save partial registers?) When the REGS flag is not set in the ftrace_ops (where kprobes uses the REGS flags), the regs parameter is not a full set of regs, but holds just enough to get access to the parameters. This just happened to be what was saved in the mcount/fentry trampoline, anyway, because tracing the start of the program, you had to save the arguments before calling the trace code, otherwise you would corrupt the parameters of the function being traced. I just tweaked it so that by default, the ftrace callbacks now have access to the saved regs (call ftrace_regs, to not let a callback get confused and think it has full regs when it does not). Now for the exit of a function, what does having the full pt_regs give you? Besides the information to get the return value, the rest of the regs are pretty much meaningless. Is there any example that someone wants access to the regs at the end of a function besides getting the return value? -- Steve
