Lines Matching full:there

28 There are many situations where users are reluctant to reboot a system. It may
39 There are multiple mechanisms in the Linux kernel that are directly related
59 a live patch is called with the help of a custom ftrace handler. But there are
66 Functions are there for a reason. They take some input parameters, get or
77 But there are more complex fixes. For example, a patch might change
93 switching combined with kpatch's stack trace switching.  There are also
132    (Note there's not yet such an approach for kthreads.)
155 There's also a /proc/<pid>/patch_state file which can be used to
163 actually delivered (there is no data in signal pending structures). Tasks are
168 /sys/kernel/livepatch/<patch>/force attribute. Writing 1 there clears
178 guaranteed there is no task sleeping in such module. It implies unbounded
189 For adding consistency model support to new architectures, there are a
193    for non-DWARF unwinders, also making sure there's a way for the stack
200    point in the loop where there are no locks taken and all data
207    There the safe location must be carefully selected on a case-by-case
232 relation between the original and the new implementation. Then there
234 module is loaded. Also there is code that cleans up before the
316 in the module_init() callback. There are two main reasons:
401 Module removal is only safe when there are no users of functions provided
413 by writing there.
461     There is a work in progress to add warnings about this situation.