Searched full:behavior (Results 1 – 25 of 251) sorted by relevance
1234567891011
| /Documentation/process/ |
| D | code-of-conduct.rst | 19 Examples of behavior that contributes to creating a positive environment
29 Examples of unacceptable behavior by participants include:
44 Maintainers are responsible for clarifying the standards of acceptable behavior
46 any instances of unacceptable behavior.
67 Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-dust.txt | 4 This target emulates the behavior of bad sectors at arbitrary
10 requests on specific blocks (to emulate the behavior of a hard disk
13 When the failure behavior is enabled (i.e.: when the output of
22 This emulates the "remapped sector" behavior of a drive with bad
59 Check the status of the read behavior ("bypass" indicates that all I/O
97 To enable the "fail read on bad block" behavior, send the "enable" message:
115 therefore emulating the "remap" behavior of hard disk drives:
269 This target seeks to provide a device that can exhibit the behavior
|
| /Documentation/powerpc/ |
| D | syscall64-abi.rst | 55 Syscall behavior can change if the processor is in transactional or suspended
56 transaction state, and the syscall can affect the behavior of the transaction.
65 behavior depends on the presence of PPC_FEATURE2_HTM_NOSC in the AT_HWCAP2 ELF
76 behavior should not be relied upon.
|
| /Documentation/admin-guide/ |
| D | jfs.rst | 16 iocharset=none specifies the default behavior explicitly.
34 previously specified in order to restore normal behavior.
|
| D | binfmt-misc.rst | 58 Legacy behavior of binfmt_misc is to overwrite
68 Legacy behavior of binfmt_misc is to pass the full path
76 Currently, the behavior of binfmt_misc is to calculate
|
| /Documentation/cdrom/ |
| D | cdrom-standard.rst | 27 all these different devices has also allowed the behavior of each
29 This divergence of behavior has been very significant for CD-ROM
35 maintain uniform behavior across all the Linux CD-ROM drivers.
37 This document describes an effort to establish Uniform behavior across
66 importantly, it appeared that the behavior of the `standard` commands
73 behavior was usually different.
94 **one** Linux CD-ROM interface with consistent behavior for all
123 importantly, this led to the divergence of behavior, which has already
127 CD-ROM drive behavior, and to provide a common set of services to the various
166 place where the behavior of all CD-ROM-devices is defined and
[all …]
|
| /Documentation/ia64/ |
| D | irq-redir.rst | 9 controlled. The behavior on IA64 platforms is slightly different from
45 Initialization and default behavior
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-da8xx-ddrctl.txt | 4 a set of registers which allow to tweak the controller's behavior.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | atmel-matrix.txt | 4 behavior (master/slave priorities, undefined burst length type, ...)
|
| /Documentation/arm/ |
| D | mem_alignment.rst | 30 To change the alignment trap behavior, simply echo a number into
34 bit behavior when set
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-class-dax | 14 2/ Enforces deterministic behavior by being strict about
|
| /Documentation/core-api/ |
| D | protection-keys.rst | 72 Behavior chapter
76 behavior of a plain mprotect(). For instance if you do this::
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | memcg_test.rst | 9 Because VM is getting complex (one of reasons is memcg...), memcg's behavior
10 is complex. This is a document for memcg's internal behavior.
114 But brief explanation of the behavior of memcg around shmem will be
161 (Memory behavior under GB and Memory behavior under MB shows very
|
| /Documentation/devicetree/bindings/devfreq/event/ |
| D | exynos-nocp.txt | 10 NoC probes to provide bandwidth information about behavior of the SoC
|
| /Documentation/dev-tools/ |
| D | ubsan.rst | 1 The Undefined Behavior Sanitizer - UBSAN
6 UBSAN uses compile-time instrumentation to catch undefined behavior (UB).
|
| /Documentation/vm/ |
| D | z3fold.rst | 29 depend on MMU enabled and provides more predictable reclaim behavior
|
| /Documentation/networking/ |
| D | openvswitch.txt | 60 but the forwarding behavior is correct. (If userspace can
62 forwarding behavior, then it could set up a flow anyway.)
127 The behavior when using overlapping wildcarded flows is undefined. It is the
131 some but not all of them. However, this behavior may change in future versions.
185 802.1Q header) and it could cause the application's behavior to change
|
| /Documentation/ |
| D | DMA-attributes.txt | 34 behavior.
44 behavior.
70 attribute and exhibit default behavior.
|
| /Documentation/admin-guide/sysctl/ |
| D | kernel.rst | 311 This value controls the hard lockup detector behavior when a hard
316 0: do nothing. This is the default behavior.
344 Controls the kernel's behavior when a hung task is detected.
347 0: continue operation. This is the default behavior.
401 1: report the panic kmsg data. This is the default behavior.
602 Controls the kernel's behavior when a CPU receives an NMI caused by
628 Controls the kernel's behavior when detecting the overflows of
686 0: do not panic() when RCU stall takes place, default behavior.
805 These values influence printk() behavior when printing or
996 Control how file position affects the behavior of updating sysctl values
[all …]
|
| /Documentation/devicetree/bindings/mips/cavium/ |
| D | sata-uctl.txt | 11 - control the behavior of the UAHC
|
| /Documentation/block/ |
| D | writeback_cache_control.rst | 11 behavior obviously speeds up various workloads, but it means the operating
16 control the caching behavior of the storage device. These mechanisms are
|
| /Documentation/filesystems/ |
| D | overlayfs.txt | 38 underlying filesystem, the same compliant behavior could be achieved
187 recursively copies the directory tree). This is the default behavior.
330 upper layer and/or workdir path the behavior of the overlay is undefined,
359 Non-standard behavior
418 the behavior of the overlay is undefined, though it will not result in
422 behavior on offline changes of the underlying lower layer is different
423 than the behavior when NFS export is disabled.
|
| /Documentation/misc-devices/ |
| D | spear-pcie-gadget.txt | 31 read behavior of nodes:
44 write behavior of nodes:
|
| /Documentation/virt/kvm/devices/ |
| D | arm-vgic.txt | 56 confirm its expected behavior is aligned with the KVM implementation.
59 the expected behavior. Unless GICD_IIDR has been set from userspace, writes
|
| /Documentation/devicetree/bindings/arm/ |
| D | l2c2x0.yaml | 163 description: The default behavior of the L220 or PL310 cache
209 disable), <1> (forcibly enable), property absent (OS specific behavior,
217 <1> (forcibly enable), property absent (OS specific behavior,
|
1234567891011