Lines Matching +refs:module +refs:get +refs:op

1124 eventually get the data where it needs to go. In general, when tracking
1475    handler to get around to it.
1511 kernel) you will get an RCU CPU stall warning. Nevertheless, this class
1770 implementation can be a no-op.
1857 unloaded. After a given module has been unloaded, any attempt to call
1858 one of its functions results in a segmentation fault. The module-unload
1859 functions must therefore cancel any delayed calls to loadable-module
1867 module unload request, we need some other way to deal with in-flight RCU
1871 in-flight RCU callbacks have been invoked. If a module uses
1874 the underlying module-unload code could invoke rcu_barrier()
1880 rcu_barrier() into RCU. The need for rcu_barrier() for module
2151    Otherwise, you will get RCU CPU stall warnings. Or at best, very long
2155    critical sections, and RCU believes this CPU to be idle, you will get
2175    If the gap grows too long, you get RCU CPU stall warnings.
2184    long, you get RCU CPU stall warnings.
2716 be the last word on this subject, but at least it serves to get an