Home
last modified time | relevance | path

Searched refs:marked (Results 1 – 24 of 24) sorted by relevance

/tools/testing/selftests/net/netfilter/packetdrill/
A Dconntrack_inexact_rst.pkt57 // marked INVALID, because conntrack is already closing.
60 // No packets should have been marked INVALID
A Dconntrack_syn_challenge_ack.pkt42 // No packets should have been marked INVALID
A Dconntrack_rst_invalid.pkt1 // check that out of window resets are marked as INVALID and conntrack remains
A Dconntrack_synack_old.pkt46 // No packets should have been marked INVALID in OUTPUT direction, 1 in INPUT
/tools/testing/selftests/powerpc/pmu/sampling_tests/
A Dmmcra_thresh_marked_sample_test.c64 FAIL_IF(EV_CODE_EXTRACT(event.attr.config, marked) != in mmcra_thresh_marked_sample()
/tools/memory-model/Documentation/
A Daccess-marking.txt73 2. Data-racy reads whose values are checked against marked reload.
110 fed into some operation that checks the full value against a later marked
234 It is important to comment marked accesses so that people reading your
245 if that concurrent access is marked with READ_ONCE(). In addition,
249 write is marked with data_race() or WRITE_ONCE().
320 this function can be marked __no_kcsan and the data_race() can be dropped:
366 Because foo is read locklessly, all accesses are marked. The purpose
368 concurrent write, whether marked or not.
487 Because foo is accessed locklessly, all accesses are marked. It does
536 flag buggy concurrent writes, even if: (1) Those writes are marked or
A Dordering.txt415 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.)
A Dglossary.txt119 accesses, or a marked access such as atomic_add_return()
158 Relaxed: A marked access that does not imply ordering, for example, a
A Dexplanation.txt2169 "marked" accesses, because they are all annotated with special
2352 cumul-fence, pb, and so on -- including vis) apply only to marked
2356 allowed to apply fancy transformations to marked accesses, and
2397 marked accesses.
2435 X and Y are both marked accesses. Hence an rfe link from X to
2453 executes before some marked access E. We can do this by finding a
2456 marked access Y such that X ->xb* Y, and Y and E are ordered by a
2512 *p; the marked load must execute before any of the machine
2616 isn't w-post-bounded by any marked accesses.
2652 as hb are limited to marked accesses only. As a result, the
[all …]
/tools/include/uapi/linux/
A Dpkt_sched.h280 __u32 marked; /* Marked packets */ member
380 __u32 marked; /* Marked packets */ member
648 __u32 marked; member
/tools/memory-model/
A Dlinux-kernel.bell87 (* Compute marked and plain memory accesses *)
A Dlinux-kernel.cat186 (* Warn about plain writes and marked accesses in the same region *)
/tools/testing/selftests/net/forwarding/
A Dsch_red.sh150 qdisc_stats_get $swp3 11: .marked
/tools/testing/selftests/tc-testing/creating-testcases/
A DAddingTestCases.txt39 marked as skipped. This key can be placed anywhere inside the
/tools/usb/usbip/
A DREADME189 First, let's list available remote devices that are marked as
/tools/testing/selftests/drivers/net/mlxsw/
A Dsch_red_core.sh315 qdisc_stats_get $swp3 $(get_qdisc_handle $vlan) .marked
/tools/objtool/Documentation/
A Dobjtool.txt336 annotated. A noreturn function must be marked __noreturn in both its
428 funcB obviously does not call schedule(), and is marked notrace (since
/tools/power/cpupower/po/
A Dzh_CN.po499 "For the arguments marked with *, omitting the -c or --cpu argument is\n"
A Dka.po533 "For the arguments marked with *, omitting the -c or --cpu argument is\n"
A Dfr.po503 "For the arguments marked with *, omitting the -c or --cpu argument is\n"
A Dcs.po501 "For the arguments marked with *, omitting the -c or --cpu argument is\n"
A Dit.po502 "For the arguments marked with *, omitting the -c or --cpu argument is\n"
A Dpt.po504 "For the arguments marked with *, omitting the -c or --cpu argument is\n"
A Dde.po518 "For the arguments marked with *, omitting the -c or --cpu argument is\n"

Completed in 126 milliseconds