| /tools/testing/selftests/bpf/progs/ |
| D | modify_return.c | 13 static int sequence = 0; variable
20 sequence++; in BPF_PROG()
21 fentry_result = (sequence == 1); in BPF_PROG()
29 sequence++; in BPF_PROG()
31 fmod_ret_result = (sequence == 2 && ret == 0); in BPF_PROG()
39 sequence++; in BPF_PROG()
44 fexit_result = (sequence == 3 && ret == input_retval); in BPF_PROG()
46 fexit_result = (sequence == 3 && ret == 4); in BPF_PROG()
|
| D | xdping_kern.c | 116 if (!pinginfo || pinginfo->seq != icmph->un.echo.sequence) in xdping_client()
142 seq = bpf_htons(bpf_ntohs(icmph->un.echo.sequence) + 1); in xdping_client()
143 icmph->un.echo.sequence = seq; in xdping_client()
|
| /tools/lib/traceevent/Documentation/ |
| D | libtraceevent-tseq.txt | 9 Initialize / destroy a trace sequence.
35 The _trace_seq_init()_ function initializes the trace sequence _s_.
37 The _trace_seq_destroy()_ function destroys the trace sequence _s_ and frees
40 The _trace_seq_reset()_ function re-initializes the trace sequence _s_. All
43 The _trace_seq_terminate()_ function terminates the trace sequence _s_. It puts
47 sequence _s_.
50 trace sequence _s_.
53 variable arguments _..._ in the trace sequence _s_.
56 list of arguments _args_ in the trace sequence _s_.
58 The _trace_seq_do_printf()_ function prints the buffer of trace sequence _s_ to
[all …]
|
| D | libtraceevent-event_print.txt | 6 tep_print_event - Writes event information into a trace sequence.
22 _record_ and writes it into the trace sequence _s_, according to the format
|
| D | libtraceevent-reg_print_func.txt | 50 the trace sequence, it can be used to create a custom string.
|
| D | libtraceevent-reg_event_handler.txt | 49 function. The _s_ argument is the trace sequence, it can be used to create a
|
| /tools/testing/selftests/powerpc/dscr/ |
| D | dscr_default_test.c | 15 static unsigned long sequence; variable
27 s1 = READ_ONCE(sequence); in do_test()
37 s2 = sequence; in do_test()
89 sequence++; in dscr_default()
99 sequence++; in dscr_default()
|
| /tools/include/uapi/drm/ |
| D | drm.h | 497 unsigned int sequence; member
503 unsigned int sequence; member
794 __u64 sequence; /* return: most recent vblank sequence */ member
808 __u64 sequence; /* on input, target sequence. on output, actual sequence */ member
990 __u32 sequence; member
1001 __u64 sequence; member
|
| D | i915_drm.h | 695 unsigned int sequence; member
|
| /tools/firewire/ |
| D | nosy-dump.h | 61 uint32_t sequence:3; member
|
| D | nosy-dump.c | 785 pp->ext_self_id.phy_id, pp->ext_self_id.sequence); in print_packet()
|
| /tools/memory-model/Documentation/ |
| D | simple.txt | 136 have been built out into an API. One of these APIs is sequence locking.
141 The basic keep-things-simple rule for sequence locking is "do not write
142 in read-side code". Yes, you can do writes from within sequence-locking
147 cases involving combining sequence locking with other synchronization
148 primitives. (LKMM does not yet know about sequence locking, so it is
|
| D | explanation.txt | 931 the following sequence of events:
1361 Consider first the case where E is a store (implying that the sequence
1378 link in the sequence is fre instead of coe.
1541 The LKMM goes on to define the rcu-order relation as a sequence of
1548 would imply that X ->rcu-order V, because this sequence contains two
1554 does not imply X ->rcu-order V, because the sequence contains only
1742 sequence of relations contains fewer instances of rcu-gp (one) than of
1774 rcu-order sequence (the srcu-rscsi links must be paired with srcu-gp
2021 if they can be connected by a sequence of hb, pb, and rb links
2043 X is connected to Z by a possibly empty sequence of
[all …]
|
| D | litmus-tests.txt | 1000 might interpret the following sequence as two partially
|
| /tools/testing/selftests/arm64/signal/ |
| D | README | 8 enforces a standard sequence of operations needed to perform a single
|
| /tools/perf/Documentation/ |
| D | perf.data-file-format.txt | 58 Some headers consist of a sequence of strings, which start with a
76 The header consists of an sequence of build_id_event. The size of each record
|
| D | jitdump-specification.txt | 132 The debug_entry entries are saved in sequence but given that they have variable sizes due to the fi…
|
| /tools/memory-model/ |
| D | linux-kernel.cat | 124 * Any sequence containing at least as many grace periods as RCU read-side
|
| /tools/testing/selftests/net/forwarding/ |
| D | vxlan_bridge_1d.sh | 586 )"00:01:"$( : ICMP request sequence number
|
| /tools/bpf/bpftool/Documentation/ |
| D | bpftool-map.rst | 99 sequence, the bytes are parsed as hexadecimal values, even if
|