Home
last modified time | relevance | path

Searched refs:callbacks (Results 1 – 25 of 348) sorted by relevance

12345678910>>...14

/openbmc/linux/kernel/livepatch/
H A Dcore.h30 if (obj->callbacks.pre_patch) in klp_pre_patch_callback()
31 ret = (*obj->callbacks.pre_patch)(obj); in klp_pre_patch_callback()
33 obj->callbacks.post_unpatch_enabled = !ret; in klp_pre_patch_callback()
40 if (obj->callbacks.post_patch) in klp_post_patch_callback()
41 (*obj->callbacks.post_patch)(obj); in klp_post_patch_callback()
46 if (obj->callbacks.pre_unpatch) in klp_pre_unpatch_callback()
47 (*obj->callbacks.pre_unpatch)(obj); in klp_pre_unpatch_callback()
52 if (obj->callbacks.post_unpatch_enabled && in klp_post_unpatch_callback()
53 obj->callbacks.post_unpatch) in klp_post_unpatch_callback()
54 (*obj->callbacks.post_unpatch)(obj); in klp_post_unpatch_callback()
[all …]
/openbmc/linux/Documentation/driver-api/usb/
H A Dcallbacks.rst1 USB core callbacks
4 What callbacks will usbcore do?
7 Usbcore will call into a driver through callbacks defined in the driver
10 callbacks are completely independent of each other. Information on the
13 The callbacks defined in the driver structure are:
15 1. Hotplugging callbacks:
34 3. Power management (PM) callbacks:
55 reason. Sysfs is preferred these days. The PM callbacks are covered
61 All callbacks are mutually exclusive. There's no need for locking
62 against other USB callbacks. All callbacks are called from a task
[all …]
/openbmc/linux/sound/drivers/opl3/
H A Dopl3_seq.c163 struct snd_seq_port_callback callbacks; in snd_opl3_synth_create_port() local
174 memset(&callbacks, 0, sizeof(callbacks)); in snd_opl3_synth_create_port()
175 callbacks.owner = THIS_MODULE; in snd_opl3_synth_create_port()
176 callbacks.use = snd_opl3_synth_use; in snd_opl3_synth_create_port()
177 callbacks.unuse = snd_opl3_synth_unuse; in snd_opl3_synth_create_port()
178 callbacks.event_input = snd_opl3_synth_event_input; in snd_opl3_synth_create_port()
179 callbacks.private_free = snd_opl3_synth_free_port; in snd_opl3_synth_create_port()
180 callbacks.private_data = opl3; in snd_opl3_synth_create_port()
186 opl3->chset->port = snd_seq_event_port_attach(opl3->seq_client, &callbacks, in snd_opl3_synth_create_port()
H A Dopl3_oss.c49 struct snd_seq_port_callback callbacks; in snd_opl3_oss_create_port() local
60 memset(&callbacks, 0, sizeof(callbacks)); in snd_opl3_oss_create_port()
61 callbacks.owner = THIS_MODULE; in snd_opl3_oss_create_port()
62 callbacks.event_input = snd_opl3_oss_event_input; in snd_opl3_oss_create_port()
63 callbacks.private_free = snd_opl3_oss_free_port; in snd_opl3_oss_create_port()
64 callbacks.private_data = opl3; in snd_opl3_oss_create_port()
70 opl3->oss_chset->port = snd_seq_event_port_attach(opl3->seq_client, &callbacks, in snd_opl3_oss_create_port()
/openbmc/linux/net/lapb/
H A Dlapb_iface.c140 const struct lapb_register_struct *callbacks) in lapb_register() argument
159 lapb->callbacks = callbacks; in lapb_register()
411 if (lapb->callbacks->connect_confirmation) in lapb_connect_confirmation()
412 lapb->callbacks->connect_confirmation(lapb->dev, reason); in lapb_connect_confirmation()
417 if (lapb->callbacks->connect_indication) in lapb_connect_indication()
418 lapb->callbacks->connect_indication(lapb->dev, reason); in lapb_connect_indication()
423 if (lapb->callbacks->disconnect_confirmation) in lapb_disconnect_confirmation()
424 lapb->callbacks->disconnect_confirmation(lapb->dev, reason); in lapb_disconnect_confirmation()
429 if (lapb->callbacks->disconnect_indication) in lapb_disconnect_indication()
430 lapb->callbacks->disconnect_indication(lapb->dev, reason); in lapb_disconnect_indication()
[all …]
/openbmc/qemu/docs/devel/
H A Dtcg-plugins.rst53 is called. The plugin will then register callbacks for various plugin
59 callbacks may provide additional information. In the case of a
62 callbacks to some or all instructions when they are executed.
70 operations and conditional callbacks offer a more efficient way to instrument
71 binaries, compared to classic callbacks.
73 Finally when QEMU exits all the registered *atexit* callbacks are
120 Memory callbacks are called after a successful load or store.
143 list of callbacks under RCU so that we do not have to hold the lock
144 when calling the callbacks. This is also for performance, since some
145 callbacks (e.g. memory access callbacks) might be called very
[all …]
/openbmc/linux/block/
H A Dblk-stat.c15 struct list_head callbacks; member
65 list_for_each_entry_rcu(cb, &q->stats->callbacks, list) { in blk_stat_add()
152 list_add_tail_rcu(&cb->list, &q->stats->callbacks); in blk_stat_add_callback()
164 if (list_empty(&q->stats->callbacks) && !q->stats->accounting) in blk_stat_remove_callback()
192 if (!--q->stats->accounting && list_empty(&q->stats->callbacks)) in blk_stat_disable_accounting()
203 if (!q->stats->accounting++ && list_empty(&q->stats->callbacks)) in blk_stat_enable_accounting()
217 INIT_LIST_HEAD(&stats->callbacks); in blk_alloc_queue_stats()
229 WARN_ON(!list_empty(&stats->callbacks)); in blk_free_queue_stats()
/openbmc/linux/samples/livepatch/
H A DMakefile6 obj-$(CONFIG_SAMPLE_LIVEPATCH) += livepatch-callbacks-demo.o
7 obj-$(CONFIG_SAMPLE_LIVEPATCH) += livepatch-callbacks-mod.o
8 obj-$(CONFIG_SAMPLE_LIVEPATCH) += livepatch-callbacks-busymod.o
H A Dlivepatch-callbacks-demo.c152 .callbacks = {
161 .callbacks = {
170 .callbacks = {
/openbmc/phosphor-dbus-monitor/src/test/templates/
H A Dcallbackgentest.mako.hpp13 const std::array<std::tuple<std::string, size_t>, ${len(callbacks)}> callbacks = {{ variable
14 % for c in callbacks:
H A Dconditiongentest.mako.hpp7 <% graphs = [ x for x in callbacks if hasattr(x, 'graph')] %>\
8 const std::array<size_t, ${len(graphs)}> callbacks = { variable
/openbmc/linux/Documentation/core-api/
H A Dcpu_hotplug.rst139 Once a CPU has been logically shutdown the teardown callbacks of registered
164 When a CPU is onlined, the startup callbacks are invoked sequentially until
166 callbacks of a state are set up or an instance is added to a multi-instance
169 When a CPU is offlined the teardown callbacks are invoked in the reverse
171 be invoked when the callbacks of a state are removed or an instance is
185 The startup callbacks in this section are invoked before the CPU is
186 started during a CPU online operation. The teardown callbacks are invoked
189 The callbacks are invoked on a control CPU as they can't obviously run on
193 The startup callbacks are used to setup resources which are required to
194 bring a CPU successfully online. The teardown callbacks are used to free
[all …]
/openbmc/linux/Documentation/livepatch/
H A Dcallbacks.rst5 Livepatch (un)patch-callbacks provide a mechanism for livepatch modules
16 In most cases, (un)patch callbacks will need to be used in conjunction
61 symmetry: pre-patch callbacks have a post-unpatch counterpart and
62 post-patch callbacks have a pre-unpatch counterpart. An unpatch
69 in-kernel vmlinux targets, this means that callbacks will always execute
71 callbacks will only execute if the target module is loaded. When a
72 module target is (un)loaded, its callbacks will execute only if the
90 No post-patch, pre-unpatch, or post-unpatch callbacks will be executed
95 (this follows the previously mentioned symmetry -- pre-unpatch callbacks
127 callbacks.
H A Dcumulative-patches.rst70 extra modifications in (un)patching callbacks or in the module_init()
77 - Only the (un)patching callbacks from the _new_ cumulative livepatch are
78 executed. Any callbacks from the replaced patches are ignored.
84 older ones. The old livepatches might not provide the necessary callbacks.
92 the various callbacks and their interactions if the callbacks from all
/openbmc/linux/net/ipv6/
H A Dip6_offload.c152 if (likely(ops && ops->callbacks.gso_segment)) { in ipv6_gso_segment()
154 segs = ops->callbacks.gso_segment(skb, features); in ipv6_gso_segment()
249 if (!ops || !ops->callbacks.gro_receive) { in ipv6_gro_receive()
253 if (!ops || !ops->callbacks.gro_receive) in ipv6_gro_receive()
315 ops->callbacks.gro_receive, head, skb); in ipv6_gro_receive()
395 if (WARN_ON(!ops || !ops->callbacks.gro_complete)) in ipv6_gro_complete()
398 err = INDIRECT_CALL_L4(ops->callbacks.gro_complete, tcp6_gro_complete, in ipv6_gro_complete()
428 .callbacks = {
463 .callbacks = {
471 .callbacks = {
[all …]
/openbmc/linux/lib/livepatch/
H A Dtest_klp_callbacks_demo.c75 .callbacks = {
84 .callbacks = {
93 .callbacks = {
/openbmc/linux/Documentation/RCU/
H A DUP.rst77 It is far better to guarantee that callbacks are invoked
85 What locking restriction must RCU callbacks respect?
90 permit call_rcu() to directly invoke callbacks, but only if a full
91 grace period has elapsed since those callbacks were queued. This is
94 encouraged to avoid invoking callbacks from call_rcu(), thus obtaining
102 infrastructure *must* respect grace periods, and *must* invoke callbacks
123 What locking restriction must RCU callbacks respect?
134 then, since RCU callbacks can be invoked from softirq context,
140 callbacks acquire locks directly. However, a great many RCU
141 callbacks do acquire locks *indirectly*, for example, via
H A Drcubarrier.rst34 If we unload the module while some RCU callbacks are pending,
35 the CPUs executing these callbacks are going to be severely
41 grace period to elapse, it does not wait for the callbacks to complete.
45 heavy RCU-callback load, then some of the callbacks might be deferred in
56 outstanding RCU callbacks to complete. Please note that rcu_barrier()
58 callbacks queued anywhere, rcu_barrier() is within its rights to return
63 1. Prevent any new RCU callbacks from being posted.
136 52 /* Wait for all RCU callbacks to fire. */
149 Line 6 sets a global variable that prevents any RCU callbacks from
151 RCU callbacks rarely include calls to call_rcu(). However, the rcutorture
[all …]
/openbmc/linux/drivers/virtio/
H A Dvirtio_pci_common.c285 struct virtqueue *vqs[], vq_callback_t *callbacks[], in vp_find_vqs_msix() argument
302 if (names[i] && callbacks[i]) in vp_find_vqs_msix()
322 if (!callbacks[i]) in vp_find_vqs_msix()
328 vqs[i] = vp_setup_vq(vdev, queue_idx++, callbacks[i], names[i], in vp_find_vqs_msix()
361 struct virtqueue *vqs[], vq_callback_t *callbacks[], in vp_find_vqs_intx() argument
383 vqs[i] = vp_setup_vq(vdev, queue_idx++, callbacks[i], names[i], in vp_find_vqs_intx()
400 struct virtqueue *vqs[], vq_callback_t *callbacks[], in vp_find_vqs() argument
407 err = vp_find_vqs_msix(vdev, nvqs, vqs, callbacks, names, true, ctx, desc); in vp_find_vqs()
411 err = vp_find_vqs_msix(vdev, nvqs, vqs, callbacks, names, false, ctx, desc); in vp_find_vqs()
418 return vp_find_vqs_intx(vdev, nvqs, vqs, callbacks, names, ctx); in vp_find_vqs()
/openbmc/linux/drivers/crypto/virtio/
H A Dvirtio_crypto_core.c101 vq_callback_t **callbacks; in virtcrypto_find_vqs() local
119 callbacks = kcalloc(total_vqs, sizeof(*callbacks), GFP_KERNEL); in virtcrypto_find_vqs()
120 if (!callbacks) in virtcrypto_find_vqs()
127 callbacks[total_vqs - 1] = virtcrypto_ctrlq_callback; in virtcrypto_find_vqs()
132 callbacks[i] = virtcrypto_dataq_callback; in virtcrypto_find_vqs()
138 ret = virtio_find_vqs(vi->vdev, total_vqs, vqs, callbacks, names, NULL); in virtcrypto_find_vqs()
159 kfree(callbacks); in virtcrypto_find_vqs()
168 kfree(callbacks); in virtcrypto_find_vqs()
/openbmc/linux/net/core/
H A Dgso.c21 if (ptype->type == type && ptype->callbacks.gso_segment) { in skb_eth_gso_segment()
22 segs = ptype->callbacks.gso_segment(skb, features); in skb_eth_gso_segment()
52 if (ptype->type == type && ptype->callbacks.gso_segment) { in skb_mac_gso_segment()
53 segs = ptype->callbacks.gso_segment(skb, features); in skb_mac_gso_segment()
/openbmc/linux/Documentation/driver-api/pm/
H A Dnotifiers.rst16 ``->resume()`` or even ``->prepare()`` and ``->complete()`` callbacks are not
33 callbacks for the "freeze" transition.
37 error occurred during hibernation. Device restore callbacks have been
47 callbacks have been executed and tasks have been thawed.
54 resume callbacks have been executed and tasks have been thawed.
H A Ddevices.rst272 executing callbacks for every device before the next phase begins. Not all
273 buses or classes support all these callbacks and not all drivers use all the
274 callbacks. The various phases always run after tasks have been frozen and
279 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
281 ``dev->class->pm`` or ``dev->driver->pm``). These callbacks are regarded by the
282 PM core as mutually exclusive. Moreover, PM domain callbacks always take
283 precedence over all of the other callbacks and, for example, type callbacks take
284 precedence over bus, class and driver callbacks. To be precise, the following
300 This allows PM domains and device types to override callbacks provided by bus
303 The PM domain, type, class and bus callbacks may in turn invoke device- or
[all …]
/openbmc/linux/drivers/rtc/
H A Drtc-hid-sensor-time.c24 struct hid_sensor_hub_callbacks callbacks; member
256 time_state->callbacks.send_event = hid_time_proc_event; in hid_time_probe()
257 time_state->callbacks.capture_sample = hid_time_capture_sample; in hid_time_probe()
258 time_state->callbacks.pdev = pdev; in hid_time_probe()
260 &time_state->callbacks); in hid_time_probe()
/openbmc/linux/drivers/iio/light/
H A Dhid-sensor-prox.c19 struct hid_sensor_hub_callbacks callbacks; member
296 prox_state->callbacks.send_event = prox_proc_event; in hid_prox_probe()
297 prox_state->callbacks.capture_sample = prox_capture_sample; in hid_prox_probe()
298 prox_state->callbacks.pdev = pdev; in hid_prox_probe()
300 &prox_state->callbacks); in hid_prox_probe()

12345678910>>...14