Searched refs:marked (Results 1 – 17 of 17) sorted by relevance
/tools/memory-model/Documentation/ |
D | access-marking.txt | 67 2. Data-racy reads whose values are checked against marked reload. 104 fed into some operation that checks the full value against a later marked 211 It is important to comment marked accesses so that people reading your 222 if that concurrent access is marked with READ_ONCE(). In addition, 226 write is marked with data_race() or WRITE_ONCE(). 297 this function can be marked __no_kcsan and the data_race() can be dropped: 343 Because foo is read locklessly, all accesses are marked. The purpose 464 Because foo is accessed locklessly, all accesses are marked. It does 513 flag buggy concurrent writes, even if: (1) Those writes are marked or
|
D | ordering.txt | 415 A control dependency extends from a marked load (READ_ONCE() or stronger) 416 through an "if" condition to a marked store (WRITE_ONCE() or stronger) 443 a. Unordered marked operations. 454 of unordered marked accesses can also be constrained using the mechanisms 464 reorder marked writes with each other or with other unordered 472 reorder marked reads with each other or with other unordered 528 accesses is a write, whether marked or not.)
|
D | glossary.txt | 119 accesses, or a marked access such as atomic_add_return() 158 Relaxed: A marked access that does not imply ordering, for example, a
|
D | explanation.txt | 1925 "marked" accesses, because they are all annotated with special 2108 cumul-fence, pb, and so on -- including vis) apply only to marked 2112 allowed to apply fancy transformations to marked accesses, and 2153 marked accesses. 2191 X and Y are both marked accesses. Hence an rfe link from X to 2209 executes before some marked access E. We can do this by finding a 2210 marked access X such that R and X are ordered by a suitable fence and 2212 marked access Y such that X ->xb* Y, and Y and E are ordered by a 2222 say that a marked access pre-bounds and post-bounds itself (e.g., if R 2223 above were a marked load then X could simply be taken to be R itself.) [all …]
|
/tools/power/cpupower/ |
D | README | 34 edit the block marked CONFIGURATION.
|
/tools/include/uapi/linux/ |
D | pkt_sched.h | 280 __u32 marked; /* Marked packets */ member 380 __u32 marked; /* Marked packets */ member 757 __u32 marked; member
|
/tools/memory-model/ |
D | linux-kernel.bell | 81 (* Compute marked and plain memory accesses *)
|
D | linux-kernel.cat | 163 (* Warn about plain writes and marked accesses in the same region *)
|
/tools/testing/selftests/net/forwarding/ |
D | sch_red.sh | 169 qdisc_stats_get $swp3 11: .marked
|
/tools/testing/selftests/tc-testing/creating-testcases/ |
D | AddingTestCases.txt | 39 marked as skipped. This key can be placed anywhere inside the
|
/tools/usb/usbip/ |
D | README | 189 First, let's list available remote devices that are marked as
|
/tools/objtool/Documentation/ |
D | stack-validation.txt | 314 funcB obviously does not call schedule(), and is marked notrace (since
|
/tools/power/cpupower/po/ |
D | cs.po | 501 "For the arguments marked with *, omitting the -c or --cpu argument is\n"
|
D | fr.po | 503 "For the arguments marked with *, omitting the -c or --cpu argument is\n"
|
D | it.po | 502 "For the arguments marked with *, omitting the -c or --cpu argument is\n"
|
D | pt.po | 504 "For the arguments marked with *, omitting the -c or --cpu argument is\n"
|
D | de.po | 518 "For the arguments marked with *, omitting the -c or --cpu argument is\n"
|