/openbmc/linux/Documentation/RCU/ |
H A D | whatisRCU.rst | 149 c. synchronize_rcu() / call_rcu() 155 express synchronize_rcu() in terms of the call_rcu() callback API. 184 synchronize_rcu() 186 void synchronize_rcu(void); 191 have completed. Note that synchronize_rcu() will **not** 199 2. enters synchronize_rcu() 202 5. exits synchronize_rcu() 205 To reiterate, synchronize_rcu() waits only for ongoing RCU 207 any that begin after synchronize_rcu() is invoked. 209 Of course, synchronize_rcu() does not necessarily return [all …]
|
H A D | NMI-RCU.rst | 87 One way to accomplish this is via synchronize_rcu(), perhaps as 91 synchronize_rcu(); 94 This works because (as of v4.20) synchronize_rcu() blocks until all 97 Since NMI handlers disable preemption, synchronize_rcu() is guaranteed 99 to free up the handler's data as soon as synchronize_rcu() returns.
|
H A D | UP.rst | 52 Why is it *not* legal to invoke synchronize_rcu() in this case? 105 Note that it *is* safe for synchronize_rcu() to return immediately on 109 Why can't synchronize_rcu() return immediately on UP systems running 115 Why is it *not* legal to invoke synchronize_rcu() in this case? 145 Why can't synchronize_rcu() return immediately on UP systems 149 of an RCU read-side critical section. If synchronize_rcu()
|
H A D | checklist.rst | 205 6. Since synchronize_rcu() can block, it cannot be called 232 If the updater uses call_rcu() or synchronize_rcu(), then 264 disables BH when updaters use call_rcu() or synchronize_rcu(). 266 8. Although synchronize_rcu() is slower than is call_rcu(), 269 or the latency of synchronize_rcu() is visible from userspace, 270 synchronize_rcu() should be used in preference to call_rcu(). 272 in even simpler code than does synchronize_rcu() without 273 synchronize_rcu()'s multi-millisecond latency. So please take 277 An especially important property of the synchronize_rcu() 279 are delayed for whatever reason, then the synchronize_rcu() [all …]
|
/openbmc/qemu/tests/unit/ |
H A D | test-rcu-list.c | 244 synchronize_rcu(); in rcu_q_updater() 246 synchronize_rcu(); in rcu_q_updater() 306 synchronize_rcu(); in rcu_qtest() 310 synchronize_rcu(); in rcu_qtest()
|
H A D | rcutorture.c | 156 synchronize_rcu(); in rcu_update_perf_test() 337 synchronize_rcu(); in rcu_update_stress_test() 354 synchronize_rcu(); in rcu_fake_update_stress_test()
|
/openbmc/linux/include/linux/ |
H A D | rcutiny.h | 90 synchronize_rcu(); in synchronize_rcu_expedited() 110 synchronize_rcu(); in __kvfree_call_rcu()
|
H A D | rcupdate.h | 45 void synchronize_rcu(void); 177 # define synchronize_rcu_tasks synchronize_rcu 224 #define synchronize_rcu_tasks synchronize_rcu
|
/openbmc/linux/kernel/rcu/ |
H A D | tiny.c | 152 void synchronize_rcu(void) in synchronize_rcu() function 160 EXPORT_SYMBOL_GPL(synchronize_rcu);
|
/openbmc/linux/net/hsr/ |
H A D | hsr_slave.c | 197 synchronize_rcu(); in hsr_add_port() 228 synchronize_rcu(); in hsr_del_port()
|
/openbmc/linux/Documentation/RCU/Design/Requirements/ |
H A D | Requirements.rst | 101 14 synchronize_rcu(); 105 Because the synchronize_rcu() on line 14 waits for all pre-existing 110 started after the synchronize_rcu() started, and must therefore also 124 | block synchronize_rcu()!!! | 131 | Second, even when using synchronize_rcu(), the other update-side | 165 24 synchronize_rcu(); 169 28 synchronize_rcu(); 174 the synchronize_rcu() in start_recovery() to guarantee that 181 | Why is the synchronize_rcu() on line 28 needed? | 191 critical section must not contain calls to synchronize_rcu(). [all …]
|
/openbmc/linux/tools/memory-model/scripts/ |
H A D | simpletest.sh | 27 exclude="${exclude}\|synchronize_rcu(\|synchronize_rcu_expedited("
|
/openbmc/qemu/util/ |
H A D | rcu.c | 144 void synchronize_rcu(void) in synchronize_rcu() function 285 synchronize_rcu(); in call_rcu_thread()
|
/openbmc/linux/drivers/leds/ |
H A D | led-triggers.c | 178 synchronize_rcu(); in led_trigger_set() 202 synchronize_rcu(); in led_trigger_set() 245 synchronize_rcu(); in led_trigger_set()
|
/openbmc/linux/net/netfilter/ |
H A D | nf_nat_tftp.c | 44 synchronize_rcu(); in nf_nat_tftp_fini()
|
H A D | nf_nat_amanda.c | 68 synchronize_rcu(); in nf_nat_amanda_fini()
|
/openbmc/qemu/docs/devel/ |
H A D | rcu.rst | 74 ``void synchronize_rcu(void);`` 80 ``synchronize_rcu`` is running. Because of this, it is better that 82 ``synchronize_rcu``. If this is not possible (for example, because 261 synchronize_rcu(); 280 synchronize_rcu(); 293 Using ``synchronize_rcu()`` is undesirably expensive, because the 384 synchronize_rcu();
|
/openbmc/linux/net/caif/ |
H A D | cfcnfg.c | 109 synchronize_rcu(); in cfcnfg_create() 121 synchronize_rcu(); in cfcnfg_remove() 197 synchronize_rcu(); in caif_disconnect_client() 583 synchronize_rcu(); in cfcnfg_del_phy_layer()
|
/openbmc/linux/net/netfilter/ipvs/ |
H A D | ip_vs_fo.c | 69 synchronize_rcu(); in ip_vs_fo_cleanup()
|
H A D | ip_vs_lc.c | 83 synchronize_rcu(); in ip_vs_lc_cleanup()
|
H A D | ip_vs_ovf.c | 76 synchronize_rcu(); in ip_vs_ovf_cleanup()
|
H A D | ip_vs_nq.c | 133 synchronize_rcu(); in ip_vs_nq_cleanup()
|
H A D | ip_vs_sed.c | 134 synchronize_rcu(); in ip_vs_sed_cleanup()
|
H A D | ip_vs_wlc.c | 106 synchronize_rcu(); in ip_vs_wlc_cleanup()
|
/openbmc/linux/Documentation/litmus-tests/rcu/ |
H A D | RCU+sync+read.litmus | 33 synchronize_rcu();
|