| /Linux-v5.10/security/ |
| D | device_cgroup.c | 45 enum devcg_behavior behavior; member
167 return (devcg->behavior != DEVCG_DEFAULT_NONE); in is_devcg_online()
185 dev_cgroup->behavior = DEVCG_DEFAULT_ALLOW; in devcgroup_online()
190 dev_cgroup->behavior = parent_dev_cgroup->behavior; in devcgroup_online()
202 dev_cgroup->behavior = DEVCG_DEFAULT_NONE; in devcgroup_offline()
218 dev_cgroup->behavior = DEVCG_DEFAULT_NONE; in devcgroup_css_alloc()
282 if (devcgroup->behavior == DEVCG_DEFAULT_ALLOW) { in devcgroup_seq_show()
394 enum devcg_behavior behavior) in verify_new_ex() argument
402 if (dev_cgroup->behavior == DEVCG_DEFAULT_ALLOW) { in verify_new_ex()
403 if (behavior == DEVCG_DEFAULT_ALLOW) { in verify_new_ex()
[all …]
|
| /Linux-v5.10/drivers/pci/ |
| D | pci-bridge-emul.c | 324 const struct pci_bridge_reg_behavior *behavior; in pci_bridge_emul_conf_read() local
340 behavior = bridge->pcie_cap_regs_behavior; in pci_bridge_emul_conf_read()
344 behavior = bridge->pci_regs_behavior; in pci_bridge_emul_conf_read()
359 *value &= behavior[reg / 4].ro | behavior[reg / 4].rw | in pci_bridge_emul_conf_read()
360 behavior[reg / 4].w1c; in pci_bridge_emul_conf_read()
386 const struct pci_bridge_reg_behavior *behavior; in pci_bridge_emul_conf_write() local
413 behavior = bridge->pcie_cap_regs_behavior; in pci_bridge_emul_conf_write()
417 behavior = bridge->pci_regs_behavior; in pci_bridge_emul_conf_write()
421 new = old & (~mask | ~behavior[reg / 4].rw); in pci_bridge_emul_conf_write()
424 new |= (value << shift) & (behavior[reg / 4].rw & mask); in pci_bridge_emul_conf_write()
[all …]
|
| /Linux-v5.10/mm/ |
| D | madvise.c | 47 static int madvise_need_mmap_write(int behavior) in madvise_need_mmap_write() argument
49 switch (behavior) { in madvise_need_mmap_write()
69 unsigned long start, unsigned long end, int behavior) in madvise_behavior() argument
76 switch (behavior) { in madvise_behavior()
119 error = ksm_madvise(vma, start, end, behavior, &new_flags); in madvise_behavior()
125 error = hugepage_madvise(vma, &new_flags, behavior); in madvise_behavior()
769 int behavior) in madvise_dontneed_free() argument
816 if (behavior == MADV_DONTNEED) in madvise_dontneed_free()
818 else if (behavior == MADV_FREE) in madvise_dontneed_free()
877 static int madvise_inject_error(int behavior, in madvise_inject_error() argument
[all …]
|
| /Linux-v5.10/tools/perf/trace/beauty/ |
| D | mmap.c | 65 static size_t madvise__scnprintf_behavior(int behavior, char *bf, size_t size) in madvise__scnprintf_behavior() argument
70 …if (behavior < strarray__madvise_advices.nr_entries && strarray__madvise_advices.entries[behavior]… in madvise__scnprintf_behavior()
71 return scnprintf(bf, size, "MADV_%s", strarray__madvise_advices.entries[behavior]); in madvise__scnprintf_behavior()
73 return scnprintf(bf, size, "%#", behavior); in madvise__scnprintf_behavior()
|
| /Linux-v5.10/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
|
| /Linux-v5.10/Documentation/admin-guide/device-mapper/ |
| D | dm-dust.rst | 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
71 Check the status of the read behavior ("bypass" indicates that all I/O
111 To enable the "fail read on bad block" behavior, send the "enable" message::
129 therefore emulating the "remap" behavior of hard disk drives::
302 This target seeks to provide a device that can exhibit the behavior
|
| /Linux-v5.10/Documentation/core-api/ |
| D | memory-allocation.rst | 32 The GFP flags control the allocators behavior. They tell what memory
87 GFP flags and reclaim behavior
112 **default** page allocator behavior is used. That means that not costly
114 that behavior so failures have to be checked properly by callers
117 * ``GFP_KERNEL | __GFP_NORETRY`` - overrides the default allocator behavior
123 behavior and all allocation requests try really hard. The request
127 * ``GFP_KERNEL | __GFP_NOFAIL`` - overrides the default allocator behavior
|
| /Linux-v5.10/arch/xtensa/ |
| D | Kconfig.debug | 18 The default linker behavior is to combine identical literal
28 Enable this option to test S32C1I instruction behavior at boot.
|
| /Linux-v5.10/Documentation/powerpc/ |
| D | syscall64-abi.rst | 74 Syscall behavior can change if the processor is in transactional or suspended
75 transaction state, and the syscall can affect the behavior of the transaction.
84 behavior depends on the presence of PPC_FEATURE2_HTM_NOSC in the AT_HWCAP2 ELF
95 behavior should not be relied upon.
|
| /Linux-v5.10/scripts/selinux/mdp/ |
| D | mdp.c | 154 #define FS_USE(behavior, fstype) \ in main() argument
156 behavior, fstype, mls ? ":" SYSTEMLOW : "") in main()
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | drivetemp.rst | 38 drives as well. The same behavior is observed if the 'hdtemp' or 'smartd'
44 drives experience similar behavior.
|
| /Linux-v5.10/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
|
| /Linux-v5.10/drivers/staging/android/ |
| D | Kconfig | 11 POSIX SHM but with different behavior and sporting a simpler
|
| /Linux-v5.10/Documentation/arm/ |
| D | mem_alignment.rst | 30 To change the alignment trap behavior, simply echo a number into
34 bit behavior when set
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | jfs.rst | 16 iocharset=none specifies the default behavior explicitly.
34 previously specified in order to restore normal behavior.
|
| /Linux-v5.10/tools/testing/selftests/futex/ |
| D | README | 6 Functional tests shall test the documented behavior of the futex operation
7 code under test. This includes checking for proper behavior under normal use,
|
| /Linux-v5.10/tools/kvm/kvm_stat/ |
| D | kvm_stat.txt | 18 This tool is useful for observing guest behavior from the host perspective.
19 Often conclusions about performance or buggy behavior can be drawn from the
|
| /Linux-v5.10/arch/sh/drivers/ |
| D | Kconfig | 11 behavior is platform-dependent, but normally the flash frequency is
|
| /Linux-v5.10/Documentation/devicetree/bindings/mfd/ |
| D | atmel-matrix.txt | 4 behavior (master/slave priorities, undefined burst length type, ...)
|
| /Linux-v5.10/Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-da8xx-ddrctl.txt | 4 a set of registers which allow to tweak the controller's behavior.
|
| /Linux-v5.10/Documentation/ia64/ |
| D | irq-redir.rst | 9 controlled. The behavior on IA64 platforms is slightly different from
45 Initialization and default behavior
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | dev-kmsg | 63 the special behavior this device has. The device allows to read
67 Because of the non-standard behavior also the error values are
69 is returned for other operations, e.g. SEEK_CUR. This behavior
|
| /Linux-v5.10/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
165 place where the behavior of all CD-ROM-devices is defined and
[all …]
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | virtiofs.rst | 48 atime behavior
52 are ignored. The atime behavior for virtiofs is the same as the
|
| /Linux-v5.10/Documentation/ABI/obsolete/ |
| D | sysfs-class-dax | 14 2. Enforces deterministic behavior by being strict about
|
