Home
last modified time | relevance | path

Searched refs:behavior (Results 1 – 200 of 219) sorted by relevance

12

/linux-4.1.27/mm/
Dmadvise.c28 static int madvise_need_mmap_write(int behavior) in madvise_need_mmap_write() argument
30 switch (behavior) { in madvise_need_mmap_write()
47 unsigned long start, unsigned long end, int behavior) in madvise_behavior() argument
54 switch (behavior) { in madvise_behavior()
86 error = ksm_madvise(vma, start, end, behavior, &new_flags); in madvise_behavior()
92 error = hugepage_madvise(vma, &new_flags, behavior); in madvise_behavior()
373 unsigned long start, unsigned long end, int behavior) in madvise_vma() argument
375 switch (behavior) { in madvise_vma()
383 return madvise_behavior(vma, prev, start, end, behavior); in madvise_vma()
388 madvise_behavior_valid(int behavior) in madvise_behavior_valid() argument
[all …]
DKconfig305 # and fixing that behavior (a second time; jbd2 doesn't have this problem) is
/linux-4.1.27/security/
Ddevice_cgroup.c51 enum devcg_behavior behavior; member
173 return (devcg->behavior != DEVCG_DEFAULT_NONE); in is_devcg_online()
191 dev_cgroup->behavior = DEVCG_DEFAULT_ALLOW; in devcgroup_online()
196 dev_cgroup->behavior = parent_dev_cgroup->behavior; in devcgroup_online()
208 dev_cgroup->behavior = DEVCG_DEFAULT_NONE; in devcgroup_offline()
224 dev_cgroup->behavior = DEVCG_DEFAULT_NONE; in devcgroup_css_alloc()
288 if (devcgroup->behavior == DEVCG_DEFAULT_ALLOW) { in devcgroup_seq_show()
399 enum devcg_behavior behavior) in verify_new_ex() argument
407 if (dev_cgroup->behavior == DEVCG_DEFAULT_ALLOW) { in verify_new_ex()
408 if (behavior == DEVCG_DEFAULT_ALLOW) { in verify_new_ex()
[all …]
/linux-4.1.27/Documentation/blackfin/
Dbfin-spi-notes.txt1 SPI Chip Select behavior:
10 behavior. If your SPI slave device in question requires SPI MODE_0 or MODE_2
13 the ones using mode 0 or 2 in order to guarantee correct CS toggling behavior.
Dbfin-gpio-notes.txt57 Some drivers, like gpio-keys, need this behavior. Kernel only print out
65 there is any abnormal driver behavior, please check the bfin-gpio
/linux-4.1.27/arch/xtensa/
DKconfig.debug20 The default linker behavior is to combine identical literal
30 Enable this option to test S32C1I instruction behavior at boot.
/linux-4.1.27/Documentation/cgroups/
Dmemcg_test.txt5 Because VM is getting complex (one of reasons is memcg...), memcg's behavior
6 is complex. This is a document for memcg's internal behavior.
91 But brief explanation of the behavior of memcg around shmem will be
129 (Memory behavior under GB and Memory behavior under MB shows very
Ddevices.txt66 group behavior exceptions
110 device cgroups is implemented internally using a behavior (ALLOW, DENY) and a
Dunified-hierarchy.txt208 happens between internal tasks and child cgroups and the behavior is
210 and knobs to tailor the behavior to specific workloads. Continuing
222 behavior. To achieve that, unified hierarchy enforces the following
335 basic desirable behavior. First off, the soft limit has no
/linux-4.1.27/arch/sh/drivers/
DKconfig10 behavior is platform-dependent, but normally the flash frequency is
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Datmel-matrix.txt4 behavior (master/slave priorities, undefined burst length type, ...)
/linux-4.1.27/Documentation/filesystems/
Djfs.txt12 iocharset=none specifies the default behavior explicitly.
27 previously specified in order to restore normal behavior.
Ddevpts.txt14 If CONFIG_DEVPTS_MULTIPLE_INSTANCES=n, there is no change in behavior and
125 initial kernel mount. This behavior while preserving legacy semantics,
Dbtrfs.txt59 These debugging options control the behavior of the integrity checking
71 checker module behavior.
126 operations). This was previously the behavior only when a snapshot is
Decryptfs.txt70 then behavior is undefined. Do not run eCryptfs in higher verbosity
Disofs.txt39 recreate previous unhide behavior
Ddebugfs.txt49 implement the file's behavior. At a minimum, the read() and/or write()
170 will be a lot of stale pointers and no end of highly antisocial behavior.
Dfuse.txt234 C) mount owner should not be able to induce undesired behavior in
262 undesired behavior in other users' processes, such as:
274 2) Even if 1) is solved the mount owner can change the behavior
Doverlayfs.txt178 Non-standard behavior
213 the behavior of the overlay is undefined, though it will not result in
Dvfat.txt145 -- specify FAT behavior on critical errors: panic, continue
147 read-only mode (default behavior).
Dext3.txt109 (These mount options override the errors behavior
Daffs.txt189 'nofilenametruncate' mount option can change that behavior.
Dspufs.txt33 The files in spufs mostly follow the standard behavior for regular sys-
238 These two files change the behavior of the signal1 and signal2 notifi-
Dsysfs.txt181 write. This forces the following behavior on the method
DLocking565 VM_FAULT_NOPAGE. Or one of the VM_FAULT_ERROR types. The default behavior
Drelay.txt109 that are available and some comments regarding their behavior:
Dext4.txt227 (These mount options override the errors behavior
/linux-4.1.27/Documentation/arm/
Dmem_alignment26 To change the alignment trap behavior, simply echo a number into
29 bit behavior when set
/linux-4.1.27/Documentation/
DDMA-attributes.txt33 behavior.
43 behavior.
69 attribute and exhibit default behavior.
Dbinfmt_misc.txt46 'P' - preserve-argv[0]. Legacy behavior of binfmt_misc is to overwrite
55 'O' - open-binary. Legacy behavior of binfmt_misc is to pass the full path
62 'C' - credentials. Currently, the behavior of binfmt_misc is to calculate
Dcpu-load.txt50 One can imagine many more situations where this behavior of the kernel
Dlockup-watchdogs.txt23 behavior is changed, which can be done through a compile time knob,
Dlocal_ops.txt43 not have a different behavior between SMP and UP, including asm-generic/local.h
Dgcov.txt126 This behavior can be deactivated by specifying the gcov_persist kernel
D00-INDEX83 - semantics and behavior of atomic and bitmask operations.
287 - semantics and behavior of local atomic operations.
Dsysfs-rules.txt34 application's behavior, but never try to search for sysfs. Never try
Dunshare.txt32 resources and thus they can achieve legacy "threads" behavior without
Dworkqueue.txt251 behavior. Work items on such wq are always queued to the unbound
DDMA-API-HOWTO.txt198 behavior. You must either use a different mask, or not use DMA.
350 in order to get correct behavior on all platforms.
Dxillybus.txt215 choice is a non-zero value, to match standard UNIX behavior.
DHOWTO140 about the unique behavior of kernel maintainers.
/linux-4.1.27/security/selinux/include/
Dobjsec.h65 unsigned short behavior; /* labeling behavior */ member
/linux-4.1.27/Documentation/ia64/
DIRQ-redir.txt7 controlled. The behavior on IA64 platforms is slightly different from
38 Initialization and default behavior:
Dfsys.txt233 would be the normal & expected behavior, so no special treatment is
/linux-4.1.27/drivers/parisc/
DREADME.dino5 ** the behavior of five models of HP VISUALIZE workstations when
/linux-4.1.27/Documentation/cdrom/
Dcdrom-standard.tex50 all these different devices has also allowed the behavior of each
52 This divergence of behavior has been very significant for \cdrom\
58 maintain uniform behavior across all the \linux\ \cdrom\ drivers.
60 This document describes an effort to establish Uniform behavior across
91 importantly, it appeared that the behavior of the `standard' commands
98 behavior was usually different.
114 {\em one\/} \linux\ \cdrom\ interface with consistent behavior for all
141 importantly, this led to the divergence of behavior, which has already
145 drive behavior, and to provide a common set of services to the various
186 place where the behavior of all \cdrom-devices is defined and
[all …]
/linux-4.1.27/Documentation/block/
Dwriteback_cache_control.txt11 behavior obviously speeds up various workloads, but it means the operating
16 control the caching behavior of the storage device. These mechanisms are
/linux-4.1.27/Documentation/sysctl/
Dkernel.txt162 Controls the kernel's callhome behavior in case of a kernel panic.
167 When the value in this file is 0 (which is the default behavior)
306 Controls the kernel's behavior when a hung task is detected.
309 0: continue operation. This is the default behavior.
555 Controls the kernel's behavior when detecting the overflows of
645 These values influence printk() behavior when printing or
794 Control how file position affects the behavior of updating sysctl values
801 0 - (default) Same behavior as above, but warn about processes that
814 This value controls the soft lockup detector thread's behavior
822 0: do nothing. This is the default behavior.
[all …]
Dfs.txt173 When set to "0", hardlink creation behavior is unrestricted.
192 When set to "0", symlink following behavior is unrestricted.
Dvm.txt717 sysctl, it will revert to this default behavior.
/linux-4.1.27/arch/mips/boot/dts/brcm/
Dbcm3384_viper.dtsi18 /* 1/2 of the CPU core clock (standard MIPS behavior) */
/linux-4.1.27/Documentation/hwmon/
Dw83l786ng19 behavior is no chip reset to preserve BIOS settings
Dw83791d33 The default behavior is to do the minimum initialization possible
41 behavior is no chip reset to preserve BIOS settings.
Dlm7835 as soon as it drops below the Hysteresis value. A more useful behavior
Dw83781d38 'reset=1' to restore the old behavior. Report if you need to do this.
78 it drops below the Hysteresis value. A more useful behavior
418 My mobo is an ASUS A7V266-E. This behavior is similar to what I got
Dds162152 As for the thermostat, behavior can also be programmed using the polarity
Dw83627ehf166 different behavior to bits 7 and 6, including extending the temperature
/linux-4.1.27/Documentation/misc-devices/
Dspear-pcie-gadget.txt31 read behavior of nodes:
44 write behavior of nodes:
/linux-4.1.27/Documentation/firmware_class/
DREADME18 High level behavior (mixed):
62 High level behavior (driver code):
/linux-4.1.27/Documentation/networking/
Dopenvswitch.txt60 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
Dmultiqueue.txt69 The behavior of tc filters remains the same. However a new tc action,
Dxfrm_sync.txt164 seen, then an odd behavior is seen as follows:
De100.txt154 Due to the default ARP behavior on Linux, it is not possible to have
Dixgb.txt188 behavior after modifying this register may be undefined (possibly errors of
391 Due to the default ARP behavior on Linux, it is not possible to have
Dip-sysctl.txt212 queue. Applications can still use TCP_CORK for optimal behavior
489 If set, provide RFC2861 behavior and time out the congestion
752 number 0). Explicit port allocation behavior is unchanged.
942 Currently, it is used to change the proxy_arp behavior:
1117 Define behavior for gratuitous ARP frames who's IP is not
1545 with IPv6 Neighbor Discovery) behavior:
DREADME.ipw2100134 There are several ways to control the behavior of the driver. Many of the
Dbonding.txt23 The behavior of the bonded interfaces depends upon the mode; generally
246 This behavior can be modified by the arp_validate option,
392 behavior), or, when enabled, perform special handling of the
538 option, documented below, affects the behavior of this
750 The default behavior of tlb mode is to shuffle active flows across
2211 destination to make load balancing decisions. The behavior of each
2414 Some switches exhibit undesirable behavior with regard to the
2483 The duplicated packet behavior is switch dependent, some
2485 behavior, it can be induced by clearing the MAC forwarding table (on
Daltera_tse.txt250 "rx_gte_1519_bytes" is a statistic defined specific to the behavior of the
Dixgbe.txt119 behavior is changed to off. Flow control in 1 gig mode on these devices can
Dl2tp.txt120 Userspace may control behavior of the tunnel or session using
Dtimestamping.txt354 Desired behavior is passed into the kernel and to a specific device by
Dcs89x0.txt312 l) If during DMA operation you find erratic behavior or network data
Dscaling.txt173 behavior indicates a problem such as a misconfiguration or spoofed
/linux-4.1.27/drivers/staging/android/
DKconfig11 POSIX SHM but with different behavior and sporting a simpler
/linux-4.1.27/security/smack/
DKconfig28 access rule set once the behavior is well understood.
/linux-4.1.27/drivers/media/v4l2-core/
DKconfig24 Only useful if you rely on the old behavior and use mknod instead of udev.
/linux-4.1.27/Documentation/device-mapper/
Dzero.txt5 zero'd data on reads and silently drops writes. This is similar behavior to
/linux-4.1.27/Documentation/devicetree/bindings/
Dcommon-properties.txt22 specify the default behavior if none of these properties are present.
/linux-4.1.27/Documentation/devicetree/bindings/serial/
D8250.txt51 pair of NS16550A), albeit with some nonstandard behavior such as
/linux-4.1.27/security/selinux/
Dhooks.c403 return sbsec->behavior == SECURITY_FS_USE_XATTR || in selinux_is_sblabel_mnt()
404 sbsec->behavior == SECURITY_FS_USE_TRANS || in selinux_is_sblabel_mnt()
405 sbsec->behavior == SECURITY_FS_USE_TASK || in selinux_is_sblabel_mnt()
406 sbsec->behavior == SECURITY_FS_USE_NATIVE || in selinux_is_sblabel_mnt()
421 if (sbsec->behavior == SECURITY_FS_USE_XATTR) { in sb_finish_set_opts()
447 if (sbsec->behavior > ARRAY_SIZE(labeling_behaviors)) in sb_finish_set_opts()
730 if (!sbsec->behavior) { in selinux_set_mnt_opts()
758 sbsec->behavior = SECURITY_FS_USE_NATIVE; in selinux_set_mnt_opts()
779 sbsec->behavior = SECURITY_FS_USE_MNTPOINT; in selinux_set_mnt_opts()
793 if (sbsec->behavior != SECURITY_FS_USE_XATTR && in selinux_set_mnt_opts()
[all …]
/linux-4.1.27/fs/quota/
DKconfig36 Note that this behavior is currently deprecated and may go away in
/linux-4.1.27/Documentation/input/
Dcs461x.txt21 behavior in my case was not raised the requirement of joystick calibration.
Dalps.txt11 have enough behavior differences that the alps_model_data definition
72 and more important in determining the behavior. This code has been
Dxpad.txt33 claimed dpad_to_buttons could be used to force behavior on known devices.
Devent-codes.txt293 accordingly. This property does not affect kernel behavior.
/linux-4.1.27/drivers/block/drbd/
DKconfig48 behavior.
/linux-4.1.27/security/selinux/ss/
Dpolicydb.h193 u32 behavior; /* labeling behavior for fs_use */ member
Dservices.c2386 sbsec->behavior = c->v.behavior; in security_fs_use()
2398 sbsec->behavior = SECURITY_FS_USE_NONE; in security_fs_use()
2401 sbsec->behavior = SECURITY_FS_USE_GENFS; in security_fs_use()
Dpolicydb.c2186 c->v.behavior = le32_to_cpu(buf[0]); in ocontext_read()
2188 if (c->v.behavior == SECURITY_FS_USE_MNTPOINT) in ocontext_read()
2190 if (c->v.behavior > SECURITY_FS_USE_MAX) in ocontext_read()
3120 buf[0] = cpu_to_le32(c->v.behavior); in ocontext_write()
/linux-4.1.27/Documentation/prctl/
Dseccomp_filter.txt35 behavior and information flow should be managed with a combination of
208 this is different from normal behavior. The tracer MUST NOT modify
214 To detect this quirky behavior, check for addr & ~0x0C00 ==
Dno_new_privs.txt42 execve and can change the behavior of newly-executed programs.
/linux-4.1.27/Documentation/sound/alsa/
DCMIPCI.txt92 "Line-In Mode" - an enum control to change the behavior of line-in
98 "Mic-In Mode" - an enum control to change the behavior of mic-in
253 problem (especially unexpected behavior of mixer), please attach the
DOSS-Emulation.txt119 In such a case, you can change the behavior of PCM per application by
165 The block and non-block options are used to change the behavior of
171 This blocking behavior can be changed globally via nonblock_open
DHD-Audio-Controls.txt14 This is an enum control to change the auto-mute behavior of the
Dtimestamping.txt175 wallclock, the timestamps show a monotonic behavior and a lower
DHD-Audio.txt421 matching better with the actual codec or device behavior. Many of
607 via power-saving behavior.
816 doesn't emulate the behavior with the real audio I/O, but it just
DAudiophile-Usb.txt88 The default behavior of the snd-usb-audio driver is to list the device
DALSA-Configuration.txt89 nonblock_open option is used to change the behavior of the PCM
252 -1 -- Default behavior.
611 behavior to each PCM device:
/linux-4.1.27/Documentation/i2c/
Di2c-stub34 4. observe its behavior in the kernel log
/linux-4.1.27/Documentation/video4linux/
Dcafe_ccic38 better behavior with mplayer can be achieved by setting to a higher
Dsi4713.txt17 properties which can change the behavior of this chip.
Dvivid.txt242 controls that select crop, compose and scale behavior are also
247 the driver behavior and test your application with all sorts of permutations.
265 but the long-term behavior is exactly following the framerate. So a
636 conversion). This behavior is also what you want, since a 75% Colorbar
716 Standard Signal Mode: selects the behavior of VIDIOC_QUERYSTD: what should
732 DV Timings Signal Mode: selects the behavior of VIDIOC_QUERY_DV_TIMINGS: what
/linux-4.1.27/Documentation/laptops/
Dasus-laptop.txt219 wapf: WAPF defines the behavior of the Fn+Fx wlan key
251 - the observed behavior of non-working features
Dthinkpad-acpi.txt60 - the observed behavior of non-working features
209 Note that unmasking some keys prevents their default behavior. For
644 (it simulates the behavior of Fn-F7).
703 effect and the behavior varies from model to model. Here is the behavior
819 and the sounds vary from model to model. Here is the behavior on the
/linux-4.1.27/Documentation/scheduler/
Dsched-deadline.txt14 4.3 Default behavior
26 system behavior. As for -rt (group) scheduling, it is assumed that root users
36 that makes it possible to isolate the behavior of tasks between each other.
127 timing behavior, e.g., multimedia, streaming, control applications, etc.
287 4.3 Default behavior
Dsched-bwc.txt36 bandwidth group. This represents the traditional work-conserving behavior for
Dsched-nice-design.txt61 accurately: the fact that nice level behavior depended on the _absolute_
Dcompletion.txt132 The default behavior is to wait without a timeout and to mark the task as
Dsched-design-CFS.txt102 interactivity and produce the expected behavior.
/linux-4.1.27/Documentation/ioctl/
Dcdrom.txt50 CDROM_SET_OPTIONS Set behavior options
51 CDROM_CLEAR_OPTIONS Clear behavior options
594 CDROM_SET_OPTIONS Set behavior options
619 CDROM_CLEAR_OPTIONS Clear behavior options
Dhdio.txt53 HDIO_SET_ACOUSTIC change acoustic behavior
998 HDIO_SET_ACOUSTIC change acoustic behavior
/linux-4.1.27/drivers/usb/core/
DKconfig64 rejected during enumeration. This behavior is required by the
/linux-4.1.27/drivers/scsi/aic7xxx/
DKconfig.aic79xx23 vary this number based on device behavior. For devices with a
DKconfig.aic7xxx28 vary this number based on device behavior. For devices with a
/linux-4.1.27/Documentation/scsi/
Dlpfc.txt54 community in modifying the behavior of the SCSI midlayer so that SCSI
Dosst.txt38 behavior looks very much the same as st to the userspace applications.
Dscsi_fc_transport.txt343 The expected behavior for the LLDD's vport_create() function is:
/linux-4.1.27/Documentation/cpuidle/
Dsysfs.txt87 The behavior and the effect of the disable variable depends on the
/linux-4.1.27/tools/perf/Documentation/
Dperf-timechart.txt6 perf-timechart - Tool to visualize total system behavior during a workload
Dperf-kvm.txt28 default behavior of perf kvm as --guest, so if neither --host nor --guest
Dperf-top.txt202 readability. 0 means no limit (default behavior).
Dperf-report.txt155 readability. 0 means no limit (default behavior).
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-class-devfreq51 This ABI shows the statistics of devfreq behavior on a
Dsysfs-block148 this behavior on one of two ways: When set to 1, complex
Dsysfs-bus-coresight-devices-etm3x233 programmed with the various implementation behavior in mind.
Dsysfs-kernel-slab9 files may be modified to change the behavior of the cache (and
/linux-4.1.27/Documentation/timers/
Dtimers-howto.txt76 is not the desired behavior.
Dhrtimers.txt116 The locking and per-CPU behavior of hrtimers was mostly taken from the
119 hrtimer functions now have clearer behavior and clearer names - such as
DNO_HZ.txt235 but do not see any change in your workload's behavior. Is this because
/linux-4.1.27/fs/ext3/
DKconfig22 behavior of ext3 file systems, you can use the tune2fs utility ("man
/linux-4.1.27/drivers/staging/unisys/Documentation/ABI/
Dsysfs-platform-visorchipset34 Description: The boottotool flag controls s-Par behavior on the next boot of
/linux-4.1.27/Documentation/vm/
Dnuma111 allocation behavior using Linux NUMA memory policy.
129 behavior. Rather they want to be sure they get memory from the specified node
Dnuma_memory_policy.txt140 optional set of nodes. The mode determines the behavior of the policy,
141 the optional mode flags determine the behavior of the mode, and the
143 behavior.
147 in context, below, as required to explain the behavior.
238 now allowed, the Default behavior is used.
Dbalance46 balancing problem, and stays as close to 2.2 behavior as possible. Also,
Dunevictable-lru.txt367 prior behavior of mlock() - before the unevictable/mlock changes -
458 behavior is to do so. /proc/sys/vm/compact_unevictable_allowed controls
459 this behavior (see Documentation/sysctl/vm.txt). Once scanning of the
Dcleancache.txt81 lock the page to ensure serial behavior.
Dtranshuge.txt183 behavior. So to make them effective you need to restart any
/linux-4.1.27/Documentation/PCI/
DPCIEBUS-HOWTO.txt173 behavior. For example, two service drivers run simultaneously on the
198 result unpredictable behavior. Service drivers should use
Dpcieaer-howto.txt54 behavior. To avoid this conflict, a successful load of the AER Root driver
/linux-4.1.27/Documentation/cpu-freq/
Dboost.txt81 For compatibility reasons this file and its behavior is still supported
Dgovernors.txt168 effect on behavior at lower speeds/lower CPU loads.
/linux-4.1.27/drivers/net/ethernet/realtek/
DKconfig101 old RX-reset behavior. If unsure, say N.
/linux-4.1.27/drivers/video/console/
DKconfig116 is the default behavior.
/linux-4.1.27/Documentation/isdn/
DREADME.audio84 General behavior and description of data formats/protocol.
/linux-4.1.27/Documentation/x86/
Dentry_64.txt95 triggers three main behavior changes:
/linux-4.1.27/arch/m68k/
DKconfig.devices15 behavior is platform-dependent, but normally the flash frequency is
/linux-4.1.27/Documentation/thermal/
Dintel_powerclamp.txt89 The following diagram shows the behavior of kernel thread
120 time is considered largely as a non-causal system where its behavior
/linux-4.1.27/drivers/firmware/
DKconfig21 bool "Sets default behavior for EDD detection to off"
/linux-4.1.27/Documentation/filesystems/nfs/
Dnfs.txt32 administrative requirements that require particular behavior that does not
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-tape.1995-200293 * Optimized shared interface behavior. The new behavior
/linux-4.1.27/Documentation/locking/
Dlocktorture.txt95 without pausing, which is the old default behavior.
/linux-4.1.27/Documentation/usb/
Ddma.txt78 behavior. Just don't override it; e.g. with NETIF_F_HIGHDMA.
Dpersist.txt29 For many sorts of devices this behavior doesn't matter in the least.
Dpower-management.txt189 from being autosuspended; the behavior was changed in 2.6.22. The
499 the kernel's behavior in this regard has changed. As of 2.6.37 the
/linux-4.1.27/Documentation/rapidio/
Dsysfs.txt51 This attribute is similar in behavior to the "config" attribute of PCI devices
/linux-4.1.27/Documentation/fault-injection/
Dfault-injection.txt29 Configure fault-injection capabilities behavior
/linux-4.1.27/Documentation/acpi/apei/
Deinj.txt80 If set to zero, legacy behavior is mimicked where the type of
/linux-4.1.27/net/ipv6/
DKconfig227 may sometimes lead to unintended routing behavior. This can be
/linux-4.1.27/Documentation/filesystems/cifs/
DCHANGES91 Various fixes to make delete of open files behavior more predictable
129 of mode (enable old behavior). Fix hang on mount caused when server crashes
341 Add mount option for disabling the default behavior of sending byte range lock
343 mandatory lock behavior such as Evolution), and also mount option for
489 override of the default uid behavior (in which the server sets the uid
711 Fix non-POSIX behavior on rename of open file and delete of open file by taking
/linux-4.1.27/arch/s390/kernel/
Dcompat_wrapper.c150 COMPAT_SYSCALL_WRAP3(madvise, unsigned long, start, size_t, len, int, behavior);
/linux-4.1.27/Documentation/power/
Dsuspend-and-interrupts.txt22 of suspended devices and cause unpredictable behavior to ensue as a result.
Duserland-swsusp.txt130 and order in which they have been read). Otherwise, the behavior of the
Dswsusp.txt427 root), the 2.6.15 behavior should be restored. If it is still too
/linux-4.1.27/fs/
DKconfig.binfmt61 The core dump behavior can be controlled per process using
/linux-4.1.27/Documentation/arm64/
Darm-acpi.txt37 -- ACPI’s bytecode (AML) allows the platform to encode hardware behavior,
39 able to encode behavior is a key tool used in supporting operating
136 command line; this is the default behavior.
Dacpi_object_usage.txt361 _HRV 6.1.6 Optional, use as needed to clarify device behavior; in
/linux-4.1.27/Documentation/virtual/kvm/
Dppc-pv.txt120 when entering the guest or don't have any impact on the hypervisor's behavior.
Dapi.txt43 not cause harm to the host, their actual behavior is not guaranteed by
439 and incurs unexpected behavior.
1643 and emulation of PCI 2.3 INTx disable command register behavior.
2457 for specifying any behavior that is not implied by the device type
3296 There are certain capabilities that change the behavior of the virtual CPU or
3372 boundedly undefined behavior.
3424 When disabled (args[0] == 0), behavior is as if this facility is unsupported.
3482 There are certain capabilities that change the behavior of the virtual
/linux-4.1.27/
DREPORTING-BUGS167 or userspace breakage caused by new kernel behavior. Those bugs should be
DMakefile686 KBUILD_CFLAGS += $(call cc-option, -fcatch-undefined-behavior)
/linux-4.1.27/fs/cifs/
DKconfig119 than Windows like) file behavior. It also enables
/linux-4.1.27/arch/x86/lib/
Dx86-opcode-map.txt276 # Note: "forced64" is Intel CPU behavior: they ignore 0x66 prefix
466 # Note: "forced64" is Intel CPU behavior (see comment about CALL insn).
853 # Note: "forced64" is Intel CPU behavior (see comment about CALL insn).
/linux-4.1.27/Documentation/blockdev/
Dfloppy.txt35 restore the default behavior.
/linux-4.1.27/Documentation/hid/
Dhiddev.txt89 behavior of the read() function can be modified using the HIDIOCSFLAG
Dhid-transport.txt76 transmission behavior regarding acknowledgements. An asynchronous channel must
/linux-4.1.27/tools/perf/
Dbuiltin-trace.c436 int behavior = arg->val; in syscall_arg__scnprintf_madvise_behavior() local
438 switch (behavior) { in syscall_arg__scnprintf_madvise_behavior()
470 return scnprintf(bf, size, "%#x", behavior); in syscall_arg__scnprintf_madvise_behavior()
/linux-4.1.27/arch/powerpc/platforms/
DKconfig265 bound. The default behavior is to show both the upper and lower
/linux-4.1.27/arch/tile/
DKconfig358 change this behavior.
/linux-4.1.27/Documentation/powerpc/
Dhvcs.txt277 When hvcs is being used to serve consoles this behavior is not a huge issue
281 because the standard Linux behavior when cat'ing or dd'ing data to a device
/linux-4.1.27/Documentation/m68k/
Dkernel-options.txt320 NBB: The behavior of video= was changed in 2.1.57 so the recommended
680 kernel (or compiled as loadable modules). The behavior of the <fbname>
864 Incorrect use can lead to unpredictable behavior, so please only use
/linux-4.1.27/Documentation/fb/
Dfbcon.txt75 that can change its behavior.
/linux-4.1.27/arch/cris/
DKconfig304 prompt "Network LED behavior"
/linux-4.1.27/drivers/base/
DKconfig53 mounted the root filesystem. The behavior can be overridden
/linux-4.1.27/net/
DKconfig73 behavior of the TCP/IP code by writing to the (virtual) files in
/linux-4.1.27/Documentation/RCU/
Dstallwarn.txt196 behavior, you might need to replace some of the cond_resched()
Dtorture.txt138 without pausing, which is the old default behavior.
/linux-4.1.27/Documentation/gpio/
Dconsumer.txt166 behavior!**
/linux-4.1.27/Documentation/nfc/
Dnfc-hci.txt25 let the HCI driver handle proprietary events or override standard behavior.
/linux-4.1.27/scripts/
Dspelling.txt155 bahavior||behavior
/linux-4.1.27/scripts/genksyms/
Dparse.tab.c_shipped1361 Don't have undefined behavior even if the translation
1695 This behavior is undocumented and Bison
/linux-4.1.27/include/linux/
Dsyscalls.h467 asmlinkage long sys_madvise(unsigned long start, size_t len, int behavior);
/linux-4.1.27/lib/
DKconfig.debug15 The behavior is also controlled by the kernel command line
476 SLUB statistics are useful to debug SLUBs allocation behavior in
850 scheduler behavior and provide them in /proc/schedstat. These
/linux-4.1.27/scripts/kconfig/
Dzconf.tab.c_shipped1286 Don't have undefined behavior even if the translation
1650 This behavior is undocumented and Bison
/linux-4.1.27/scripts/dtc/
Ddtc-parser.tab.c_shipped1192 Don't have undefined behavior even if the translation
1509 This behavior is undocumented and Bison
/linux-4.1.27/kernel/trace/
DKconfig297 Only enable it if you want to analyse the branching behavior.
/linux-4.1.27/Documentation/s390/
Ds390dbf.txt84 debug log. You can change the behavior using 2 sysctl parameters in
/linux-4.1.27/Documentation/trace/
Dring-buffer-design.txt67 enforces this behavior.
/linux-4.1.27/drivers/char/
DKconfig583 controlling the behavior of this hardware.
/linux-4.1.27/Documentation/development-process/
D2.Process186 to forget about code after merging it, that sort of behavior tends to
/linux-4.1.27/arch/blackfin/
DKconfig961 default behavior is to leave this set to on (type "Y"). If you are experiencing

12