Lines Matching refs:that

8 Here we will cover the architecture pieces that the common function tracing
10 complexity so that you can start simple and at least get basic functionality.
12 Note that this focuses on architecture implementation details only.  If you
38 We'll make the assumption below that the symbol is "mcount" just to keep things
41 Keep in mind that the ABI that is in effect inside of the mcount function is
52 so return immediately.  If it isn't, then call that function in the same way
55 size of the mcount call that is embedded in the function).
62 Also keep in mind that this mcount function will be called *a lot*, so
69 Here is some pseudo code that should help (these functions should actually be
127 that will return the original return address with which you can return to the
170 that the ABI that applies here is different from what applies to the mcount
200 that calls prepare_ftrace_return(), pass the frame pointer as the 3rd argument.
201 Then in the C version of that function, do what the x86 port does and pass it
221 - Have a NR_syscalls variable in <asm/unistd.h> that provides the number
270 Since no one else will have a decl for that function, you will need to:
295 the ftrace_stub() as that will now be inlined in ftrace_caller().
321 This might look a little odd at first, but keep in mind that we will be runtime
322 patching multiple things.  First, only functions that we actually want to trace
327 With that in mind, let's move on to the C code that will actually be doing the
332 to initialize some state, this is the time to do that.  Otherwise, this simple
340 There are two functions that are used to do runtime patching of arbitrary
344 typically that is ftracer_caller()).  See the general function definition in
348 The rec->ip value is the address of the mcount call site that was collected
354 at that location to support the new function calls you'll be inserting.  Some