Lines Matching refs:there

46 a live patch is called with the help of a custom ftrace handler. But there are
53 Functions are there for a reason. They take some input parameters, acquire or
64 But there are more complex fixes. For example, a patch might change
119    (Note there's not yet such an approach for kthreads.)
150 actually delivered (there is no data in signal pending structures). Tasks are
155 /sys/kernel/livepatch/<patch>/force attribute. Writing 1 there clears
165 guaranteed there is no task sleeping in such module. It implies unbounded
176 For adding consistency model support to new architectures, there are a
180    for non-DWARF unwinders, also making sure there's a way for the stack
187    point in the loop where there are no locks taken and all data
219 relation between the original and the new implementation. Then there
221 module is loaded. Also there is code that cleans up before the
388 Module removal is only safe when there are no users of functions provided
400 by writing there.