invoked (full) in projects: linux-5.10 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

12 3 4 5 6 7 8 9 10 >>...36

/linux-5.10/include/linux/
D	entry-common.h	82 * 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 …]
D	rpmsg.h	`81 * the rpmsg channel), the driver's handler is invoked to process it. 102 * @probe: invoked when a matching rpmsg channel (i.e. device) is found 103 * @remove: invoked when the rpmsg channel is removed 104 * @callback: invoked when an inbound message is received on the channel`
D	entry-kvm.h	`26 * Invoked from xfer_to_guest_mode_handle_work(). Defaults to NOOP. Can be 70 * Has to be invoked with interrupts disabled before the transition to`
D	seqlock.h	48 * If readers can be invoked from hardirq or softirq contexts, 526 * non-preemptible. If readers can be invoked from hardirq or softirq 883 * sections, can be invoked from hardirq or softirq contexts, use the 910 * other write side sections, can be invoked from softirq contexts. 937 * other write sections, can be invoked from hardirq contexts. 975 * section, or other write sections, can be invoked from hardirq context. 1007 * be invoked from hardirq or softirq contexts, use the _irqsave or _bh 1032 * seqlock_t write side section, or other read sections, can be invoked 1056 * write side section, or other read sections, can be invoked from a 1090 * write side section, or other read sections, can be invoked from a [all …]
/linux-5.10/tools/testing/selftests/bpf/prog_tests/
D	tcp_rtt.c	`7 __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()`
/linux-5.10/Documentation/networking/dsa/
D	dsa.rst	109 - 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 …]
/linux-5.10/drivers/crypto/qce/
D	core.h	`26 * @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`
/linux-5.10/Documentation/scsi/
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 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 …]
D	scsi_mid_low_api.rst	171 remove() callback being invoked. In either case, the sequence is the 376 * Notes: Can be invoked any time on a SCSI device controlled by this 378 * slave_destroy().] Can safely be invoked from interrupt code. 509 * lead to the slave_destroy() callback being invoked. sdev is an 525 * Notes: Should only be invoked if the "hotplug initialization 612 * Notes: Should not be invoked if the "hotplug initialization 732 * will be invoked from scsi_eh thread. No other commands 752 * Notes: Invoked from scsi_eh thread. No other commands will be 770 * Notes: Invoked from scsi_eh thread. No other commands will be 788 * Notes: Invoked from scsi_eh thread. No other commands will be [all …]
/linux-5.10/Documentation/core-api/
D	cpu_hotplug.rst	146 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 …]
/linux-5.10/drivers/net/fddi/skfp/h/
D	hwmtm.h	202 * 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
/linux-5.10/Documentation/RCU/
D	lockdep.rst	`41 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`
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 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,`
/linux-5.10/include/linux/regulator/
D	coupler.h	`23 * @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`
/linux-5.10/Documentation/virt/kvm/
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). 138 that cpu, otherwise the polling will cease immediately and schedule will be invoked to`
/linux-5.10/drivers/crypto/caam/
D	qi.h	`29 * 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`
/linux-5.10/arch/mips/sgi-ip27/
D	TODO	`11 being invoked on all nodes in ip27-memory.c. 12 8. Too many do_page_faults invoked - investigate.`
/linux-5.10/tools/testing/selftests/bpf/progs/
D	tcp_rtt.c	`9 __u32 invoked; member 52 storage->invoked++; in _sockops()`
/linux-5.10/tools/testing/selftests/rseq/
D	rseq.h	`123 * does not need to be invoked. 150 * rseq_prepare_unload() should be invoked by each thread executing a rseq 155 * generated by JIT: rseq_prepare_unload() should be invoked at least once by`
/linux-5.10/Documentation/admin-guide/pm/
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 397 invoking its utilization update callback for that CPU. If it is invoked by the 400 if it is invoked by the CFS scheduling class, the governor will use the [all …]
/linux-5.10/drivers/media/platform/mtk-vcodec/
D	vdec_vpu_if.h	`46 * vpu_dec_start - start decoding, basically the function will be invoked once 56 * vpu_dec_end - end decoding, basically the function will be invoked once`
/linux-5.10/include/uapi/linux/
D	nitro_enclaves.h	`19 * The ioctl can be invoked on the /dev/nitro_enclaves fd, before 58 * The ioctl can be invoked on the enclave fd, before an enclave 93 * The ioctl can be invoked on the enclave fd, before 116 * The ioctl can be invoked on the enclave fd, 158 * The ioctl can be invoked on the enclave fd, after an`
/linux-5.10/Documentation/driver-api/pm/
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-5.10/include/drm/
D	drm_bridge.h	61 * This callback is invoked whenever our bridge is being attached to a 77 * This callback is invoked whenever our bridge is being detached from a 280 * Note that this function will only be invoked in the context of an 281 * atomic commit. It will not be invoked from 306 * Note that this function will only be invoked in the context of an 307 * atomic commit. It will not be invoked from &drm_bridge_chain_enable. 328 * Note that this function will only be invoked in the context of an 329 * atomic commit. It will not be invoked from 353 * Note that this function will only be invoked in the context of an 354 * atomic commit. It will not be invoked from
/linux-5.10/drivers/pci/hotplug/
D	TODO	`65 removed and its functions invoked directly? This has already been done in 69 * The ->get_mode1_ECC_cap callback in shpchp_hpc_ops is never invoked.`

12 3 4 5 6 7 8 9 10 >>...36