Home
last modified time | relevance | path

Searched refs:handlers (Results 1 – 125 of 125) sorted by relevance

/linux-4.4.14/fs/btrfs/
Dprops.c81 const struct hlist_head *handlers) in find_prop_handler() argument
85 if (!handlers) { in find_prop_handler()
88 handlers = find_prop_handlers_by_hash(hash); in find_prop_handler()
89 if (!handlers) in find_prop_handler()
93 hlist_for_each_entry(h, handlers, node) in find_prop_handler()
178 const struct hlist_head *handlers; in iterate_object_props() local
198 handlers = find_prop_handlers_by_hash(key.offset); in iterate_object_props()
199 if (!handlers) in iterate_object_props()
234 handler = find_prop_handler(name_buf, handlers); in iterate_object_props()
/linux-4.4.14/arch/powerpc/platforms/powermac/
Dpfunc_core.c123 #define PMF_PARSE_CALL(name, cmd, handlers, p...) \ argument
127 if (handlers == NULL) \
129 if (handlers->name) \
130 return handlers->name(cmd->func, cmd->instdata, \
541 struct pmf_handlers *handlers; member
579 struct pmf_handlers *handlers, in pmf_parse_one() argument
595 handlers ? "executing" : "parsing"); in pmf_parse_one()
620 rc = pmf_parsers[ccode](&cmd, handlers); in pmf_parse_one()
629 if (handlers == NULL) in pmf_parse_one()
701 struct pmf_handlers *handlers, in pmf_register_driver() argument
[all …]
/linux-4.4.14/drivers/net/wireless/iwlwifi/dvm/
Drx.c1028 void (**handlers)(struct iwl_priv *priv, struct iwl_rx_cmd_buffer *rxb); in iwl_setup_rx_handlers() local
1030 handlers = priv->rx_handlers; in iwl_setup_rx_handlers()
1032 handlers[REPLY_ERROR] = iwlagn_rx_reply_error; in iwl_setup_rx_handlers()
1033 handlers[CHANNEL_SWITCH_NOTIFICATION] = iwlagn_rx_csa; in iwl_setup_rx_handlers()
1034 handlers[SPECTRUM_MEASURE_NOTIFICATION] = in iwl_setup_rx_handlers()
1036 handlers[PM_SLEEP_NOTIFICATION] = iwlagn_rx_pm_sleep_notif; in iwl_setup_rx_handlers()
1037 handlers[PM_DEBUG_STATISTIC_NOTIFIC] = in iwl_setup_rx_handlers()
1039 handlers[BEACON_NOTIFICATION] = iwlagn_rx_beacon_notif; in iwl_setup_rx_handlers()
1040 handlers[REPLY_ADD_STA] = iwl_add_sta_callback; in iwl_setup_rx_handlers()
1042 handlers[REPLY_WIPAN_NOA_NOTIFICATION] = iwlagn_rx_noa_notification; in iwl_setup_rx_handlers()
[all …]
/linux-4.4.14/Documentation/ia64/
Dfsys.txt28 interruption-handlers start execution in. The user-level
79 The file arch/ia64/kernel/fsys.S contains a table of fsyscall-handlers
110 Fsyscall handlers can execute with very little overhead, but with that
113 o Fsyscall-handlers MUST check for any pending work in the flags
118 o Fsyscall-handlers MUST preserve incoming arguments (r32-r39, r11,
123 o Fsyscall-handlers MUST check argument registers for containing a
129 o Fsyscall-handlers MUST NOT use the "alloc" instruction or perform
133 o Fsyscall-handlers MUST NOT write to any stacked registers because
137 o Fsyscall-handlers need to be careful when accessing per-CPU variables:
142 o Fsyscall-handlers must be careful not to leak sensitive kernel'
[all …]
Dmca.txt35 handlers cannot rely on the thread pointer, PAL physical mode can
44 Because the MCA/INIT handlers cannot trust the kernel stack, they
46 preformatted with just enough task state to let the relevant handlers
81 requires set_curr_task() so the MCA/INIT handlers can register their
91 stacks meant separate "tasks" for the MCA/INIT handlers.
98 slaves. All the OS INIT handlers are entered at approximately the same
184 handlers have _TIF_MCA_INIT set in thread_info.flags.
/linux-4.4.14/drivers/net/ethernet/chelsio/cxgb3/
Dcxgb3_offload.c747 t3c_tid->client->handlers && in do_act_open_rpl()
748 t3c_tid->client->handlers[CPL_ACT_OPEN_RPL]) { in do_act_open_rpl()
749 return t3c_tid->client->handlers[CPL_ACT_OPEN_RPL] (dev, skb, in do_act_open_rpl()
766 if (t3c_tid && t3c_tid->ctx && t3c_tid->client->handlers && in do_stid_rpl()
767 t3c_tid->client->handlers[p->opcode]) { in do_stid_rpl()
768 return t3c_tid->client->handlers[p->opcode] (dev, skb, in do_stid_rpl()
784 if (t3c_tid && t3c_tid->ctx && t3c_tid->client->handlers && in do_hwtid_rpl()
785 t3c_tid->client->handlers[p->opcode]) { in do_hwtid_rpl()
786 return t3c_tid->client->handlers[p->opcode] in do_hwtid_rpl()
811 if (t3c_tid && t3c_tid->ctx && t3c_tid->client->handlers && in do_cr()
[all …]
Dcxgb3_offload.h86 cxgb3_cpl_handler_func *handlers; member
/linux-4.4.14/drivers/char/ipmi/
Dipmi_si_intf.c166 const struct si_sm_handlers *handlers; member
402 err = smi_info->handlers->start_transaction( in start_next_msg()
433 smi_info->handlers->start_transaction(smi_info->si_sm, msg, size); in start_new_msg()
446 smi_info->handlers->start_transaction(smi_info->si_sm, msg, 2); in start_check_enables()
462 smi_info->handlers->start_transaction(smi_info->si_sm, msg, 3); in start_clear_flags()
627 = smi_info->handlers->get_result( in handle_transaction_done()
648 len = smi_info->handlers->get_result(smi_info->si_sm, msg, 4); in handle_transaction_done()
670 smi_info->handlers->get_result(smi_info->si_sm, msg, 3); in handle_transaction_done()
683 = smi_info->handlers->get_result( in handle_transaction_done()
721 = smi_info->handlers->get_result( in handle_transaction_done()
[all …]
Dipmi_msghandler.c345 const struct ipmi_smi_handlers *handlers; member
980 if (!try_module_get(intf->handlers->owner)) { in ipmi_create_user()
985 if (intf->handlers->inc_usecount) { in ipmi_create_user()
986 rv = intf->handlers->inc_usecount(intf->send_info); in ipmi_create_user()
988 module_put(intf->handlers->owner); in ipmi_create_user()
1024 const struct ipmi_smi_handlers *handlers; in ipmi_get_smi_info() local
1037 handlers = intf->handlers; in ipmi_get_smi_info()
1039 if (handlers->get_smi_info) in ipmi_get_smi_info()
1040 rv = handlers->get_smi_info(intf->send_info, data); in ipmi_get_smi_info()
1105 if (intf->handlers) { in ipmi_destroy_user()
[all …]
Dipmi_ssif.c205 struct ipmi_smi_handlers handlers; member
1631 ssif_info->handlers.owner = THIS_MODULE; in ssif_probe()
1632 ssif_info->handlers.start_processing = ssif_start_processing; in ssif_probe()
1633 ssif_info->handlers.get_smi_info = get_smi_info; in ssif_probe()
1634 ssif_info->handlers.sender = sender; in ssif_probe()
1635 ssif_info->handlers.request_events = request_events; in ssif_probe()
1636 ssif_info->handlers.inc_usecount = inc_usecount; in ssif_probe()
1637 ssif_info->handlers.dec_usecount = dec_usecount; in ssif_probe()
1656 rv = ipmi_register_smi(&ssif_info->handlers, in ssif_probe()
/linux-4.4.14/Documentation/acpi/
Dscan_handlers.txt33 called ACPI scan handlers represented by the following structure:
43 take care of, list_node is the hook to the global list of ACPI scan handlers
51 available scan handlers. If a matching scan handler is found, its .attach()
66 callbacks from the scan handlers of all device nodes in the given namespace
67 scope (if they have scan handlers). Next, it unregisters all of the device
70 ACPI scan handlers can be added to the list maintained by the ACPI core with the
72 handler as an argument. The order in which scan handlers are added to the list
/linux-4.4.14/Documentation/trace/
Devents-nmi.txt12 NMI handlers are hogging large amounts of CPU time. The kernel
13 will warn if it sees long-running handlers:
/linux-4.4.14/Documentation/RCU/
DNMI-RCU.txt6 handlers, as well as dynamic irq handlers. This document describes
93 Since NMI handlers disable preemption, synchronize_sched() is guaranteed
94 not to return until all ongoing NMI handlers exit. It is therefore safe
Dstallwarn.txt125 handlers that the stalled CPU has executed. The number before the "/"
133 handlers are no longer able to execute on this CPU. This can happen if
Dchecklist.txt326 If you want to wait for interrupt handlers, NMI handlers, and
DwhatisRCU.txt904 c. Do you need to treat NMI handlers, hardirq handlers,
956 become blocking locks, and all irq handlers execute in
/linux-4.4.14/fs/
Dxattr.c686 #define for_each_xattr_handler(handlers, handler) \ argument
687 for ((handler) = *(handlers)++; \
689 (handler) = *(handlers)++)
695 xattr_resolve_name(const struct xattr_handler **handlers, const char **name) in xattr_resolve_name() argument
702 for_each_xattr_handler(handlers, handler) { in xattr_resolve_name()
733 const struct xattr_handler *handler, **handlers = dentry->d_sb->s_xattr; in generic_listxattr() local
737 for_each_xattr_handler(handlers, handler) { in generic_listxattr()
744 for_each_xattr_handler(handlers, handler) { in generic_listxattr()
/linux-4.4.14/net/wireless/
Dwext-core.c685 const struct iw_handler_def *handlers = NULL; in get_handler() local
689 handlers = dev->ieee80211_ptr->wiphy->wext; in get_handler()
693 handlers = dev->wireless_handlers; in get_handler()
696 if (!handlers) in get_handler()
701 if (index < handlers->num_standard) in get_handler()
702 return handlers->standard[index]; in get_handler()
707 if (index < handlers->num_private) in get_handler()
708 return handlers->private[index]; in get_handler()
/linux-4.4.14/Documentation/power/
Dsuspend-and-interrupts.txt19 interrupt handlers for shared IRQs that device drivers implementing them were
49 user of it. Thus, if the IRQ is shared, all of the interrupt handlers installed
88 already suspended. However, after suspend_device_irqs() interrupt handlers are
120 interrupts (interrupt handlers are invoked after suspend_device_irqs()) are
122 handlers are not invoked after suspend_device_irqs()).
125 to individual interrupt handlers, so sharing an IRQ between a system wakeup
Ddevices.txt277 unfrozen. Furthermore, the *_noirq phases run at a time when IRQ handlers have
361 4. The suspend_noirq phase occurs after IRQ handlers have been disabled,
399 before the driver's interrupt handlers are invoked. This generally
Dpci.txt515 when their interrupt handlers are invoked for the first time during resume,
881 after the PM core has enabled device drivers' interrupt handlers to be invoked.
/linux-4.4.14/arch/um/os-Linux/
Dsignal.c129 static void (*handlers[_NSIG])(int sig, struct siginfo *si, mcontext_t *mc) = { variable
170 (*handlers[sig])(sig, (struct siginfo *)si, mc); in hard_handler()
/linux-4.4.14/drivers/xen/
Dmanage.c215 static struct shutdown_handler handlers[] = { in shutdown_handler() local
241 for (handler = &handlers[0]; handler->command; handler++) { in shutdown_handler()
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-restart.txt18 restart handler completes allowing other restart handlers to be attempted.
39 restart handlers
/linux-4.4.14/include/linux/
Dntb_transport.h76 const struct ntb_queue_handlers *handlers);
Dipmi_smi.h215 int ipmi_register_smi(const struct ipmi_smi_handlers *handlers,
/linux-4.4.14/fs/reiserfs/
Dxattr.c743 #define for_each_xattr_handler(handlers, handler) \ argument
744 for ((handler) = *(handlers)++; \
746 (handler) = *(handlers)++)
750 find_xattr_handler_prefix(const struct xattr_handler **handlers, in find_xattr_handler_prefix() argument
755 if (!handlers) in find_xattr_handler_prefix()
758 for_each_xattr_handler(handlers, xah) { in find_xattr_handler_prefix()
/linux-4.4.14/arch/mips/sgi-ip27/
DTODO16 11. All intrs (ip27_do_irq handlers) are targeted at cpu A on the node.
DKconfig44 Say Y here to enable replicating the kernel exception handlers
/linux-4.4.14/Documentation/security/
DYama.txt36 between a debugging process and its inferior (crash handlers, etc),
41 Firefox's crash handlers, and by Wine for allowing only Wine processes
/linux-4.4.14/Documentation/
Dkprobes.txt158 data between corresponding user entry and return handlers. The size of each
209 - a call to the trampoline code which calls user's probe handlers.
330 the associated probe handlers that you'll write. See the files in the
343 kp->fault_handler. Any or all handlers can be NULL. If kp->flags
345 so, its handlers aren't hit until calling enable_kprobe(kp).
526 In particular, you can probe interrupt handlers. Known exceptions
547 Kprobes makes no attempt to prevent probe handlers from stepping on
550 handlers won't be run in that instance, and the kprobe.nmissed member
553 As of Linux v2.6.15-rc1, multiple handlers (or multiple instances of
559 Probe handlers are run with preemption disabled. Depending on the
[all …]
Dremoteproc.txt20 handlers, and then all rpmsg drivers will then just work
92 name of this remote processor, platform-specific ops handlers,
151 * struct rproc_ops - platform-specific device handlers
163 handlers. If rpmsg/virtio functionality is also desired, then the ->kick handler
Dunshare.txt269 signal handlers, for which unsharing is not implemented
289 signals and signal handlers. Signals are complex to begin with and
290 to unshare signals and/or signal handlers of a currently running
292 need to allow unsharing of signals and/or signal handlers, it can
Dlocal_ops.txt26 require disabling interrupts to protect from interrupt handlers and it permits
27 coherent counters in NMI handlers. It is especially useful for tracing purposes
DIRQ-domain.txt14 handlers as irqchips, i.e. in effect cascading interrupt controllers.
Dhwspinlock.txt265 * @ops: platform-specific hwspinlock handlers
Dkernel-per-CPU-kthreads.txt65 Purpose: Execute softirq handlers when threaded or when under heavy load.
Dkernel-docs.txt285 interrupt handlers .
Dkernel-parameters.txt1633 When an interrupt is not handled search all handlers
1638 When an interrupt is not handled search all handlers
1639 for it. Also check all handlers each timer
3714 Force threading of all interrupt handlers except those
/linux-4.4.14/drivers/pinctrl/samsung/
Dpinctrl-s3c24xx.c484 irq_flow_handler_t *handlers; in s3c24xx_eint_init() local
503 handlers = eint0_3_parent_only ? s3c2410_eint_handlers in s3c24xx_eint_init()
515 irq_set_chained_handler_and_data(irq, handlers[i], eint_data); in s3c24xx_eint_init()
/linux-4.4.14/arch/m68k/fpsp040/
Dx_store.S6 | Used by underflow and overflow handlers.
54 | handlers restore fp0-fp3 from there.
Dfpsp.h16 | All FPSP handlers begin by executing:
48 | On exit, the handlers execute:
59 | type that was generated. Some handlers may omit the "frestore"
Dres_func.S1460 | handlers.
1478 | handlers.
/linux-4.4.14/arch/mips/kvm/
D00README.txt24 …nux-3.7-rc2 based SMP guest hangs due to the following code sequence in the generated TLB handlers:
Dlocore.S621 ##### The exception handlers.
/linux-4.4.14/drivers/media/radio/wl128x/
Dfmdrv.h119 int_handler_prototype *handlers; member
Dfmdrv_common.c183 fmdev->irq_info.handlers[fmdev->irq_info.stage](fmdev); in fm_irq_call()
298 irq_info->handlers[irq_info->stage](fmdev); in recv_tasklet()
325 irq_info->handlers[irq_info->stage](fmdev); in recv_tasklet()
1052 fmdev->irq_info.handlers[fmdev->irq_info.stage](fmdev); in fm_irq_handle_intmsk_cmd_resp()
1653 fmdev->irq_info.handlers = int_handler_table; in fm_drv_init()
/linux-4.4.14/Documentation/arm64/
Dtagged-pointers.txt22 This means that signal handlers in applications making use
/linux-4.4.14/arch/m68k/ifpsp060/
Dfpsp.doc33 Package. This package is essentially a set of exception handlers
35 These exception handlers emulate Unimplemented FP instructions,
38 includes exception handlers to provide full IEEE-754 compliant
/linux-4.4.14/drivers/net/wireless/iwlegacy/
D3945-mac.c845 il->handlers[N_ALIVE] = il3945_hdl_alive; in il3945_setup_handlers()
846 il->handlers[C_ADD_STA] = il3945_hdl_add_sta; in il3945_setup_handlers()
847 il->handlers[N_ERROR] = il_hdl_error; in il3945_setup_handlers()
848 il->handlers[N_CHANNEL_SWITCH] = il_hdl_csa; in il3945_setup_handlers()
849 il->handlers[N_SPECTRUM_MEASUREMENT] = il_hdl_spectrum_measurement; in il3945_setup_handlers()
850 il->handlers[N_PM_SLEEP] = il_hdl_pm_sleep; in il3945_setup_handlers()
851 il->handlers[N_PM_DEBUG_STATS] = il_hdl_pm_debug_stats; in il3945_setup_handlers()
852 il->handlers[N_BEACON] = il3945_hdl_beacon; in il3945_setup_handlers()
859 il->handlers[C_STATS] = il3945_hdl_c_stats; in il3945_setup_handlers()
860 il->handlers[N_STATS] = il3945_hdl_stats; in il3945_setup_handlers()
[all …]
D4965-mac.c4187 il->handlers[N_ALIVE] = il4965_hdl_alive; in il4965_setup_handlers()
4188 il->handlers[N_ERROR] = il_hdl_error; in il4965_setup_handlers()
4189 il->handlers[N_CHANNEL_SWITCH] = il_hdl_csa; in il4965_setup_handlers()
4190 il->handlers[N_SPECTRUM_MEASUREMENT] = il_hdl_spectrum_measurement; in il4965_setup_handlers()
4191 il->handlers[N_PM_SLEEP] = il_hdl_pm_sleep; in il4965_setup_handlers()
4192 il->handlers[N_PM_DEBUG_STATS] = il_hdl_pm_debug_stats; in il4965_setup_handlers()
4193 il->handlers[N_BEACON] = il4965_hdl_beacon; in il4965_setup_handlers()
4200 il->handlers[C_STATS] = il4965_hdl_c_stats; in il4965_setup_handlers()
4201 il->handlers[N_STATS] = il4965_hdl_stats; in il4965_setup_handlers()
4206 il->handlers[N_CARD_STATE] = il4965_hdl_card_state; in il4965_setup_handlers()
[all …]
Ddebug.c725 if (il->isr_stats.handlers[cnt] > 0) in il_dbgfs_interrupt_read()
730 il->isr_stats.handlers[cnt]); in il_dbgfs_interrupt_read()
D3945.c2465 il->handlers[C_TX] = il3945_hdl_tx; in il3945_hw_handler_setup()
2466 il->handlers[N_3945_RX] = il3945_hdl_rx; in il3945_hw_handler_setup()
Dcommon.h1030 u32 handlers[IL_CN_MAX]; member
1147 void (*handlers[IL_CN_MAX]) (struct il_priv *il, member
Dcommon.c1472 il->handlers[C_SCAN] = il_hdl_scan; in il_setup_rx_scan_handlers()
1473 il->handlers[N_SCAN_START] = il_hdl_scan_start; in il_setup_rx_scan_handlers()
1474 il->handlers[N_SCAN_RESULTS] = il_hdl_scan_results; in il_setup_rx_scan_handlers()
1475 il->handlers[N_SCAN_COMPLETE] = il_hdl_scan_complete; in il_setup_rx_scan_handlers()
/linux-4.4.14/Documentation/gpio/
Ddriver.txt68 on -RT (inside hard IRQ handlers and similar contexts). Normally this should
108 RT_FULL: Note, chained IRQ handlers will not be forced threaded on -RT.
127 but chained IRQ handlers are not used. Instead GPIO IRQs dispatching is
136 RT_FULL: Such kind of handlers will be forced threaded on -RT, as result IRQ
180 - Nominally set all handlers to handle_bad_irq() in the setup call and pass
Dconsumer.txt176 handlers and similar contexts.
200 sleeping, which can't be done from inside IRQ handlers.
217 that can't be accessed from hardIRQ handlers, these calls act the same as the
Dgpio-legacy.txt164 (nonthreaded) IRQ handlers and similar contexts.
200 This requires sleeping, which can't be done from inside IRQ handlers.
222 on GPIOs that can't be accessed from hardIRQ handlers, these calls act
/linux-4.4.14/drivers/mfd/
Dmenelaus.c177 void (*handlers[16])(struct menelaus_chip *); member
249 the_menelaus->handlers[irq] = handler; in menelaus_add_irq_work()
263 the_menelaus->handlers[irq] = NULL; in menelaus_remove_irq_work()
796 handler = menelaus->handlers[irq]; in menelaus_work()
/linux-4.4.14/Documentation/powerpc/
Dtransactional_memory.txt119 However, basic signal handlers don't need to be aware of transactions
122 Transaction-aware signal handlers can read the transactional register state
123 from the second ucontext. This will be necessary for crash handlers to
Dqe_firmware.txt75 3) The TIBCR trap registers are loaded with the addresses of the trap handlers
/linux-4.4.14/Documentation/parisc/
Ddebugging33 registers interruption handlers read to find out where the machine
Dregisters85 (GR) saves and restores in interruption handlers.
/linux-4.4.14/arch/cris/arch-v32/lib/
Dchecksumcopy.S50 ;; r12 <= acr is needed after mloop and in the exception handlers.
/linux-4.4.14/drivers/nubus/
Dproc.c64 #warning Need to set some I/O handlers here
/linux-4.4.14/Documentation/usb/
Derror-codes.txt72 USB device drivers may only test urb status values in completion handlers.
83 flag is set. Completion handlers for isochronous URBs should only see
DURB.txt143 For isochronous endpoints, your completion handlers should (re)submit
215 In the current kernel, completion handlers run with local interrupts
217 local IRQs are always disabled inside completion handlers.
/linux-4.4.14/arch/powerpc/include/asm/
Dpmac_pfunc.h178 struct pmf_handlers *handlers,
/linux-4.4.14/Documentation/arm/
DInterrupts100 The handler can be one of the 3 standard handlers - "level", "edge" and
131 enables this IRQ (eg, Neponset and SA1111 handlers).
Dtcm.txt50 - FIQ and other interrupt handlers that need deterministic
/linux-4.4.14/drivers/infiniband/hw/cxgb3/
Diwch.c58 .handlers = t3c_handlers,
/linux-4.4.14/Documentation/input/
Dinput.txt46 1.2 Event handlers
154 3.2 Event handlers
156 Event handlers distribute the events from the devices to userland and
/linux-4.4.14/Documentation/fb/
Ddeferred_io.txt10 - deferred IO and driver sets up fault and page_mkwrite handlers
/linux-4.4.14/Documentation/infiniband/
Dcore_locking.txt76 completion event handlers for the same CQ are not called
/linux-4.4.14/arch/powerpc/platforms/pseries/
DKconfig69 event types and scopes. Device drivers can register their handlers
/linux-4.4.14/drivers/hid/
Dhid-wiimote-core.c1582 static struct wiiproto_handler handlers[] = { variable
1623 for (i = 0; handlers[i].id; ++i) { in wiimote_hid_event()
1624 h = &handlers[i]; in wiimote_hid_event()
1631 if (!handlers[i].id) in wiimote_hid_event()
/linux-4.4.14/Documentation/filesystems/
Ddax.txt64 include handlers for fault, pmd_fault and page_mkwrite (which should
Dfiemap.txt199 structure directly. Filesystem handlers should be tolerant to signals and return
Dproc.txt988 Provides counts of softirq handlers serviced since boot time, for each cpu.
/linux-4.4.14/arch/cris/arch-v32/mm/
Dmmu.S201 ; This is the MMU bus fault handlers.
/linux-4.4.14/drivers/ntb/
Dntb_transport.c1607 const struct ntb_queue_handlers *handlers) in ntb_transport_create_queue() argument
1639 qp->rx_handler = handlers->rx_handler; in ntb_transport_create_queue()
1640 qp->tx_handler = handlers->tx_handler; in ntb_transport_create_queue()
1641 qp->event_handler = handlers->event_handler; in ntb_transport_create_queue()
/linux-4.4.14/Documentation/target/
Dtcm_mod_builder.txt21 the TransportID / Initiator and Target WWPN related handlers for
Dtcmu-design.txt268 devices separately. All handlers should make sure to only open their
/linux-4.4.14/arch/sh/kernel/cpu/sh3/
Dentry.S494 mov r15, r8 ! trap handlers take saved regs in r8
/linux-4.4.14/drivers/remoteproc/
Dremoteproc_core.c711 rproc_handle_resource_t handlers[RSC_LAST]) in rproc_handle_resources()
736 handler = handlers[hdr->type]; in rproc_handle_resources()
/linux-4.4.14/drivers/edac/
Dedac_mc.c669 int handlers = atomic_dec_return(&edac_handlers); in del_mc_from_global_list() local
678 return handlers; in del_mc_from_global_list()
/linux-4.4.14/arch/cris/arch-v10/kernel/
Dentry.S334 ;; from the other interrupt handlers.
417 ;; special handlers for breakpoint and NMI
/linux-4.4.14/Documentation/video4linux/
Dv4l2-controls.txt38 controls, possibly to controls owned by other handlers.
366 the value of controls owned by other handlers, then you have to be very careful
613 all video nodes. But you can also specify different control handlers for
652 What you should not do is make two identical controls for two handlers.
/linux-4.4.14/tools/perf/Documentation/
Dperf-script-python.txt119 # perf script event handlers, generated by perf script -g python
175 more info on event handlers).
484 arguments passed to all event handlers; some of the fields correspond
Dperf-script-perl.txt88 arguments passed to all event handlers; some of the fields correspond
/linux-4.4.14/net/bluetooth/
Dhci_sock.c1079 chan->handlers[opcode].func == NULL) { in hci_mgmt_cmd()
1086 handler = &chan->handlers[opcode]; in hci_mgmt_cmd()
Dmgmt.c8645 .handlers = mgmt_handlers,
/linux-4.4.14/tools/lib/traceevent/
Devent-parse.c5809 for (next = &pevent->handlers; *next; in find_event_handle()
6489 handle->next = pevent->handlers; in pevent_register_event_handler()
6490 pevent->handlers = handle; in pevent_register_event_handler()
6553 for (next = &pevent->handlers; *next; next = &(*next)->next) { in pevent_unregister_event_handler()
6701 while (pevent->handlers) { in pevent_free()
6702 handle = pevent->handlers; in pevent_free()
6703 pevent->handlers = handle->next; in pevent_free()
Devent-parse.h528 struct event_handler *handlers; member
/linux-4.4.14/Documentation/spi/
Dspidev20 they need to access kernel interfaces (such as IRQ handlers or other layers
Dspi-summary591 execution contexts like IRQ handlers, tasklets, or workqueues (such
/linux-4.4.14/Documentation/locking/
Dspinlocks.txt101 never used in interrupt handlers, you can use the non-irq versions:
/linux-4.4.14/net/mac80211/
DKconfig121 bool "Do not inline TX/RX handlers"
/linux-4.4.14/Documentation/isdn/
DREADME.hysdn52 handlers for various protocols like ppp and others as well as config info
/linux-4.4.14/arch/blackfin/
DKconfig.debug184 bool "Turn off hwtrace in CPLB handlers"
/linux-4.4.14/arch/arm/kernel/
Dentry-armv.S126 @ common_invalid - generic code for failed exception (re-entrant version of handlers)
/linux-4.4.14/Documentation/s390/
Ddriver-model.txt185 distinct handlers (e.g. multi subchannel devices), this is a member of ccw_device
Dcds.txt51 * The interrupt handlers must be adapted to use a ccw_device as argument.
/linux-4.4.14/tools/perf/
Dbuiltin-sched.c1520 const struct perf_evsel_str_handler handlers[] = { in perf_sched__read_events() local
1543 if (perf_session__set_tracepoints_handlers(session, handlers)) in perf_sched__read_events()
Dbuiltin-trace.c2736 const struct perf_evsel_str_handler handlers[] = { in trace__replay() local
2773 err = perf_session__set_tracepoints_handlers(session, handlers); in trace__replay()
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-cd.1994-200459 * Fix race condition in setting up interrupt handlers
/linux-4.4.14/Documentation/x86/
Dmtrr.txt18 MTRRs is through the use of SMI handlers, one case could be for fan control,
/linux-4.4.14/Documentation/sysctl/
Dfs.txt129 handlers. This value should be 3-4 times larger than the value
/linux-4.4.14/Documentation/PCI/
Dpci.txt367 All interrupt handlers for IRQ lines should be registered with IRQF_SHARED
395 two (or more) interrupt handlers: one for MSI/MSI-X and another for IRQs.
/linux-4.4.14/Documentation/networking/
Drds.txt260 CM event handlers, and other Infiniband details.
Dfilter.txt589 in the eBPF interpreter. For in-kernel handlers, this all works transparently
/linux-4.4.14/Documentation/timers/
Dhighres.txt112 architecture specific timer interrupt handlers and hands the control over the
/linux-4.4.14/arch/unicore32/kernel/
Dentry.S230 @ (re-entrant version of handlers)
/linux-4.4.14/Documentation/vm/
Dunevictable-lru.txt277 (1) in the mlock()/mlockall() system call handlers;
310 Both [do_]mlock() and [do_]mlockall() system call handlers call mlock_fixup()
/linux-4.4.14/drivers/power/
DKconfig321 handlers.
/linux-4.4.14/arch/
DKconfig432 the slow path using TIF_NOHZ flag. Exceptions handlers must be
/linux-4.4.14/drivers/scsi/cxgbi/cxgb3i/
Dcxgb3i.c77 .handlers = cxgb3i_cpl_handlers,
/linux-4.4.14/include/net/bluetooth/
Dhci_core.h1404 const struct hci_mgmt_handler *handlers; member
/linux-4.4.14/drivers/message/fusion/
Dmptbase.c7711 int handlers = 0; in ProcessEventNotification() local
7784 handlers++; in ProcessEventNotification()
7801 *evHandlers = handlers; in ProcessEventNotification()
/linux-4.4.14/Documentation/scsi/
DChangeLog.lpfc113 * Removed TXQ from all abort and reset handlers since it is never
196 * Following timeout handlers moved to the lpfc worker thread:
569 * Have lpfc eh handlers, bus_reset and lun_reset, wait for all
DChangeLog.1992-1997439 - Change all interrupt handlers to accept new calling convention.
/linux-4.4.14/Documentation/virtual/kvm/
Dapi.txt3583 consists of those hcalls for which in-kernel handlers were implemented
3629 This capability allows post-handlers for the STSI instruction. After
3633 Before exiting to userspace, kvm handlers should fill in s390_stsi field of
3650 KVM handlers should exit to userspace with rc = -EREMOTE.
/linux-4.4.14/Documentation/cgroups/
Dcpusets.txt242 interrupt handlers, is allowed to be taken outside even a
/linux-4.4.14/lib/
DKconfig.debug680 bool "Debug shared IRQ handlers"
/linux-4.4.14/
DCREDITS675 D: Originator of design for new combined interrupt handlers