Searched refs:thread1 (Results 1 – 5 of 5) sorted by relevance
| /openbmc/linux/tools/testing/selftests/powerpc/benchmarks/ |
| H A D | context_switch.c | 166 void *(*thread1)(void *); member
215 .thread1 = pipe_thread1,
254 .thread1 = yield_thread1,
384 .thread1 = futex_thread1,
501 start_fn(actions->thread1, NULL, cpu1); in main()
|
| /openbmc/linux/Documentation/devicetree/bindings/cpu/ |
| H A D | cpu-topology.txt | 198 thread1 {
207 thread1 {
218 thread1 {
227 thread1 {
240 thread1 {
248 thread1 {
259 thread1 {
267 thread1 {
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | microcode.rst | 181 When thread0 of a core is doing the microcode update, if thread1 is
|
| /openbmc/linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 98 11 void thread1(void)
107 ``x`` must complete before thread1() stores to ``y``, so that
716 11 void thread1(void)
726 After thread0() and thread1() execute concurrently, it is quite
771 13 void thread1(void)
780 thread1() function's update, the WARN_ON() could never fire. But
831 9 void thread1(void)
874 9 void thread1(void)
897 before the end of thread1()'s grace period. If in addition
900 that ``(r2 == 1)``, then the end of thread1()'s grace period must
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | atomics.rst | 342 | pthread_exit(a); | pthread_join(thread1, &a); |
|