Searched refs:ll (Results 1 – 16 of 16) sorted by relevance
| /tools/testing/selftests/kvm/x86/ |
| A D | hyperv_clock.c | 23 u64 ll; in mul_u64_u64_shr64() member
30 a0.ll = a; in mul_u64_u64_shr64()
31 b0.ll = b; in mul_u64_u64_shr64()
33 rm.ll = (u64)a0.l.low * b0.l.high; in mul_u64_u64_shr64()
34 rn.ll = (u64)a0.l.high * b0.l.low; in mul_u64_u64_shr64()
35 rh.ll = (u64)a0.l.high * b0.l.high; in mul_u64_u64_shr64()
40 return rh.ll; in mul_u64_u64_shr64()
|
| /tools/testing/selftests/net/ |
| A D | psock_tpacket.c | 70 struct sockaddr_ll ll; member
377 struct sockaddr_ll ll = { in walk_tx() local
403 ll.sll_ifindex = if_nametoindex("lo"); in walk_tx()
404 ret = bind(rcv_sock, (struct sockaddr *) &ll, sizeof(ll)); in walk_tx()
732 ring->ll.sll_family = PF_PACKET; in bind_ring()
733 ring->ll.sll_protocol = htons(ETH_P_ALL); in bind_ring()
734 ring->ll.sll_ifindex = if_nametoindex("lo"); in bind_ring()
735 ring->ll.sll_hatype = 0; in bind_ring()
736 ring->ll.sll_pkttype = 0; in bind_ring()
737 ring->ll.sll_halen = 0; in bind_ring()
[all …]
|
| A D | toeplitz.c | 343 struct sockaddr_ll ll = { 0 }; in create_ring() local
360 ll.sll_family = AF_PACKET; in create_ring()
361 ll.sll_ifindex = if_nametoindex(cfg_ifname); in create_ring()
362 ll.sll_protocol = cfg_family == AF_INET ? htons(ETH_P_IP) : in create_ring()
364 if (bind(fd, (void *)&ll, sizeof(ll))) in create_ring()
|
| /tools/testing/selftests/bpf/progs/ |
| A D | set_global_vars.c | 16 enum Enums64 { EC1 = 0ll, EC2 = 13ll };
|
| /tools/testing/selftests/net/packetdrill/ |
| A D | tcp_nagle_sendmsg_msg_more.pkt | 48 // Test we'll hold on the subsequent writes when inflight (3801:3951) > 0
|
| /tools/sched_ext/ |
| A D | README.md | 51 In order to run a sched_ext scheduler, you'll have to run a kernel compiled
211 schedulers. We'll go over some of the common ones here.
239 As described above, you'll need a `vmlinux.h` file that was generated from a
241 you'll see errors such as the following which indicate that a type being
|
| /tools/perf/Documentation/ |
| A D | perf-mem.txt | 179 sort keys ("mem" and "snoop"). So unlike other fields and sort keys, they'll
|
| A D | perf-script-python.txt | 92 don't care how it exited, so we'll use 'perf record' to record only
207 trace event, but rather aggregating it in a useful way. So we'll get
230 In trace_end(), we'll simply print the results, but first we need to
|
| A D | perf-trace.txt | 154 To be used with -s or -S, to select how to show summary. By default it'll
|
| A D | perf-top.txt | 371 but probably we'll make the default not to show the switch-on/off events
|
| A D | perf-config.txt | 432 This is an original overhead and we'll filter out the first 'foo'
|
| A D | perf-report.txt | 521 but probably we'll make the default not to show the switch-on/off events
|
| A D | perf-record.txt | 115 or CoreSight), it'll be processed as an address filter. Otherwise
|
| /tools/testing/selftests/nolibc/ |
| A D | nolibc-test.c | 1586 long long ll; in test_scanf() local
1638 &i, &l, &ll, &u, &ul, &ull) != 6) in test_scanf()
1641 if (i != 1 || l != 2 || ll != 3 || in test_scanf()
|
| /tools/power/pm-graph/ |
| A D | README | 139 When the system comes back you'll see the script finishing up and
|
| /tools/memory-model/Documentation/ |
| A D | explanation.txt | 1649 We'll consider just a very simple case:
2246 1 and 2 above. We'll go a little farther and say that two accesses
|
Completed in 33 milliseconds