| /Linux-v6.6/drivers/acpi/acpica/ |
| D | dbinput.c | 346 char *invocation = help->invocation; in acpi_db_match_command_help() local
351 if (*invocation != ' ') { in acpi_db_match_command_help()
355 while (*invocation == ' ') { in acpi_db_match_command_help()
356 invocation++; in acpi_db_match_command_help()
361 while ((*command) && (*invocation) && (*invocation != ' ')) { in acpi_db_match_command_help()
362 if (tolower((int)*command) != tolower((int)*invocation)) { in acpi_db_match_command_help()
366 invocation++; in acpi_db_match_command_help()
374 acpi_os_printf("%-38s : %s", help->invocation, in acpi_db_match_command_help()
403 while (next->invocation) { in acpi_db_display_command_info()
437 while (next->invocation) { in acpi_db_display_help()
[all …]
|
| D | acdebug.h | 29 char *invocation; /* Command Invocation */ member
|
| /Linux-v6.6/Documentation/rust/ |
| D | general-information.rst | 26 target with the same invocation used for compilation, e.g.::
42 the same invocation used for compilation, e.g.::
|
| /Linux-v6.6/tools/perf/Documentation/ |
| D | perf-bench.txt | 174 Repeat memcpy invocation this number of times.
198 Repeat memset invocation this number of times.
|
| /Linux-v6.6/Documentation/RCU/ |
| D | rcuref.rst | 131 even given a concurrent invocation of delete() for that same object.
136 the eventual invocation of kfree(), which is usually not a problem on
|
| D | UP.rst | 62 be self-deadlock *even if* this invocation occurred from a later
63 call_rcu() invocation a full grace period later.
|
| /Linux-v6.6/Documentation/crypto/ |
| D | userspace-if.rst | 156 the setsockopt invocation below.
180 subsequent invocation of the send system call.
210 the setsockopt invocation below.
215 invocation described below.
243 subsequent invocation of the send system call.
370 Each setsockopt invocation must use the level SOL_ALG.
|
| D | architecture.rst | 71 implies that the invocation of a cipher operation will complete almost
72 instantly. That invocation triggers the cipher operation but it does not
|
| /Linux-v6.6/drivers/android/ |
| D | Kconfig | 10 and remote method invocation.
|
| /Linux-v6.6/kernel/rcu/ |
| D | Kconfig | 202 callback invocation.
242 callback invocation to energy-efficient CPUs in battery-powered
248 This option offloads callback invocation from the set of CPUs
310 bool "RCU callback lazy invocation functionality"
|
| /Linux-v6.6/Documentation/bpf/ |
| D | bpf_prog_run.rst | 95 the kernel executes the XDP program repeatedly, each invocation getting a
104 invocation. When possible, the pages will be recycled on future program
|
| /Linux-v6.6/Documentation/driver-api/usb/ |
| D | hotplug.rst | 50 the subsystem making that invocation.
63 are added or removed from system. The invocation is done by the kernel
|
| /Linux-v6.6/Documentation/driver-api/pm/ |
| D | notifiers.rst | 32 additional work is done between the notifiers and the invocation of PM
|
| /Linux-v6.6/Documentation/dev-tools/kunit/ |
| D | index.rst | 37 language function). Excluding build time, from invocation to
|
| /Linux-v6.6/samples/bpf/ |
| D | README.rst | 62 hide the invocation of make as above.
|
| /Linux-v6.6/Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 273 that happens before a given invocation of ``call_rcu()`` must also
428 the invocation of ``__note_gp_changes()`` to have started before the
599 ``__note_gp_changes()``. As shown in the diagram below, this invocation
608 .. kernel-figure:: TreeRCU-callback-invocation.svg
610 Please note that callback invocation can also be prompted by any number
|
| /Linux-v6.6/Documentation/admin-guide/device-mapper/ |
| D | writecache.rst | 10 first sector should contain valid superblock from previous invocation.
|
| /Linux-v6.6/Documentation/ABI/ |
| D | README | 90 commonly installed to /boot, or in any invocation of the kernel build
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | syscall-user-dispatch.rst | 40 non-native applications, it must function on syscalls whose invocation
|
| D | binfmt-misc.rst | 53 is an optional field that controls several aspects of the invocation
|
| /Linux-v6.6/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 193 that waits, directly or indirectly, on completion of an invocation of
507 CPUs during that invocation, then each of the CPUs in that group is
1222 of synchronize_rcu(), thus amortizing the per-invocation overhead
1357 | be correct, given that the invocation of the callback and the freeing |
1414 In theory, delaying grace-period completion and callback invocation is
1432 to ensure timely completion of grace periods and timely invocation of
1465 invocation of callbacks when any given non-\ ``rcu_nocbs`` CPU has
1477 invocation at the expense of degrading realtime response.
1482 RCU`_. Even for RCU, callback-invocation forward
1486 both ``rcu_nocbs`` CPUs and high call_rcu() invocation rates, then
[all …]
|
| /Linux-v6.6/Documentation/driver-api/ |
| D | pwm.rst | 66 last invocation of pwm_apply_state() using pwm_get_state(). Note this is
|
| /Linux-v6.6/Documentation/kbuild/ |
| D | llvm.rst | 78 The same value used for ``LLVM=`` should be set for each invocation of ``make``
|
| /Linux-v6.6/Documentation/userspace-api/ |
| D | seccomp_filter.rst | 179 architecture that supports multiple system call invocation conventions,
180 the system call numbers may vary based on the specific invocation. If
|
| /Linux-v6.6/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 63 invocation will provide the needed quiescent-state report.
97 | ``rcu_read_unlock()`` invocation, which means that the remote state |
124 ``rcu_read_unlock_sched()`` leave no trace of their invocation, in
|
