| /linux-6.8/lib/ |
| D | dynamic_debug.c | 56 const char *module; member
145 query->module ?: "", in vpr_info_dq()
190 if (query->module && in ddebug_change()
191 !match_wildcard(query->module, dt->mod_name)) in ddebug_change()
449 rc = check_set(&query->module, arg, "module"); in ddebug_parse_query()
467 if (!query->module && modname) in ddebug_parse_query()
472 query->module = modname; in ddebug_parse_query()
486 int op, i; in ddebug_parse_flags() local
492 op = *str++; in ddebug_parse_flags()
498 v3pr_info("op='%c'\n", op); in ddebug_parse_flags()
[all …]
|
| /linux-6.8/drivers/char/ |
| D | Kconfig | 49 To compile this driver as a module, choose M here and read
50 <file:Documentation/admin-guide/parport.rst>. The module will be called lp.
67 doing that; to actually get it to happen you need to pass the
91 To compile this driver as a module, choose M here: the
92 module will be called ppdev.
133 If unsure, say M here to build it as a module called powernv-op-panel.
145 It is also possible to say M here to build it as a module (ds1620)
167 To compile this driver as a module, choose M here: the
168 module will be called nwbutton.
182 driver as a module, you can specify the number of presses at load
[all …]
|
| /linux-6.8/Documentation/driver-api/ |
| D | ipmi.rst | 84 option. You can also enable these dynamically by setting the module
85 parameter named "panic_op" in the ipmi_msghandler module to "event"
94 code. These chunks (by module name) are:
288 Once you are done, call ipmi_destroy_user() to get rid of the user.
312 read() to get them, you must call the IPMICTL_RECEIVE_MSG with the
313 ipmi_recv_t structure to actually get the message. Remember that you
318 If the message cannot fit into the data you provide, you will get an
320 queue. If you want to get it and have it truncate the message, us
395 You can specify up to four interfaces on the module load line and
396 control some module parameters::
[all …]
|
| /linux-6.8/Documentation/admin-guide/ |
| D | sysrq.rst | 214 Sometimes SysRq seems to get 'stuck' after using it, what can I do?
236 I want to add SysRQ key events to a module, how does it work?
249 if that slot in the table is blank. At module unload time, you must call
251 which will remove the key op pointed to by 'op_p' from the key 'key', if and
255 The Magic SysRQ system works by registering key operations against a key op
263 your module that called register_sysrq_key() exits, it must call
|
| /linux-6.8/arch/m68k/ifpsp060/src/ |
| D | pfpsp.S | 916 btst &0x4,1+EXC_CMDREG(%a6) # is op an fsincos?
922 lea FP_DST(%a6),%a0 # pass: ptr to dst op
1268 lea FP_SRC(%a6),%a0 # pass: ptr to src op
1356 # save the result in the proper fp reg (unless the op is fcmp or ftst);
1408 frestore FP_SRC(%a6) # restore src op
1673 # for snan,operr,ovfl,unfl, src op is still in FP_SRC so just
1757 # frame or it will get overwritten when the exc stack frame is shifted "down".
1833 lea FP_DST(%a6),%a0 # pass: ptr to dst op
1934 # save the result in the proper fp reg (unless the op is fcmp or ftst);
1992 frestore FP_SRC(%a6) # restore src op
[all …]
|
| D | fpsp.S | 917 btst &0x4,1+EXC_CMDREG(%a6) # is op an fsincos?
923 lea FP_DST(%a6),%a0 # pass: ptr to dst op
1269 lea FP_SRC(%a6),%a0 # pass: ptr to src op
1357 # save the result in the proper fp reg (unless the op is fcmp or ftst);
1409 frestore FP_SRC(%a6) # restore src op
1674 # for snan,operr,ovfl,unfl, src op is still in FP_SRC so just
1758 # frame or it will get overwritten when the exc stack frame is shifted "down".
1834 lea FP_DST(%a6),%a0 # pass: ptr to dst op
1935 # save the result in the proper fp reg (unless the op is fcmp or ftst);
1993 frestore FP_SRC(%a6) # restore src op
[all …]
|
| /linux-6.8/Documentation/admin-guide/media/ |
| D | vivid.rst | 53 all configurable using the following module options:
80 these module options to vivid:
107 would use the following module options:
132 following module options:
265 This module option can override that for each instance. Values are:
305 Taken together, all these module options allow you to precisely customize
315 can be configured by using the module options num_inputs, input_types and
326 exceeds your kernel's HZ value, then you will get dropped frames, but the
436 The video output device can be configured by using the module options
484 support both. This is determined by the node_types module option. In all
[all …]
|
| /linux-6.8/Documentation/networking/ |
| D | filter.rst | 207 op:16, jt:8, jf:8, k:32
209 The element op is a 16 bit wide opcode that has a particular instruction
213 ways depending on the given instruction in op.
336 # get a random uint32 number
446 /* { op, jt, jf, k }, */
659 Next to the BPF toolchain, the kernel also ships a test module that contains
666 After the module has been built and installed, the test suite can be executed
667 via insmod or modprobe against 'test_bpf' module. Results of the test cases
|
| D | can.rst | 47 protocol family module and also vice-versa. Also, the protocol family
48 module provides an API for transport protocol modules to register, so
50 dynamically. In fact, the can core module alone does not provide any
52 protocol module. Multiple sockets can be opened at the same time,
53 on different or the same protocol module and they can listen/send
127 module - which implements the protocol family CAN - provides several
129 application opens a CAN RAW socket, the raw protocol module itself
134 CAN protocol modules by the SocketCAN core (see :ref:`socketcan-core-module`).
368 /* get interface name of the received CAN frame */
671 socket option returns an error: No problem. You'll get Classical CAN frames
[all …]
|
| D | ip-sysctl.rst | 863 get detected right after Fastopen is re-enabled and will reset to
1122 field, and currently no-op for IPv4 headers. It is possible
1129 available and used by congestion control module to estimate a
2905 trying to get a SCTP_PF-state transport info via SCTP_GET_PEER_ADDR_INFO
3168 must be started. On the server, it would get the encap_port from
|
| /linux-6.8/sound/core/ |
| D | control.c | 66 if (!try_module_get(card->module)) { in snd_ctl_open()
90 module_put(card->module); in snd_ctl_open()
137 module_put(card->module); in snd_ctl_release()
309 kctl->get = ncontrol->get; in snd_ctl_new1()
1291 if (!(vd->access & SNDRV_CTL_ELEM_ACCESS_READ) || kctl->get == NULL) { in snd_ctl_elem_read()
1311 ret = kctl->get(kctl, control); in snd_ctl_elem_read()
1814 kctl->get = snd_ctl_elem_user_get; in snd_ctl_elem_add()
1896 int op; in call_tlv_handler() member
1908 if (op_flag == pairs[i].op && (vd->access & pairs[i].perm)) in call_tlv_handler()
|
| /linux-6.8/Documentation/filesystems/ |
| D | netfs_library.rst | 29 Note that the library module doesn't link against local caching directly, so
89 and finally, a function to get the cache cookie pointer from the context
163 progress when an error occurs, the request will get partially completed if
218 may be altered by the ->expand_readahead() op.
371 left set) or the op should be retried (``*foliop`` cleared) and any other
391 be performed, though this may not get written to the cache in its entirety.
|
| D | mount_api.rst | 115 superblock thereof). This is filled in by the ->get_tree() op. If this
203 module.
279 Called to get or create the mountable root and superblock, using the
451 for use where a filesystem has to get a mount within a mount, such as NFS4
470 In all the above operations, apart from the put op, the return is a mount
567 attempt to get a new superblock gets this one (and any parameter
|
| D | autofs.rst | 30 The "autofs" filesystem module is only one part of an autofs system.
34 This document describes only the kernel module and the interactions
38 "autofs" is a Linux kernel module which provides the "autofs"
140 discussed later. This allows the automount daemon not to get
190 VFS remain in RCU-walk mode, but can only tell it to get out of
480 that the kernel module can support.
558 space based on the kernel mount list a no-op mount option ("ignore" is
|
| /linux-6.8/drivers/scsi/qedf/ |
| D | qedf_main.c | 307 struct fc_frame *fp, unsigned int op, in qedf_elsct_send() argument
326 return fc_elsct_send(lport, did, fp, op, qedf_flogi_resp, in qedf_elsct_send()
330 return fc_elsct_send(lport, did, fp, op, resp, arg, timeout); in qedf_elsct_send()
635 static void qedf_dcbx_handler(void *dev, struct qed_dcbx_get *get, u32 mib_type) in qedf_dcbx_handler() argument
641 "prio=%d.\n", get->operational.valid, get->operational.enabled, in qedf_dcbx_handler()
642 get->operational.app_prio.fcoe); in qedf_dcbx_handler()
644 if (get->operational.enabled && get->operational.valid) { in qedf_dcbx_handler()
661 tmp_prio = get->operational.app_prio.fcoe; in qedf_dcbx_handler()
985 .module = THIS_MODULE,
|
| /linux-6.8/Documentation/gpu/ |
| D | todo.rst | 15 Starter: Good tasks to get started with the DRM subsystem.
71 We have a helper to get this right with drm_plane_helper_check_update(), but
240 being rewritten without dependencies on the fbdev module. Some of the
329 - For most connectors it's a no-op to call drm_connector_register/unregister
344 for historical reasons they get the ordering wrong (and we can't fix that)
467 been called. To get some idea of the duplicated code, try::
738 will need to be done to get the output <-> backlight device mapping
744 only one of the 2 required backlight devices will get registered, based on
789 no support to get the buffer age or any other damage accumulation algorithm.
797 This should be improved to get damage tracking properly working on drivers that
|
| /linux-6.8/Documentation/virt/uml/ |
| D | user_mode_linux_howto_v2.rst | 63 * You can get extremely high performance for anything which is a "kernel
185 To specify the full module installation path, use::
722 * get the kernel version
754 You'll get a prompt, at which you can run one of these commands:
779 There are a couple actual uses for this. It's a simple no-op which
985 module and available inside the virtual machine, and insmod it.
1022 module. Then run UML with the boot device pointing at that directory::
1170 UML driver as a kernel module, that limits the possible functionality
1224 security-wise. Allowing it as a loadable module parameter
1237 are loaded at boot and kernel module loading is disabled
|
| /linux-6.8/Documentation/scsi/ |
| D | ncr53c8xx.rst | 335 impact on performances is not too bad. You can get rid of the messages by
371 However, if the driver has been made as module, the number of the
378 and you will get something like the following text::
415 attached. So, if the driver is a module, the profile counters are
462 (time from SCSI status get to command completion call)
713 The following command will install driver module with the same options as
885 burst:255 get burst length from initial IO register settings.
1095 "ncr53c8xx=verb:2" to get the "static" setup of the driver, or add "verb:2"
1142 to control what information the driver will get from the NVRAM and what
1149 The parameters the driver is able to get from the NVRAM depend on the
[all …]
|
| /linux-6.8/net/netfilter/ |
| D | nf_tables_api.c | 76 int op; member
864 char module[MODULE_NAME_LEN]; member
886 if (!strcmp(req->module, module_name)) { in nft_request_module()
900 strscpy(req->module, module_name, MODULE_NAME_LEN); in nft_request_module()
1116 .module = THIS_MODULE, in nf_tables_gettable()
1941 .module = THIS_MODULE, in nf_tables_getchain()
3244 struct module *owner; in nft_expr_init()
3685 .module = THIS_MODULE, in nf_tables_getrule()
3714 .module = THIS_MODULE, in nf_tables_getrule_reset()
4760 .module = THIS_MODULE, in nf_tables_getset()
[all …]
|
| /linux-6.8/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 1124 eventually get the data where it needs to go. In general, when tracking
1475 handler to get around to it.
1511 kernel) you will get an RCU CPU stall warning. Nevertheless, this class
1770 implementation can be a no-op.
1857 unloaded. After a given module has been unloaded, any attempt to call
1858 one of its functions results in a segmentation fault. The module-unload
1859 functions must therefore cancel any delayed calls to loadable-module
1867 module unload request, we need some other way to deal with in-flight RCU
1871 in-flight RCU callbacks have been invoked. If a module uses
1874 the underlying module-unload code could invoke rcu_barrier()
[all …]
|
| /linux-6.8/Documentation/virt/kvm/ |
| D | api.rst | 706 configuration (if there is) is not corrupted. Userspace can get a copy
1458 The capability that is supposed to get enabled.
2088 the kernel will ignore the length of guest write and may get a faster vmexit.
2893 LoongArch csr registers are used to control guest cpu or get status of guest
3814 __u32 op; /* type of operation */
3838 The type of operation is specified in the "op" field. Flags modifying
3921 occurred. The cmpxchg op is permitted for the VM ioctl if
3948 This ioctl is used to get guest storage key values on the s390
3960 you want to get.
3963 whose storage keys to get. The count field must be at least 1 and the maximum
[all …]
|
| /linux-6.8/ |
| D | CREDITS | 264 E: pbd@op.net
565 D: device drivers. His encouragement also helped many engineers get
785 D: Kernel module SMART utilities
1725 D: Some other hacks to get different kinds of programs to work for linux
2198 D: Loopback block device: dynamic sizing ("max_loop" as module)
2450 D: Netfilter pkttype module
2644 D: rcutorture module
3087 D: Isochronous receive for IEEE 1394 driver (OHCI module).
3229 D: {copy,get,put}_user calls updates
3394 D: IEEE 1394 OHCI module
[all …]
|
| /linux-6.8/Documentation/security/keys/ |
| D | core.rst | 810 process must have LINK permission on the keyring and the active LSM module
1189 passed to the key_type->request_key() op if it exists, and the
1631 * ``int (*request_key)(struct key_construction *cons, const char *op, void *aux);``
1702 enum kernel_pkey_operation op : 8;
1723 specified by params->op. Note that params->op is also set for
1733 data in the output buffer. Padding will get checked and stripped off if
|