| /tools/testing/selftests/bpf/progs/ |
| A 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()
|
| A 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/testing/selftests/net/packetdrill/ |
| A D | tcp_ts_recent_invalid_ack.pkt | 2 // Test that we reject TS val updates on a packet with invalid ACK sequence
20 // bad packet with high tsval (its ACK sequence is above our sndnxt)
|
| A D | tcp_rcv_big_endseq.pkt | 25 // packet in sequence : SKB_DROP_REASON_TCP_INVALID_END_SEQUENCE / LINUX_MIB_BEYOND_WINDOW
|
| A D | tcp_dsack_mult.pkt | 23 // Check SACK coalescing (contiguous sequence).
|
| A D | tcp_close_close-remote-fin-then-close.pkt | 2 // Verify behavior for the sequence: remote side sends FIN, then we close().
|
| A D | tcp_sack_sack-shift-sacked-7-3-4-8-9-fack.pkt | 44 // because >=3 higher-sequence packets are SACKed.
|
| /tools/testing/selftests/kvm/ |
| A D | steal_time.c | 216 uint32_t sequence; member
238 GUEST_ASSERT(!(READ_ONCE(st->sequence) & 1)); in check_status()
246 uint32_t sequence; in guest_code() local
258 sequence = READ_ONCE(st->sequence); in guest_code()
263 GUEST_ASSERT(sequence < READ_ONCE(st->sequence)); in guest_code()
294 pr_info(" sequence: %d\n", st->sequence); in steal_time_dump()
|
| /tools/include/uapi/drm/ |
| A D | drm.h | 496 unsigned int sequence; member
502 unsigned int sequence; member
1013 __u64 sequence; /* return: most recent vblank sequence */ member
1027 __u64 sequence; /* on input, target sequence. on output, actual sequence */ member
1374 __u32 sequence; member
1385 __u64 sequence; member
|
| /tools/memory-model/ |
| A D | linux-kernel.cat | 54 * However, in a longer sequence of lock handovers, the implicit
99 let rmw-sequence = (rf ; rmw)*
101 po-unlock-lock-po) ; [Marked] ; rmw-sequence
147 * Any sequence containing at least as many grace periods as RCU read-side
200 let w-post-bounded = fence? ; [Marked] ; rmw-sequence
|
| /tools/testing/selftests/net/netfilter/packetdrill/ |
| A D | conntrack_rst_invalid.pkt | 51 // exact next sequence
|
| A D | conntrack_inexact_rst.pkt | 1 // check RST packet that doesn't exactly match expected next sequence
|
| A D | conntrack_synack_old.pkt | 3 // tcpdump with buggy sequence
|
| /tools/firewire/ |
| A D | nosy-dump.h | 61 uint32_t sequence:3; member
|
| A D | nosy-dump.c | 785 pp->ext_self_id.phy_id, pp->ext_self_id.sequence); in print_packet()
|
| /tools/memory-model/Documentation/ |
| A 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
|
| A D | explanation.txt | 984 the following sequence of events:
1025 U ->cumul-fence X -> rmw-sequence Y
1461 link in the sequence is fre instead of coe.
1989 it permits an arbitrarily long sequence of
2265 if they can be connected by a sequence of hb, pb, and rb links
2287 X is connected to Z by a possibly empty sequence of
2294 possibly empty sequence of xb links,
2299 empty sequence of xb links (again, if the sequence is empty it
2506 is, in the sequence:
2624 sequence. If W is plain then they also have to be linked by an
[all …]
|
| /tools/testing/selftests/arm64/signal/ |
| A D | README | 8 enforces a standard sequence of operations needed to perform a single
|
| /tools/testing/selftests/iommu/ |
| A D | iommufd_utils.h | 1091 hdr->sequence - *prev_seq > 1) { in _test_cmd_read_vevents()
1092 *prev_seq = hdr->sequence; in _test_cmd_read_vevents()
1097 *prev_seq = hdr->sequence; in _test_cmd_read_vevents()
|
| /tools/testing/selftests/bpf/prog_tests/ |
| A D | tc_netkit.c | 33 __be16 sequence; member
168 icmp.echo.sequence = 1; in __send_icmp()
|
| /tools/perf/Documentation/ |
| A 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
|
| A 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/testing/selftests/net/forwarding/ |
| A D | vxlan_bridge_1d.sh | 594 )"00:01:"$( : ICMP request sequence number
|
| /tools/bpf/bpftool/Documentation/ |
| A D | bpftool-map.rst | 100 If the **hex** keyword is provided in front of the bytes sequence, the
|
| /tools/testing/selftests/hid/tests/ |
| A D | test_multitouch.py | 1144 sequence = [
1156 for num, r_str in enumerate(sequence):
|