Home
last modified time | relevance | path

Searched full:invoked (Results 1 – 25 of 1695) sorted by relevance

12345678910>>...68

/kernel/linux/linux-5.10/include/linux/
Dentry-common.h82 * Invoked from syscall_enter_from_user_mode() in the non-instrumentable
101 * Invoked from syscall_enter_from_user_mode()
116 * Invoked from architecture specific syscall entry code with interrupts
123 * This is invoked when there is extra architecture specific functionality
134 * Invoked from architecture specific syscall entry code with interrupts
159 * Invoked from architecture specific syscall entry code with interrupts
209 * Invoked from exit_to_user_mode_loop() with interrupt enabled
229 * Invoked from exit_to_user_mode_prepare() with interrupt disabled as the last
246 * Invoked from exit_to_user_mode() with interrupt disabled as the last
250 * invoked after context tracking switched to user mode.
[all …]
/kernel/linux/linux-5.10/tools/testing/selftests/bpf/prog_tests/
Dtcp_rtt.c7 __u32 invoked; member
46 static int verify_sk(int map_fd, int client_fd, const char *msg, __u32 invoked, in verify_sk() argument
58 if (val.invoked != invoked) { in verify_sk()
59 log_err("%s: unexpected bpf_tcp_sock.invoked %d != %d", in verify_sk()
60 msg, val.invoked, invoked); in verify_sk()
128 /*invoked=*/1, in run_test()
142 /*invoked=*/2, in run_test()
/kernel/linux/linux-5.10/Documentation/networking/dsa/
Ddsa.rst109 - receive function is invoked
136 - invoked ``netif_receive_skb()``
228 function hooks should be invoked, information about the directly attached
359 - ``probe``: probe routine which will be invoked by the DSA platform device upon
387 - ``phy_read``: Function invoked by the DSA slave MDIO bus when attempting to read
392 - ``phy_write``: Function invoked by the DSA slave MDIO bus when attempting to write
396 - ``adjust_link``: Function invoked by the PHY library when a slave network device
401 - ``fixed_link_update``: Function invoked by the PHY library, and specifically by
455 - ``suspend``: function invoked by the DSA platform device when the system goes to
460 - ``resume``: function invoked by the DSA platform device when the system resumes,
[all …]
/kernel/linux/linux-4.19/Documentation/networking/dsa/
Ddsa.txt110 - receive function is invoked
136 -> invoked netif_receive_skb()
225 function hooks should be invoked, information about the directly attached switch
369 - probe: probe routine which will be invoked by the DSA platform device upon
397 - phy_read: Function invoked by the DSA slave MDIO bus when attempting to read
402 - phy_write: Function invoked by the DSA slave MDIO bus when attempting to write
406 - adjust_link: Function invoked by the PHY library when a slave network device
411 - fixed_link_update: Function invoked by the PHY library, and specifically by
465 - suspend: function invoked by the DSA platform device when the system goes to
470 - resume: function invoked by the DSA platform device when the system resumes,
[all …]
/kernel/linux/linux-5.10/drivers/crypto/qce/
Dcore.h26 * @async_req_enqueue: invoked by every algorithm to enqueue a request
27 * @async_req_done: invoked by every algorithm to finish its request
49 * @register_algs: invoked by core to register the algorithms
50 * @unregister_algs: invoked by core to unregister the algorithms
51 * @async_req_handle: invoked by core to handle enqueued request
/kernel/linux/linux-4.19/Documentation/scsi/
Dscsi_eh.txt60 scsi_finish_command() is invoked for the command. The
73 scsi_eh_scmd_add(scmd) is invoked for the command. See
95 2. scsi_abort_command() is invoked to schedule an asynchrous abort.
96 Asynchronous abort are not invoked for commands which the
101 3. scsi_eh_scmd_add(scmd, SCSI_EH_CANCEL_CMD) is invoked for the
110 Otherwise scsi_eh_scmd_add() is invoked for the command.
226 recovered (eh_work_q is empty), scsi_eh_flush_done_q() is invoked to
238 ACTION: scsi_eh_scmd_add() is invoked for scmd
251 ACTION: scsi_eh_finish_cmd() is invoked to EH-finish scmd
266 - otherwise, scsi_finish_command() is invoked for scmd
[all …]
/kernel/linux/linux-4.19/drivers/crypto/qce/
Dcore.h34 * @async_req_enqueue: invoked by every algorithm to enqueue a request
35 * @async_req_done: invoked by every algorithm to finish its request
57 * @register_algs: invoked by core to register the algorithms
58 * @unregister_algs: invoked by core to unregister the algorithms
59 * @async_req_handle: invoked by core to handle enqueued request
/kernel/linux/linux-5.10/Documentation/scsi/
Dscsi_eh.rst67 scsi_finish_command() is invoked for the command. The
83 scsi_eh_scmd_add(scmd) is invoked for the command. See
106 2. scsi_abort_command() is invoked to schedule an asynchrous abort.
107 Asynchronous abort are not invoked for commands which the
112 3. scsi_eh_scmd_add(scmd, SCSI_EH_CANCEL_CMD) is invoked for the
123 Otherwise scsi_eh_scmd_add() is invoked for the command.
245 recovered (eh_work_q is empty), scsi_eh_flush_done_q() is invoked to
259 :ACTION: scsi_eh_scmd_add() is invoked for scmd
277 :ACTION: scsi_eh_finish_cmd() is invoked to EH-finish scmd
297 - otherwise, scsi_finish_command() is invoked for scmd
[all …]
/kernel/linux/linux-4.19/Documentation/RCU/
Dlockdep.txt37 invoked by both RCU readers and updaters.
41 is invoked by both RCU-bh readers and updaters.
45 is invoked by both RCU-sched readers and updaters.
49 is invoked by both SRCU readers and updaters.
56 invoked only by updaters.
84 from taking place. If the above statement was invoked only from updater
DUP.txt28 This same problem can occur if call_rcu() is invoked from a hardware
55 Suppose that call_rcu() is invoked while holding a lock, and that the
72 It is far better to guarantee that callbacks are invoked
103 Therefore, the called function has been invoked within an RCU
117 then, since RCU callbacks can be invoked from softirq context,
/kernel/linux/linux-4.19/Documentation/core-api/
Dcpu_hotplug.rst153 hotplug states will be invoked, starting with ``CPUHP_ONLINE`` and terminating
178 will be invoked during registration on all online CPUs. If an error
180 invoked on all CPUs on which the online callback was previously invoked.
181 After registration completed, the *Y_online* callback will be invoked
182 once a CPU is brought online and *Y_prepare_down* will be invoked when a
192 During the removal of a hotplug state the teardown callback will be invoked.
219 should be invoked which will invoke the teardown callback on all online
238 * The states *CPUHP_OFFLINE* … *CPUHP_AP_OFFLINE* are invoked before the
240 * The states *CPUHP_AP_OFFLINE* … *CPUHP_AP_ONLINE* are invoked
243 the callbacks are invoked on the target CPU.
[all …]
/kernel/linux/linux-5.10/Documentation/core-api/
Dcpu_hotplug.rst146 hotplug states will be invoked, starting with ``CPUHP_ONLINE`` and terminating
171 will be invoked during registration on all online CPUs. If an error
173 invoked on all CPUs on which the online callback was previously invoked.
174 After registration completed, the *Y_online* callback will be invoked
175 once a CPU is brought online and *Y_prepare_down* will be invoked when a
185 During the removal of a hotplug state the teardown callback will be invoked.
212 should be invoked which will invoke the teardown callback on all online
231 * The states *CPUHP_OFFLINE* … *CPUHP_AP_OFFLINE* are invoked before the
233 * The states *CPUHP_AP_OFFLINE* … *CPUHP_AP_ONLINE* are invoked
236 the callbacks are invoked on the target CPU.
[all …]
/kernel/linux/linux-5.10/Documentation/RCU/
Dlockdep.rst41 invoked by both RCU readers and updaters.
45 is invoked by both RCU-bh readers and updaters.
49 is invoked by both RCU-sched readers and updaters.
53 is invoked by both SRCU readers and updaters.
60 invoked only by updaters.
88 from taking place. If the above statement was invoked only from updater
DUP.rst30 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
76 It is far better to guarantee that callbacks are invoked
110 Therefore, the called function has been invoked within an RCU
125 then, since RCU callbacks can be invoked from softirq context,
/kernel/linux/linux-5.10/drivers/net/fddi/skfp/h/
Dhwmtm.h202 * This macro may be invoked by the OS-specific module to read
216 * This macro may be invoked by the OS-specific module to read
232 * This macro may be invoked by the OS-specific module to get the
249 * This macro may be invoked by the OS-specific module to get the
268 * This macro may be invoked by the OS-specific module to read
285 * This macro may be invoked by the OS-specific module to read
301 * This macro may be invoked by the OS-specific module to get
318 * This macro may be invoked by the OS-specific module to get
332 * This macro may be invoked by the OS-specific module to get the
348 * This macro is invoked by the OS-specific before it left the
/kernel/linux/linux-4.19/drivers/net/fddi/skfp/h/
Dhwmtm.h206 * This macro may be invoked by the OS-specific module to read
220 * This macro may be invoked by the OS-specific module to read
236 * This macro may be invoked by the OS-specific module to get the
253 * This macro may be invoked by the OS-specific module to get the
272 * This macro may be invoked by the OS-specific module to read
289 * This macro may be invoked by the OS-specific module to read
305 * This macro may be invoked by the OS-specific module to get
322 * This macro may be invoked by the OS-specific module to get
336 * This macro may be invoked by the OS-specific module to get the
352 * This macro is invoked by the OS-specific before it left the
/kernel/liteos_m/components/lmk/
Dlos_lmk.h81 * Lmk error code: The registered free memory functions have been invoked.
99 * Lmk error code: No need to restore when no free memory functions have been invoked.
115 BOOL isMemFreed; /**< Flag that if LOS_LmkTasksKill has been invoked. */
182 * This function will be invoked by the developer as needed.
188 * @retval LOS_OK All the restore killed tasks functions are invoked successfully.
208 * @retval LOS_OK All the free memory functions are invoked successfully.
209 … @retval LOS_ERRNO_LMK_MEMORY_ALREADY_FREED The registered free memory functions have been invoked.
/kernel/linux/linux-4.19/drivers/pci/pcie/
Derr.c155 * Invoked when performing link reset on a Downstream Port or a
199 * Invoked during error recovery process. Once being invoked, the content
225 * Invoked when an error is fatal. Once being invoked, removes the devices
286 * Invoked when an error is nonfatal/fatal. Once being invoked, broadcast
/kernel/linux/linux-4.19/Documentation/virtual/kvm/
Dhalt-polling.txt16 invoked. Thus halt polling is especially useful on workloads with very short
46 received during the polling interval (and thus schedule is invoked) there are
71 invoked and a wakeup source received (irrespective of
72 whether the scheduler is invoked within that function).
126 schedule will be invoked to allow that other task to run. Thus this doesn't
/kernel/linux/linux-5.10/include/linux/regulator/
Dcoupler.h23 * @attach_regulator: Callback invoked on creation of a coupled regulator,
29 * @detach_regulator: Callback invoked on destruction of a coupled regulator.
31 * @balance_voltage: Callback invoked when voltage of a coupled regulator is
/kernel/linux/linux-5.10/drivers/crypto/caam/
Dqi.h29 * caam_qi_cbk - application's callback function invoked by the driver when the
136 * Invoked when shared descriptor is required to be change in driver context.
156 * Invoked when a user of the CAAM-QI (i.e. caamalg-qi) needs data which has
170 * Invoked when a user of the CAAM-QI (i.e. caamalg-qi) no longer needs
/kernel/linux/linux-5.10/Documentation/virt/kvm/
Dhalt-polling.rst19 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).
138 that cpu, otherwise the polling will cease immediately and schedule will be invoked to
/kernel/linux/linux-4.19/drivers/crypto/caam/
Dqi.h55 * caam_qi_cbk - application's callback function invoked by the driver when the
161 * Invoked when shared descriptor is required to be change in driver context.
182 * Invoked when a user of the CAAM-QI (i.e. caamalg-qi) needs data which has
196 * Invoked when a user of the CAAM-QI (i.e. caamalg-qi) no longer needs
/kernel/linux/linux-4.19/arch/mips/sgi-ip27/
DTODO11 being invoked on all nodes in ip27-memory.c.
12 8. Too many do_page_faults invoked - investigate.
/kernel/linux/linux-5.10/arch/mips/sgi-ip27/
DTODO11 being invoked on all nodes in ip27-memory.c.
12 8. Too many do_page_faults invoked - investigate.

12345678910>>...68