| /linux-6.15/tools/testing/selftests/bpf/prog_tests/ |
| H A D | tcp_rtt.c | 9 __u32 invoked; member
50 static int verify_sk(int map_fd, int client_fd, const char *msg, __u32 invoked, in verify_sk() argument
60 if (val.invoked != invoked) { in verify_sk()
62 msg, val.invoked, invoked); in verify_sk()
|
| H A D | mptcp.c | 64 __u32 invoked; member
92 if (!ASSERT_EQ(val.invoked, 1, "unexpected invoked count")) in verify_tsk()
136 if (!ASSERT_EQ(val.invoked, 1, "unexpected invoked count")) in verify_msk()
|
| /linux-6.15/Documentation/core-api/ |
| H A D | cpu_hotplug.rst | 159 the state CPUHP_ONLINE is reached. They can also be invoked when the
163 When a CPU is offlined the teardown callbacks are invoked in the reverse
165 be invoked when the callbacks of a state are removed or an instance is
179 The startup callbacks in this section are invoked before the CPU is
203 The startup callbacks in this section are invoked on the hotplugged CPU
205 setup code. The teardown callbacks are invoked with interrupts disabled
224 which is pinned on the hotplugged CPU. The callbacks are invoked with
347 startup callback has to be invoked before the PERF driver startup
429 be invoked during a CPU offline operation. If the usage site does not
560 section the callback is either invoked on the current CPU (PREPARE
[all …]
|
| H A D | entry.rst | 64 invoked from low-level assembly code looks like this:
90 function can be invoked. The instrumentable code section then ends, after which
91 syscall_exit_to_user_mode() is invoked.
169 means that up to the point where irq_enter_rcu() is invoked in_hardirq()
|
| H A D | cachetlb.rst | 10 after the interface is invoked.
38 This is usually invoked when the kernel page tables are
95 At the end of every page fault, this routine is invoked to tell
100 This routine is also invoked in various other places which pass
220 The first of these two routines is invoked after vmap_range()
221 has installed the page table entries. The second is invoked
|
| /linux-6.15/Documentation/scsi/ |
| H A D | scsi_eh.rst | 67 scsi_finish_command() is invoked for the command. The
83 scsi_eh_scmd_add(scmd) is invoked for the command. See
113 3. scsi_eh_scmd_add(scmd) is invoked for the
124 Otherwise scsi_eh_scmd_add() is invoked for the command.
260 :ACTION: scsi_eh_scmd_add() is invoked for scmd
278 :ACTION: scsi_eh_finish_cmd() is invoked to EH-finish scmd
297 - otherwise, scsi_finish_command() is invoked for scmd
341 scsi_eh_finish_cmd() is invoked.
344 scsi_eh_finish_cmd() invoked
403 is invoked. If host reset succeeds, all failed scmds on
[all …]
|
| /linux-6.15/tools/testing/selftests/bpf/progs/ |
| H A D | tcp_rtt.c | 8 __u32 invoked; member
54 storage->invoked++; in _sockops()
|
| H A D | mptcp_sock.c | 13 __u32 invoked; member
73 storage->invoked++; in _sockops()
|
| /linux-6.15/Documentation/RCU/ |
| H A D | lockdep.rst | 43 invoked by both RCU readers and updaters.
47 is invoked by both RCU-bh readers and updaters.
51 is invoked by both RCU-sched readers and updaters.
55 is invoked by both SRCU readers and updaters.
64 invoked only by updaters.
91 from taking place. If the above statement was invoked only from updater
|
| H A D | UP.rst | 30 This same problem can occur if call_rcu() is invoked from a hardware
59 Suppose that call_rcu() is invoked while holding a lock, and that the
77 It is far better to guarantee that callbacks are invoked
119 Therefore, the called function has been invoked within an RCU
134 then, since RCU callbacks can be invoked from softirq context,
|
| /linux-6.15/Documentation/networking/ |
| H A D | tls-handshake.rst | 71 @ta_done contains a callback function that is invoked when the handshake
101 zero return guarantees the callback function @ta_done will be invoked
104 @ta_done will not be invoked on this socket.
155 will not be invoked. If this function returns false, then the consumer's
156 completion callback has already been invoked.
165 field in the tls_handshake_args structure, is invoked.
212 Once the handshake completion callback function has been invoked, normal
|
| /linux-6.15/Documentation/virt/kvm/ |
| H A D | halt-polling.rst | 19 invoked. Thus halt polling is especially useful on workloads with very short
49 received during the polling interval (and thus schedule is invoked) there are
76 invoked and a wakeup source received (irrespective of
77 whether the scheduler is invoked within that function).
151 that cpu, otherwise the polling will cease immediately and schedule will be invoked to
|
| /linux-6.15/Documentation/virt/kvm/devices/ |
| H A D | vfio.rst | 55 The FILE/GROUP_ADD operation above should be invoked prior to accessing the
60 descriptors, FILE_ADD should be invoked before VFIO_DEVICE_BIND_IOMMUFD
|
| /linux-6.15/Documentation/networking/dsa/ |
| H A D | dsa.rst | 250 - receive function is invoked
277 - invoked ``netif_receive_skb()``
316 calls ``dsa_switch_rcv()``, is invoked early (on the physical DSA conduit;
394 function hooks should be invoked, information about the directly attached
754 - ``port_enable``: function invoked by the DSA user network device ndo_open
959 - ``port_bridge_flags``: bridge layer function invoked when a port must
970 - ``port_fast_age``: bridge layer function invoked when flushing the
989 - ``port_vlan_add``: bridge layer function invoked when a VLAN is configured
1046 - ``port_lag_join``: function invoked when a given switch port is added to a
1050 - ``port_lag_leave``: function invoked when a given switch port leaves a LAG
[all …]
|
| /linux-6.15/Documentation/admin-guide/ |
| H A D | workload-tracing.rst | 36 This method of tracing using strace tells us the system calls invoked by
37 the workload and doesn't include all the system calls that can be invoked
39 these system calls that are invoked. As an example, if a workload opens a
161 invoked by a process.
326 The below table shows the system calls invoked by the workload, number of
327 times each system call is invoked, and the corresponding Linux subsystem.
436 The below table shows the system calls invoked by the workload, number of
437 times each system call is invoked, and the corresponding Linux subsystem.
530 The below table shows the system calls invoked by the workload, number of
531 times each system call is invoked, and the corresponding Linux subsystem.
|
| H A D | binfmt-misc.rst | 8 To achieve this you must tell binfmt_misc which interpreter has to be invoked
50 is the program that should be invoked with the binary as first
85 binary lazily when the misc format file is invoked. However,
|
| /linux-6.15/Documentation/pcmcia/ |
| H A D | driver.rst | 20 Once added, the driver probe routine will be invoked for any unclaimed
|
| /linux-6.15/Documentation/bpf/ |
| H A D | prog_sk_lookup.rst | 11 When invoked BPF sk_lookup program can select a socket that will receive the
41 invoked in the same order as they were attached.
|
| /linux-6.15/Documentation/locking/ |
| H A D | seqlock.rst | 48 write side section. If the read section can be invoked from hardirq or
154 side can be invoked from NMI handlers.
167 If the read side section can be invoked from hardirq or softirq context,
|
| /linux-6.15/Documentation/scheduler/ |
| H A D | sched-ext.rst | 157 * callback will only be invoked if we failed to find a core to insert
210 ``ops.dispatch()`` is invoked.
218 invoked. This serves two purposes. First, CPU selection optimization
240 2. Once the target CPU is selected, ``ops.enqueue()`` is invoked (unless the
255 run, ``ops.dispatch()`` is invoked which can use the following two
|
| /linux-6.15/Documentation/devicetree/bindings/arm/firmware/ |
| H A D | sdei.txt | 10 and enabling/disabling events. Functions are invoked by trapping to the
|
| /linux-6.15/Documentation/driver-api/memory-devices/ |
| H A D | ti-emif.rst | 51 affecting EMIF and takes appropriate actions when these are invoked.
|
| /linux-6.15/Documentation/driver-api/pm/ |
| H A D | cpuidle.rst | 43 A CPU idle time (``CPUIdle``) governor is a bundle of policy code invoked when
91 until the ``->enable()`` governor callback is invoked for that CPU
104 callback when it was last invoked for the target CPU, free all memory
143 selection made by the ``->select()`` callback (when it was invoked last
255 be invoked for the logical CPU represented by it, so it must take place after
|
| /linux-6.15/Documentation/admin-guide/pm/ |
| H A D | cpufreq.rst | 118 the scaling driver, the ``CPUFreq`` core will be invoked to take note of them
121 In any case, the ``CPUFreq`` core is invoked to take note of any logical CPU it
129 Once invoked, the ``CPUFreq`` core checks if the policy pointer is already set
135 Next, the scaling driver's ``->init()`` callback is invoked with the policy
158 The utilization update callbacks will be invoked by the CPU scheduler on
164 the P-state selection. The scaling driver may be invoked directly from
184 new policy objects. Instead, the driver's ``->setpolicy()`` callback is invoked
186 callbacks are invoked by the CPU scheduler in the same way as for scaling
416 invoking its utilization update callback for that CPU. If it is invoked by the
419 if it is invoked by the CFS scheduling class, the governor will use the
[all …]
|
| /linux-6.15/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-remove-bufs.rst | 39 are invoked.
|