| /linux-4.4.14/kernel/ |
| D | stop_machine.c | 31 bool executed; /* actually executed? */ member
66 static void cpu_stop_signal_done(struct cpu_stop_done *done, bool executed) in cpu_stop_signal_done() argument
69 if (executed) in cpu_stop_signal_done()
70 done->executed = true; in cpu_stop_signal_done()
129 return done.executed ? done.ret : -ENOENT; in stop_one_cpu()
289 return done.executed ? done.ret : -ENOENT; in stop_two_cpus()
347 return done.executed ? done.ret : -ENOENT; in __stop_cpus()
|
| /linux-4.4.14/Documentation/power/ |
| D | pci.txt | 144 methods" that may be executed by the kernel to perform specific tasks, such as
175 3.0) control method defined for it has to be executed before _PSx. Power
295 These callbacks are executed by the PM core in various situations related to
360 that are executed by the core runtime PM routines. It also implements the
392 the driver's callback is executed, pci_pm_runtime_resume() brings the device
422 callbacks for this purpose. They are executed in phases such that each phase
447 suspend callback is executed, if present, and its result is returned. Next, if
453 callback is executed, if defined, and its result is returned if it fails.
458 the pci_pm_suspend() callback may be executed in parallel for any pair of PCI
462 The pci_pm_suspend_noirq() routine is executed after suspend_device_irqs() has
[all …]
|
| D | notifiers.txt | 26 been executed and tasks have been thawed.
33 Device drivers' restore callbacks have been executed
40 executed and tasks have been thawed.
|
| D | suspend-and-interrupts.txt | 12 ->prepare, ->suspend and ->suspend_late callbacks have been executed for all
50 for it will be executed as usual after suspend_device_irqs(), even if the
89 not executed for system wakeup IRQs. They are only executed for IRQF_NO_SUSPEND
|
| D | runtime_pm.txt | 48 are executed by the PM core for the device's subsystem that may be either of
92 RAM until the appropriate resume callback is executed for it. The runtime
135 executed by the PM core whenever the device appears to be idle, which is
164 ->runtime_suspend() or ->runtime_resume() can be executed in parallel with
166 of the other callbacks is being executed for the same device).
168 (2) ->runtime_idle() and ->runtime_suspend() can only be executed for 'active'
173 (3) ->runtime_idle() and ->runtime_suspend() can only be executed for a device
178 (4) ->runtime_resume() can only be executed for 'suspended' devices (i.e. the
185 * If ->runtime_suspend() is about to be executed or there's a pending request
186 to execute it, ->runtime_idle() will not be executed for the same device.
[all …]
|
| D | pm_qos_interface.txt | 203 .set_latency_tolerance() callback will be executed and the effective value will
|
| D | devices.txt | 358 suspend_late is meant to do the latter. It is always executed after
615 analogous to the subsystem-level and device driver callbacks that are executed
619 executed instead of its subsystem's (e.g. bus type's) ->suspend() callback and
|
| D | freezing-of-tasks.txt | 148 be frozen before the driver's .suspend() callback is executed and it will be
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-devices-online | 10 .offline() callback is executed for the device and (if
13 this file, the device bus type's .online() callback is executed
|
| D | sysfs-driver-ppi | 31 executed in the pre-OS environment. It is the only input from
60 operation to be executed in the pre-OS environment by the BIOS
71 operation to be executed in the pre-OS environment by the BIOS
|
| D | sysfs-devices-memory | 57 string "online" the following command can be executed by
|
| D | sysfs-devices-power | 60 be executed asynchronously (ie. in separate threads, in parallel
|
| D | sysfs-power | 153 drivers' suspend and resume callbacks to be executed in parallel
|
| /linux-4.4.14/arch/cris/boot/compressed/ |
| D | README | 11 burned into a flash or executed directly at the DRAM origin.
18 into the file vmlinuz. It can be executed in an arbitrary place in flash.
|
| /linux-4.4.14/Documentation/arm/ |
| D | kernel_mode_neon.txt | 12 * Don't sleep in your NEON code, and be aware that it will be executed with
23 may call schedule()], as NEON or VFP instructions will be executed in a
57 * NEON/VFP code is executed with preemption disabled.
74 executed in kernel mode. If such a condition is encountered, the kernel will
|
| D | swp_emulation | 8 instructions, triggering an undefined instruction exception when executed.
|
| D | Porting | 31 and eventually executed. The following constraint must be valid:
|
| D | tcm.txt | 132 printk("Hello TCM executed from ITCM RAM\n");
|
| D | kernel_user_helpers.txt | 8 code to be executed directly in user mode for best efficiency but which is
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | abi.txt | 9 When a process is executed, it's linked to an exec_domain whose
|
| /linux-4.4.14/kernel/debug/kdb/ |
| D | kdb_cmds | 2 # These commands are executed in kdb_init() context, no SMP, no
|
| /linux-4.4.14/arch/arm/boot/compressed/ |
| D | head-xscale.S | 19 @ This is done by fetching through currently executed
|
| /linux-4.4.14/Documentation/frv/ |
| D | booting.txt | 42 The image is then ready to be executed.
51 The image is then ready to be executed.
63 When finished, the image will then be ready to be executed.
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | ti-edma.txt | 92 /* DMA channel 36 executed on eDMA TC0 - low priority queue */
106 /* DMA channels 8 and 9 executed on eDMA TC2 - high priority queue */
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-report.txt | 77 - dso: name of library or module executed at the time of sample
78 - symbol: name of function executed at the time of sample
83 - srcline: filename and line number executed at the time of sample. The
134 - symbol_daddr: name of data symbol being executed on at the time of sample
135 - dso_daddr: name of library or module containing the data being executed
|
| D | intel-pt.txt | 22 decoder must know precisely which instruction was being executed.
34 builds, however the executed images are needed - which makes use in JIT-compiled
116 by inability to access the executed image, self-modified or JIT-ed code, or the
118 which results in the decoder not knowing what code was executed.
|
| D | perf-top.txt | 221 underlying hardware, the type of branches of interest, and the executed code.
|
| D | perf-record.txt | 236 underlying hardware, the type of branches of interest, and the executed code.
|
| /linux-4.4.14/Documentation/arm/SA1100/ |
| D | ADSBitsy | 13 The kernel zImage is linked to be loaded and executed at 0xc0400000.
|
| D | GraphicsMaster | 13 The kernel zImage is linked to be loaded and executed at 0xc0400000.
|
| D | GraphicsClient | 17 The kernel zImage is linked to be loaded and executed at 0xc0200000.
|
| /linux-4.4.14/Documentation/ |
| D | workqueue.txt | 80 that is to be executed asynchronously. Whenever a driver or subsystem
81 wants a function to be executed asynchronously it has to set up a work
101 aspects of the way the work items are executed by setting flags on the
165 resources, scheduled and executed.
227 are now non-reentrant - any work item is guaranteed to be executed by
354 Because the work functions are executed by generic worker threads
|
| D | intel_txt.txt | 63 executed between system reset through the completion of the kernel
199 kernel code is executed.
|
| D | men-chameleon-bus.txt | 111 also contains callback methods which get executed on driver probe and
|
| D | vme_api.txt | 239 executed, reused and destroyed.
302 once the list has been executed:
|
| D | this_cpu_ops.txt | 111 after the this_cpu instruction is executed. In general this means that
|
| D | memory-hotplug.txt | 83 administrator. For the hot-add case, it must be executed after Physical Hotplug
|
| D | initrd.txt | 35 5) /sbin/init is executed (this can be any valid executable, including
|
| D | cachetlb.txt | 18 if it can be proven that a user address space has never executed
|
| D | kmemcheck.txt | 725 But after the instruction has been executed, we should hide the page again, so
|
| D | kprobes.txt | 202 the instruction can be executed out of line.
|
| D | DMA-API-HOWTO.txt | 332 - Device firmware microcode executed out of
|
| D | kernel-parameters.txt | 1510 initcall_debug [KNL] Trace initcalls as they are executed. Useful
2468 only way then for a file to be executed with privilege
2469 is to be setuid root or executed by root.
|
| /linux-4.4.14/Documentation/acpi/ |
| D | scan_handlers.txt | 45 executed, respectively, after registration of new device nodes and before
52 callback is executed for the given device node. If that callback returns 1,
|
| /linux-4.4.14/Documentation/RCU/ |
| D | rcu.txt | 36 executed in user mode, or executed in the idle loop, we can
|
| D | stallwarn.txt | 125 handlers that the stalled CPU has executed. The number before the "/"
126 is the number that had executed since boot at the time that this CPU
130 time period. The number after the "/" is the number that have executed
|
| D | checklist.txt | 343 13. RCU callbacks can be and are executed in parallel. In many cases,
351 RCU callbacks are -usually- executed on the same CPU that executed
|
| D | listRCU.txt | 268 that the list_add_rcu() was really executed before the list_del_rcu().
|
| D | rcubarrier.txt | 311 means that all CPUs have executed rcu_barrier_func() before
|
| D | whatisRCU.txt | 662 Once -all- CPUs have executed a context switch, then -all- preceding
|
| /linux-4.4.14/Documentation/timers/ |
| D | timer_stats.txt | 66 executed on expiry.
|
| D | highres.txt | 175 is restricted to code which can safely be executed in the hard interrupt
187 function is executed in the next event interrupt context and updates jiffies
|
| D | NO_HZ.txt | 80 1. It increases the number of instructions executed on the path
|
| /linux-4.4.14/drivers/mmc/card/ |
| D | Kconfig | 65 in host controllers. The tests are executed by writing to the
|
| /linux-4.4.14/drivers/of/ |
| D | Kconfig | 21 that are executed once at boot time, and the results dumped to the
|
| /linux-4.4.14/Documentation/prctl/ |
| D | seccomp_filter.txt | 52 The BPF program will be executed over struct seccomp_data
121 userland and the system call is not executed.
142 Results in the system call being executed.
|
| D | no_new_privs.txt | 42 execve and can change the behavior of newly-executed programs.
|
| /linux-4.4.14/Documentation/fault-injection/ |
| D | notifier-error-inject.txt | 6 notifier call chain failures which is rarely executed. There are kernel
|
| /linux-4.4.14/Documentation/serial/ |
| D | moxa-smartio | 73 this program can only be executed under DOS.
204 This step is only needed to be executed once. But you still
228 all the source code. This step is only need to be executed once.
398 you need next time executed.
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | dmatest.txt | 85 number of tests executed, number that failed, and a result code.
|
| /linux-4.4.14/Documentation/accounting/ |
| D | delay-accounting.txt | 78 executed and the corresponding delays to be
|
| /linux-4.4.14/security/integrity/ima/ |
| D | Kconfig | 18 as they are read or executed. If an attacker manages
|
| /linux-4.4.14/Documentation/w1/masters/ |
| D | ds2490 | 54 (and data is available) before the read is executed, so it should
|
| /linux-4.4.14/arch/mn10300/mm/ |
| D | Kconfig.cache | 27 flushed if writes are made that subsequently need to be executed or
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-design-CFS.txt | 41 value (i.e., the task which executed least so far). CFS always tries to split
70 As the system progresses forwards, the executed tasks are put into the tree
|
| D | sched-deadline.txt | 63 to be executed next. Thanks to this feature, tasks that do not strictly comply
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | platform.txt | 191 early_param() command line parsing and can be executed very early on.
233 This step can be executed at any point during the early boot. As soon
|
| D | porting.txt | 393 This is called immediately before /sbin/hotplug is executed.
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra20-pmc.txt | 47 The LP0 vector contains the warm boot code that is executed by AVP when
|
| /linux-4.4.14/arch/arc/kernel/ |
| D | entry.S | 59 ; a kernel thread which is executed via JL above but always returns
|
| /linux-4.4.14/Documentation/x86/ |
| D | entry_64.txt | 90 stack but before we executed SWAPGS, then the only safe way to check
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | CHANGES | 57 For example, if a user executed "fsin.x ADDR,fp0" where
|
| D | fskeleton.S | 190 | bsun will now be re-executed but with the NaN FPSR bit cleared.
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 14 When the WFI instruction is executed the ARM core would gate its internal
|
| /linux-4.4.14/Documentation/trace/ |
| D | tracepoints.txt | 22 is executed, in the execution context of the caller. When the function
|
| D | mmiotrace.txt | 111 fault handler. The instruction that faulted is executed and debug trap is
|
| D | ftrace.txt | 645 never changes) and the version of the kernel upon which this was executed on
863 the time the function itself executed for, not the time
1930 - The cpu number on which the function executed is default
2002 executed the function. It is default disabled.
2123 are loaded and before they are executed. When a module is
2536 CPU that executed the function that triggered the dump.
|
| /linux-4.4.14/Documentation/networking/ |
| D | x25-iface.txt | 92 always executed on the same CPU. Thus,
|
| D | filter.txt | 1272 various test cases for classic and internal BPF that can be executed against
1278 After the module has been built and installed, the test suite can be executed
|
| D | can.txt | 600 executed on an older Linux kernel and switching the CAN_RAW_FD_FRAMES
|
| D | bonding.txt | 1500 executed with sysfs, and without using ifenslave.
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | pmbus-core | 23 executed. Some devices return an error, some devices return 0xff or 0xffff and
116 necessary for chips which react badly if non-supported commands are executed,
|
| /linux-4.4.14/arch/m68k/ |
| D | Kconfig.cpu | 327 needs to be executed whether a floating-point instruction in the
328 kernel should be executed or not.
|
| /linux-4.4.14/Documentation/rapidio/ |
| D | sysfs.txt | 130 Normally, before enumeration/discovery have been executed only
|
| /linux-4.4.14/tools/perf/ |
| D | design.txt | 7 as instructions executed, cachemisses suffered, or branches mis-predicted -
274 executed instructions.
|
| /linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/ |
| D | hub.fuc | 60 // HUB fuc initialisation, executed by triggering ucode start, will
545 // Only executed on the first load of a channel. Might want to look into
|
| D | gpc.fuc | 112 // GPC fuc initialisation, executed by triggering ucode start, will
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-class-tpm | 83 ordinal has been executed successfully in the chip. A '0'
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | head.S | 112 s %r0,8(%r3) # r0/8 = number of ccws executed
|
| D | entry.S | 1055 # check if stpt has been executed
1062 0: # check if stmg has been executed
1156 0: # check if stck & stpt have been executed
|
| /linux-4.4.14/drivers/block/paride/ |
| D | Transition-notes | 19 1 and schedule ps_tq, ps_tq is executed, ps_tq_int() is entered,
|
| /linux-4.4.14/Documentation/scsi/ |
| D | osd.txt | 92 layer and wait for its completion. The request can be executed
|
| D | libsas.txt | 305 Used to queue a task to the SAS LLDD. @task is the task to be executed.
|
| D | scsi_mid_low_api.txt | 243 - init_this_scsi_driver() which is executed when the LLD is
245 - exit_this_scsi_driver() which is executed when the LLD is shut
1043 * scp->scsi_done callback is executed. Note: the driver may
|
| /linux-4.4.14/Documentation/early-userspace/ |
| D | README | 138 mounted and executed via prepare_namespace().
|
| /linux-4.4.14/Documentation/laptops/ |
| D | disk-shock-protection.txt | 86 request to that other device will be executed immediately. Further
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | README | 96 When mount is executed as root, nosuid is not passed in by default,
279 who executed the mount (root, except when mount.cifs
365 program to be executed. This is only meaningful for mounts
375 be executed (default for mounts when executed as root,
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | makefiles.txt | 750 "make clean" is executed.
787 directory compressed/ when "make clean" is executed.
797 When "make clean" is executed, make will descend down in arch/x86/boot,
1058 When make is executed without arguments, the first goal encountered
1070 When "make" is executed without arguments, bzImage will be built.
|
| D | modules.txt | 66 executed to make module versioning work.
114 precondition that a successful "make" has been executed for the
|
| /linux-4.4.14/arch/x86/math-emu/ |
| D | README | 135 queue of the CPU before the mov instruction is executed. If the
138 instruction is executed. The emulator will be invoked but will not be
|
| /linux-4.4.14/Documentation/PCI/ |
| D | PCIEBUS-HOWTO.txt | 100 necessary since these calls are executed by the PCI Port Bus driver.
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | bugfix.S | 479 | an fline illegal instruction to be executed.
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| D | pfpsp.S | 2366 # This handler should be the first code executed upon taking the #
2426 # was executed from supervisor mode, this handler must store the FP #
3067 # This handler should be the first code executed upon taking the #
3741 # This handler should be the first code executed upon taking #
3812 # This handler should be the first code executed upon taking a #
|
| D | fpsp.S | 2367 # This handler should be the first code executed upon taking the #
2427 # was executed from supervisor mode, this handler must store the FP #
3068 # This handler should be the first code executed upon taking the #
3742 # This handler should be the first code executed upon taking #
3810 # This handler should be the first code executed upon taking the #
4124 # into the machine. the frestore has already been executed...so, the fmov.l
16275 # finally executed, the branch occurs. #
|
| /linux-4.4.14/arch/arm/kvm/ |
| D | interrupts_head.S | 595 * VFP wasn't already enabled (always executed on vmtrap).
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | cxl.txt | 169 process. Once this ioctl is successfully executed, all memory
|
| D | hvcs.txt | 343 completed or was never executed.
|
| /linux-4.4.14/Documentation/ia64/ |
| D | fsys.txt | 186 load/store instruction is executed. PSR.be is normally NOT
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | xfs.txt | 220 executed synchronously. This ensures that when the namespace
|
| D | spufs.txt | 153 with the numeric value of the next instruction to be executed. These
|
| D | xfs-delayed-logging-design.txt | 555 checkpoint commit to complete. This background push is checked and executed by
|
| D | proc.txt | 132 cpu Current and last cpu in which it was executed (2.4)(smp)
|
| /linux-4.4.14/Documentation/spi/ |
| D | spi-summary | 135 are always executed in FIFO order, and complete asynchronously through
382 - An spi_message is a sequence of protocol operations, executed
|
| /linux-4.4.14/Documentation/nfc/ |
| D | nfc-hci.txt | 20 host controller (the chip). Commands can be executed synchronously (the sending
|
| /linux-4.4.14/Documentation/block/ |
| D | cfq-iosched.txt | 125 executed for a certain amount of time(time_slice) before switching to another
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | thin-provisioning.txt | 358 this message was executed. Use the pool's status command to
|
| /linux-4.4.14/Documentation/vm/ |
| D | frontswap.txt | 184 executed to obtain the page of data from the real swap device.
|
| /linux-4.4.14/arch/sh/ |
| D | Kconfig | 627 a specially reserved region and then later executed after
|
| /linux-4.4.14/scripts/dtc/ |
| D | dtc-lexer.lex.c_shipped | 830 /* Code executed at the beginning of each rule, after yytext and yyleng
837 /* Code executed at the end of each rule. */
|
| /linux-4.4.14/scripts/genksyms/ |
| D | lex.lex.c_shipped | 733 /* Code executed at the beginning of each rule, after yytext and yyleng
740 /* Code executed at the end of each rule. */
|
| /linux-4.4.14/scripts/kconfig/ |
| D | zconf.lex.c_shipped | 1014 /* Code executed at the beginning of each rule, after zconftext and zconfleng
1021 /* Code executed at the end of each rule. */
|
| /linux-4.4.14/ |
| D | README | 270 to see compile, link, or other commands exactly as they are executed.
|
| /linux-4.4.14/arch/s390/ |
| D | Kconfig | 681 into a specially reserved region and then later executed after
|
| /linux-4.4.14/Documentation/arm64/ |
| D | acpi_object_usage.txt | 88 and executed with the ACPICA tools only during testing.
|
| /linux-4.4.14/Documentation/usb/ |
| D | WUSB-Design-overview.txt | 367 When the xfer is executed, we receive a notification that says data is
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | blkio-controller.txt | 450 the configuration, the bio may be executed at a lower priority and if
|
| D | unified-hierarchy.txt | 152 wins. The specific operations are executed atomically - either all
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | usage-model.txt | 228 specific setup that needs to be executed early in the boot process,
|
| /linux-4.4.14/Documentation/s390/ |
| D | cds.txt | 436 executed a program controlled interrupt (PCI) is generated. The device driver
|
| D | Debugging390.txt | 299 to contain the gmap asce before the SIE instruction gets executed. When
604 in r13,so now we subtract the size of the function prologue we have executed
|
| /linux-4.4.14/Documentation/security/ |
| D | credentials.txt | 191 execve(), especially when a binary is executed that will execute as UID 0.
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | hdio.txt | 556 req_cmd command type to be executed
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README | 367 ... (this can be executed more than once, all assigned numbers are
|
| /linux-4.4.14/Documentation/mtd/ |
| D | nand_ecc.txt | 280 Note that of course now the loop is executed only 64 times (256/4).
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | backend-api.txt | 77 The cache methods are executed one of two contexts:
|
| /linux-4.4.14/arch/arm/mm/ |
| D | Kconfig | 696 when executed. Say Y here to enable software emulation of these
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig | 1238 bool "ARM errata: incorrect instructions may be executed from loop buffer"
2028 reserved region and then later executed after a crash by
|
| /linux-4.4.14/arch/mips/ |
| D | Kconfig | 2430 This option must be set if a kernel might be executed on a MIPS16-
2665 a specially reserved region and then later executed after
|
| /linux-4.4.14/init/ |
| D | Kconfig | 764 be executed in the context of per-CPU rcuo kthreads created for
1654 types of hw events: such as instructions executed, cachemisses
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | api.txt | 1051 - KVM_MP_STATE_HALTED: the vcpu has executed a HLT instruction and
3124 executed a port I/O instruction which could not be satisfied by kvm.
3146 executed a memory-mapped I/O instruction which could not be satisfied
|
| /linux-4.4.14/crypto/ |
| D | Kconfig | 199 crypto algorithms. Multi-buffer crypto algorithms are executed
|
| /linux-4.4.14/Documentation/locking/ |
| D | rt-mutex-design.txt | 711 the rt_mutex_adjust_prio_chain needs to be executed again on the owner,
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig | 1185 be executed on a specific processor. It is a character device
1798 a specially reserved region and then later executed after
|
| /linux-4.4.14/drivers/watchdog/ |
| D | Kconfig | 1449 user define Control Program command to be executed after a
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 1615 executed only once during system boot, so affects only boot time.
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic79xx.reg | 3653 * Address of the SEQRAM instruction executed prior to the current instruction.
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | spkguide.txt | 1171 Note that talkwith must always be executed with root privileges.
|