Searched refs:cpu_id_start (Results 1 – 6 of 6) sorted by relevance
25 cpu_id_in_sigfn = rs->cpu_id_start; in sigfn()55 rs->cpu_id_start = -1; in TEST_F()57 ASSERT_NE(rs->cpu_id_start, -1); in TEST_F()59 rs->cpu_id_start = -1; in TEST_F()61 ASSERT_NE(rs->cpu_id_start, -1); in TEST_F()
96 __u32 cpu_id_start; member
195 return RSEQ_ACCESS_ONCE(rseq_get_abi()->cpu_id_start); in rseq_cpu_start()
115 __u32 cpu_id_start; member
400 unsafe_put_user(0, &rseq->cpu_id_start, efault); in rseq_reset_ids()451 unsafe_put_user(RSEQ_CPU_ID_UNINITIALIZED, &rseq->cpu_id_start, efault); in rseq_register()
54 - The cpu_id_start, cpu_id, node_id and mm_cid fields (User mode read105 overwrite the cpu_id_start field for their own purposes. This is obviously