/linux-6.1.9/kernel/livepatch/ |
D | core.h | 30 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 …]
|
/linux-6.1.9/sound/drivers/opl3/ |
D | opl3_seq.c | 163 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()
|
D | opl3_oss.c | 49 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()
|
/linux-6.1.9/fs/dlm/ |
D | ast.c | 221 struct dlm_callback callbacks[DLM_CALLBACKS_SIZE]; in dlm_callback_work() local 224 memset(&callbacks, 0, sizeof(callbacks)); in dlm_callback_work() 235 rv = dlm_rem_lkb_callback(ls, lkb, &callbacks[i], &resid); in dlm_callback_work() 253 if (!callbacks[i].seq) in dlm_callback_work() 255 if (callbacks[i].flags & DLM_CB_SKIP) { in dlm_callback_work() 257 } else if (callbacks[i].flags & DLM_CB_BAST) { in dlm_callback_work() 258 trace_dlm_bast(ls, lkb, callbacks[i].mode); in dlm_callback_work() 259 bastfn(lkb->lkb_astparam, callbacks[i].mode); in dlm_callback_work() 260 } else if (callbacks[i].flags & DLM_CB_CAST) { in dlm_callback_work() 261 lkb->lkb_lksb->sb_status = callbacks[i].sb_status; in dlm_callback_work() [all …]
|
/linux-6.1.9/Documentation/driver-api/usb/ |
D | callbacks.rst | 1 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 …]
|
/linux-6.1.9/net/lapb/ |
D | lapb_iface.c | 140 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 …]
|
/linux-6.1.9/samples/livepatch/ |
D | Makefile | 6 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
|
D | livepatch-callbacks-demo.c | 152 .callbacks = { 161 .callbacks = { 170 .callbacks = {
|
/linux-6.1.9/Documentation/core-api/ |
D | cpu_hotplug.rst | 148 Once a CPU has been logically shutdown the teardown callbacks of registered 173 When a CPU is onlined, the startup callbacks are invoked sequentially until 175 callbacks of a state are set up or an instance is added to a multi-instance 178 When a CPU is offlined the teardown callbacks are invoked in the reverse 180 be invoked when the callbacks of a state are removed or an instance is 194 The startup callbacks in this section are invoked before the CPU is 195 started during a CPU online operation. The teardown callbacks are invoked 198 The callbacks are invoked on a control CPU as they can't obviously run on 202 The startup callbacks are used to setup resources which are required to 203 bring a CPU successfully online. The teardown callbacks are used to free [all …]
|
/linux-6.1.9/Documentation/livepatch/ |
D | callbacks.rst | 5 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.
|
D | cumulative-patches.rst | 70 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
|
/linux-6.1.9/net/ipv6/ |
D | ip6_offload.c | 136 if (likely(ops && ops->callbacks.gso_segment)) { in ipv6_gso_segment() 138 segs = ops->callbacks.gso_segment(skb, features); in ipv6_gso_segment() 234 if (!ops || !ops->callbacks.gro_receive) { in ipv6_gro_receive() 243 if (!ops || !ops->callbacks.gro_receive) in ipv6_gro_receive() 301 ops->callbacks.gro_receive, head, skb); in ipv6_gro_receive() 381 if (WARN_ON(!ops || !ops->callbacks.gro_complete)) in ipv6_gro_complete() 384 err = INDIRECT_CALL_L4(ops->callbacks.gro_complete, tcp6_gro_complete, in ipv6_gro_complete() 414 .callbacks = { 449 .callbacks = { 457 .callbacks = { [all …]
|
/linux-6.1.9/block/ |
D | blk-stat.c | 16 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() 217 INIT_LIST_HEAD(&stats->callbacks); in blk_alloc_queue_stats() 229 WARN_ON(!list_empty(&stats->callbacks)); in blk_free_queue_stats()
|
/linux-6.1.9/lib/livepatch/ |
D | test_klp_callbacks_demo.c | 75 .callbacks = { 84 .callbacks = { 93 .callbacks = {
|
/linux-6.1.9/Documentation/RCU/ |
D | rcubarrier.rst | 59 If we unload the module while some RCU callbacks are pending, 60 the CPUs executing these callbacks are going to be severely 66 grace period to elapse, it does not wait for the callbacks to complete. 70 heavy RCU-callback load, then some of the callbacks might be deferred 80 callbacks to complete. Please note that rcu_barrier() does **not** imply 81 synchronize_rcu(), in particular, if there are no RCU callbacks queued 87 1. Prevent any new RCU callbacks from being posted. 157 52 /* Wait for all RCU callbacks to fire. */ 170 Line 6 sets a global variable that prevents any RCU callbacks from 172 RCU callbacks rarely include calls to call_rcu(). However, the rcutorture [all …]
|
/linux-6.1.9/drivers/crypto/virtio/ |
D | virtio_crypto_core.c | 100 vq_callback_t **callbacks; in virtcrypto_find_vqs() local 118 callbacks = kcalloc(total_vqs, sizeof(*callbacks), GFP_KERNEL); in virtcrypto_find_vqs() 119 if (!callbacks) in virtcrypto_find_vqs() 126 callbacks[total_vqs - 1] = virtcrypto_ctrlq_callback; in virtcrypto_find_vqs() 131 callbacks[i] = virtcrypto_dataq_callback; in virtcrypto_find_vqs() 137 ret = virtio_find_vqs(vi->vdev, total_vqs, vqs, callbacks, names, NULL); in virtcrypto_find_vqs() 156 kfree(callbacks); in virtcrypto_find_vqs() 165 kfree(callbacks); in virtcrypto_find_vqs()
|
/linux-6.1.9/drivers/virtio/ |
D | virtio_pci_common.c | 285 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() 359 struct virtqueue *vqs[], vq_callback_t *callbacks[], in vp_find_vqs_intx() argument 381 vqs[i] = vp_setup_vq(vdev, queue_idx++, callbacks[i], names[i], in vp_find_vqs_intx() 398 struct virtqueue *vqs[], vq_callback_t *callbacks[], in vp_find_vqs() argument 405 err = vp_find_vqs_msix(vdev, nvqs, vqs, callbacks, names, true, ctx, desc); in vp_find_vqs() 409 err = vp_find_vqs_msix(vdev, nvqs, vqs, callbacks, names, false, ctx, desc); in vp_find_vqs() 416 return vp_find_vqs_intx(vdev, nvqs, vqs, callbacks, names, ctx); in vp_find_vqs()
|
/linux-6.1.9/drivers/rtc/ |
D | rtc-hid-sensor-time.c | 24 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()
|
/linux-6.1.9/Documentation/driver-api/pm/ |
D | notifiers.rst | 16 ``->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.
|
D | devices.rst | 272 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 …]
|
/linux-6.1.9/drivers/iio/light/ |
D | hid-sensor-prox.c | 19 struct hid_sensor_hub_callbacks callbacks; member 291 prox_state->callbacks.send_event = prox_proc_event; in hid_prox_probe() 292 prox_state->callbacks.capture_sample = prox_capture_sample; in hid_prox_probe() 293 prox_state->callbacks.pdev = pdev; in hid_prox_probe() 295 &prox_state->callbacks); in hid_prox_probe()
|
/linux-6.1.9/drivers/iio/pressure/ |
D | hid-sensor-press.c | 22 struct hid_sensor_hub_callbacks callbacks; member 306 press_state->callbacks.send_event = press_proc_event; in hid_press_probe() 307 press_state->callbacks.capture_sample = press_capture_sample; in hid_press_probe() 308 press_state->callbacks.pdev = pdev; in hid_press_probe() 310 &press_state->callbacks); in hid_press_probe()
|
/linux-6.1.9/include/linux/ |
D | virtio_config.h | 105 struct virtqueue *vqs[], vq_callback_t *callbacks[], 211 vq_callback_t *callbacks[] = { c }; in virtio_find_single_vq() local 214 int err = vdev->config->find_vqs(vdev, 1, &vq, callbacks, names, NULL, in virtio_find_single_vq() 223 struct virtqueue *vqs[], vq_callback_t *callbacks[], in virtio_find_vqs() argument 227 return vdev->config->find_vqs(vdev, nvqs, vqs, callbacks, names, NULL, desc); in virtio_find_vqs() 232 struct virtqueue *vqs[], vq_callback_t *callbacks[], in virtio_find_vqs_ctx() argument 236 return vdev->config->find_vqs(vdev, nvqs, vqs, callbacks, names, ctx, in virtio_find_vqs_ctx()
|
/linux-6.1.9/drivers/iio/orientation/ |
D | hid-sensor-rotation.c | 18 struct hid_sensor_hub_callbacks callbacks; member 310 rot_state->callbacks.send_event = dev_rot_proc_event; in hid_dev_rot_probe() 311 rot_state->callbacks.capture_sample = dev_rot_capture_sample; in hid_dev_rot_probe() 312 rot_state->callbacks.pdev = pdev; in hid_dev_rot_probe() 314 &rot_state->callbacks); in hid_dev_rot_probe()
|
/linux-6.1.9/Documentation/power/ |
D | pci.rst | 280 pointers to several device power management callbacks:: 302 These callbacks are executed by the PM core in various situations related to 303 device power management and they, in turn, execute power management callbacks 309 that these callbacks operate on:: 363 Namely, it provides subsystem-level callbacks:: 431 management callbacks for this purpose. They are executed in phases such that 444 The following PCI bus type's callbacks, respectively, are used in these phases:: 459 pointers to the driver's callbacks), pci_pm_default_suspend() is called, which 483 device driver's callbacks executed before might do that), pci_pm_suspend_noirq() 494 PCI device drivers (that don't implement legacy power management callbacks) are [all …]
|