Lines Matching full:there

15 There are many situations where users are reluctant to reboot a system. It may
26 There are multiple mechanisms in the Linux kernel that are directly related
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, get or
64 But there are more complex fixes. For example, a patch might change
80 switching combined with kpatch's stack trace switching.  There are also
119    (Note there's not yet such an approach for kthreads.)
142 There's also a /proc/<pid>/patch_state file which can be used to
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
194    There the safe location must be carefully selected on a case-by-case
219 relation between the original and the new implementation. Then there
221 module is loaded. Also there is code that cleans up before the
303 in the module_init() callback. There are two main reasons:
388 Module removal is only safe when there are no users of functions provided
400 by writing there.
448     There is a work in progress to add warnings about this situation.