Home
last modified time | relevance | path

Searched refs:ASSERT_EXCLUSIVE_WRITER (Results 1 – 7 of 7) sorted by relevance

/linux-6.1.9/kernel/events/
Dhw_breakpoint.c255 ASSERT_EXCLUSIVE_WRITER(hist->count[i]); in bp_slots_histogram_max()
273 ASSERT_EXCLUSIVE_WRITER(hist1->count[i]); in bp_slots_histogram_max_merge()
274 ASSERT_EXCLUSIVE_WRITER(hist2->count[i]); in bp_slots_histogram_max_merge()
/linux-6.1.9/include/linux/
Dkcsan-checks.h370 #define ASSERT_EXCLUSIVE_WRITER(var) \ macro
/linux-6.1.9/tools/memory-model/Documentation/
Daccess-marking.txt223 ASSERT_EXCLUSIVE_WRITER(foo) tells KCSAN that although it is OK for there
229 ASSERT_EXCLUSIVE_ACCESS() or ASSERT_EXCLUSIVE_WRITER() on the one hand
332 ASSERT_EXCLUSIVE_WRITER(foo);
344 of the ASSERT_EXCLUSIVE_WRITER() is to allow KCSAN to check for a buggy
465 not make sense to use ASSERT_EXCLUSIVE_WRITER() in this case because
/linux-6.1.9/kernel/rcu/
Dtree.c1467 ASSERT_EXCLUSIVE_WRITER(rcu_state.gp_seq); in rcu_gp_init()
1787 ASSERT_EXCLUSIVE_WRITER(rcu_state.gp_seq); in rcu_gp_cleanup()
4241 ASSERT_EXCLUSIVE_WRITER(rcu_state.ncpus); in rcu_cpu_starting()
/linux-6.1.9/kernel/
Dfork.c469 ASSERT_EXCLUSIVE_WRITER(orig->vm_flags); in vm_area_dup()
470 ASSERT_EXCLUSIVE_WRITER(orig->vm_file); in vm_area_dup()
/linux-6.1.9/Documentation/dev-tools/
Dkcsan.rst229 :functions: ASSERT_EXCLUSIVE_WRITER ASSERT_EXCLUSIVE_WRITER_SCOPED
/linux-6.1.9/kernel/kcsan/
Dkcsan_test.c363 ASSERT_EXCLUSIVE_WRITER(test_var); in test_kernel_assert_writer()