| /linux/kernel/livepatch/ |
| H A 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/Documentation/driver-api/usb/ |
| H A 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/net/lapb/ |
| H A 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/sound/drivers/opl3/ |
| H A 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/block/ |
| H A D | blk-stat.c | 15 struct list_head callbacks; member
62 list_for_each_entry_rcu(cb, &q->stats->callbacks, list) { in blk_stat_add()
149 list_add_tail_rcu(&cb->list, &q->stats->callbacks); in blk_stat_add_callback()
161 if (list_empty(&q->stats->callbacks) && !q->stats->accounting) in blk_stat_remove_callback()
189 if (!--q->stats->accounting && list_empty(&q->stats->callbacks)) in blk_stat_disable_accounting()
200 if (!q->stats->accounting++ && list_empty(&q->stats->callbacks)) in blk_stat_enable_accounting()
214 INIT_LIST_HEAD(&stats->callbacks); in blk_alloc_queue_stats()
226 WARN_ON(!list_empty(&stats->callbacks)); in blk_free_queue_stats()
|
| /linux/Documentation/core-api/ |
| H A D | cpu_hotplug.rst | 133 Once a CPU has been logically shutdown the teardown callbacks of registered
158 When a CPU is onlined, the startup callbacks are invoked sequentially until
160 callbacks of a state are set up or an instance is added to a multi-instance
163 When a CPU is offlined the teardown callbacks are invoked in the reverse
165 be invoked when the callbacks of a state are removed or an instance is
179 The startup callbacks in this section are invoked before the CPU is
180 started during a CPU online operation. The teardown callbacks are invoked
183 The callbacks are invoked on a control CPU as they can't obviously run on
187 The startup callbacks are used to setup resources which are required to
188 bring a CPU successfully online. The teardown callbacks are used to free
[all …]
|
| /linux/net/ipv6/ |
| H A D | ip6_offload.c | 150 if (likely(ops && ops->callbacks.gso_segment)) { in ipv6_gso_segment()
154 segs = ops->callbacks.gso_segment(skb, features); in ipv6_gso_segment()
247 if (!ops || !ops->callbacks.gro_receive) { in ipv6_gro_receive()
251 if (!ops || !ops->callbacks.gro_receive) in ipv6_gro_receive()
302 ops->callbacks.gro_receive, head, skb); in ipv6_gro_receive()
382 if (WARN_ON(!ops || !ops->callbacks.gro_complete)) in ipv6_gro_complete()
385 err = INDIRECT_CALL_L4(ops->callbacks.gro_complete, tcp6_gro_complete, in ipv6_gro_complete()
442 .callbacks = {
450 .callbacks = {
458 .callbacks = {
[all …]
|
| /linux/Documentation/livepatch/ |
| H A 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.
|
| H A 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/samples/livepatch/ |
| H A 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
|
| H A D | livepatch-callbacks-demo.c | 152 .callbacks = {
161 .callbacks = {
170 .callbacks = {
|
| /linux/Documentation/networking/ |
| H A D | sriov.rst | 16 it consists of a number of ``ndo_set_vf_*`` and ``ndo_get_vf_*`` callbacks.
20 will be accepted. New drivers should not implement the uncommon callbacks;
21 namely the following callbacks are off limits:
|
| /linux/Documentation/RCU/ |
| H A D | UP.rst | 77 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
|
| /linux/tools/testing/selftests/livepatch/test_modules/ |
| H A D | test_klp_callbacks_demo.c | 75 .callbacks = {
84 .callbacks = {
93 .callbacks = {
|
| /linux/net/core/ |
| H A D | gso.c | 21 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()
|
| /linux/Documentation/driver-api/pm/ |
| H A 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.
|
| /linux/drivers/rtc/ |
| H A 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/drivers/iio/pressure/ |
| H A D | hid-sensor-press.c | 22 struct hid_sensor_hub_callbacks callbacks; member
307 press_state->callbacks.send_event = press_proc_event; in hid_press_probe()
308 press_state->callbacks.capture_sample = press_capture_sample; in hid_press_probe()
309 press_state->callbacks.pdev = pdev; in hid_press_probe()
311 &press_state->callbacks); in hid_press_probe()
|
| /linux/drivers/iio/orientation/ |
| H A 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()
|
| H A D | hid-sensor-incl-3d.c | 27 struct hid_sensor_hub_callbacks callbacks; member
365 incl_state->callbacks.send_event = incl_3d_proc_event; in hid_incl_3d_probe()
366 incl_state->callbacks.capture_sample = incl_3d_capture_sample; in hid_incl_3d_probe()
367 incl_state->callbacks.pdev = pdev; in hid_incl_3d_probe()
370 &incl_state->callbacks); in hid_incl_3d_probe()
|
| /linux/Documentation/driver-api/media/ |
| H A D | v4l2-event.rst | 59 ``merge()`` and ``replace()`` callbacks which drivers can set. These
60 callbacks are called when a new event is raised and there is no more room.
75 A good example of these ``replace``/``merge`` callbacks is in v4l2-event.c:
76 ``ctrls_replace()`` and ``ctrls_merge()`` callbacks for the control event.
79 these callbacks can be called from interrupt context, so they must
110 The ops argument allows the driver to specify a number of callbacks:
124 All 4 callbacks are optional, if you don't want to specify any callbacks
|
| /linux/drivers/iio/gyro/ |
| H A D | hid-sensor-gyro-3d.c | 25 struct hid_sensor_hub_callbacks callbacks; member
342 gyro_state->callbacks.send_event = gyro_3d_proc_event; in hid_gyro_3d_probe()
343 gyro_state->callbacks.capture_sample = gyro_3d_capture_sample; in hid_gyro_3d_probe()
344 gyro_state->callbacks.pdev = pdev; in hid_gyro_3d_probe()
346 &gyro_state->callbacks); in hid_gyro_3d_probe()
|
| /linux/drivers/iio/position/ |
| H A D | hid-sensor-custom-intel-hinge.c | 37 struct hid_sensor_hub_callbacks callbacks; member
320 st->callbacks.send_event = hinge_proc_event; in hid_hinge_probe()
321 st->callbacks.capture_sample = hinge_capture_sample; in hid_hinge_probe()
322 st->callbacks.pdev = pdev; in hid_hinge_probe()
323 ret = sensor_hub_register_callback(hsdev, hsdev->usage, &st->callbacks); in hid_hinge_probe()
|
| /linux/Documentation/driver-api/80211/ |
| H A D | mac80211.rst | 25 Additionally, some discussion about the callbacks and the general
49 This chapter should describe PHY handling including start/stop callbacks
64 the add_iface/remove_iface callbacks as well as the interface
65 configuration callbacks.
|
| /linux/drivers/iio/light/ |
| H A D | hid-sensor-prox.c | 31 struct hid_sensor_hub_callbacks callbacks; member
328 prox_state->callbacks.send_event = prox_proc_event; in hid_prox_probe()
329 prox_state->callbacks.capture_sample = prox_capture_sample; in hid_prox_probe()
330 prox_state->callbacks.pdev = pdev; in hid_prox_probe()
332 &prox_state->callbacks); in hid_prox_probe()
|