Lines Matching refs:code
13 * the dangers of modifying code on the run.
46 * past the _mcount call and continue executing code like normal.
67 * Modifying code must take extra care. On an SMP machine, if
68 * the code being modified is also being executed on another CPU
70 * We use kstop_machine to stop other CPUS from executing code.
73 * the code to take care of this.
75 * Two buffers are added: An IP buffer and a "code" buffer.
78 * and the new code into the "code" buffer.
80 * we are modifying code, it is done in an atomic operation.
81 * 3) Write the code
87 * and if it is, it will write what is in the IP and "code" buffers.
90 * content to the code location. Also, if a CPU is executing code
91 * it is OK to write to that code location if the contents being written
118 * (and the code itself)
178 /* Make sure all running NMIs have finished before we write the code */
201 * Carefully read and modify the code with probe_kernel_*(), and make
264 unsigned char code[MCOUNT_INSN_SIZE];
266 if (copy_from_kernel_nofault(code, (void *)ip, MCOUNT_INSN_SIZE))
269 if (old_addr != __raw_readl((unsigned long *)code))