| /kernel/linux/linux-5.10/security/ |
| D | device_cgroup.c | 45 enum devcg_behavior behavior; member
178 return (devcg->behavior != DEVCG_DEFAULT_NONE); in is_devcg_online()
196 dev_cgroup->behavior = DEVCG_DEFAULT_ALLOW; in devcgroup_online()
201 dev_cgroup->behavior = parent_dev_cgroup->behavior; in devcgroup_online()
213 dev_cgroup->behavior = DEVCG_DEFAULT_NONE; in devcgroup_offline()
229 dev_cgroup->behavior = DEVCG_DEFAULT_NONE; in devcgroup_css_alloc()
293 if (devcgroup->behavior == DEVCG_DEFAULT_ALLOW) { in devcgroup_seq_show()
405 enum devcg_behavior behavior) in verify_new_ex() argument
413 if (dev_cgroup->behavior == DEVCG_DEFAULT_ALLOW) { in verify_new_ex()
414 if (behavior == DEVCG_DEFAULT_ALLOW) { in verify_new_ex()
[all …]
|
| /kernel/linux/linux-5.10/drivers/pci/ |
| D | pci-bridge-emul.c | 367 const struct pci_bridge_reg_behavior *behavior; in pci_bridge_emul_conf_read() local
383 behavior = bridge->pcie_cap_regs_behavior; in pci_bridge_emul_conf_read()
387 behavior = bridge->pci_regs_behavior; in pci_bridge_emul_conf_read()
402 *value &= behavior[reg / 4].ro | behavior[reg / 4].rw | in pci_bridge_emul_conf_read()
403 behavior[reg / 4].w1c; in pci_bridge_emul_conf_read()
429 const struct pci_bridge_reg_behavior *behavior; in pci_bridge_emul_conf_write() local
456 behavior = bridge->pcie_cap_regs_behavior; in pci_bridge_emul_conf_write()
460 behavior = bridge->pci_regs_behavior; in pci_bridge_emul_conf_write()
464 new = old & (~mask | ~behavior[reg / 4].rw); in pci_bridge_emul_conf_write()
467 new |= (value << shift) & (behavior[reg / 4].rw & mask); in pci_bridge_emul_conf_write()
[all …]
|
| /kernel/linux/linux-5.10/mm/ |
| D | madvise.c | 49 static int madvise_need_mmap_write(int behavior) in madvise_need_mmap_write() argument
51 switch (behavior) { in madvise_need_mmap_write()
778 int behavior) in madvise_dontneed_free() argument
825 if (behavior == MADV_DONTNEED) in madvise_dontneed_free()
827 else if (behavior == MADV_FREE) in madvise_dontneed_free()
890 unsigned long behavior) in madvise_vma_behavior() argument
896 switch (behavior) { in madvise_vma_behavior()
907 return madvise_dontneed_free(vma, prev, start, end, behavior); in madvise_vma_behavior()
944 error = ksm_madvise(vma, start, end, behavior, &new_flags); in madvise_vma_behavior()
950 error = hugepage_madvise(vma, &new_flags, behavior); in madvise_vma_behavior()
[all …]
|
| /kernel/linux/linux-5.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()
|
| /kernel/liteos_a/kernel/extended/plimit/ |
| D | los_devicelimit.c | 47 deviceLimit->behavior = DEVLIMIT_DEFAULT_ALLOW; in OsDevLimitInit()
60 plimit->behavior = DEVLIMIT_DEFAULT_NONE; in OsDevLimitAlloc()
89 devLimitDest->behavior = devLimitSrc->behavior; in DevLimitCopyAccess()
175 return (parent->behavior == DEVLIMIT_DEFAULT_ALLOW); in DevLimitMayAllowAll()
213 devLimit->behavior = DEVLIMIT_DEFAULT_ALLOW; in DealItemAllAccess()
225 devLimit->behavior = DEVLIMIT_DEFAULT_DENY; in DealItemAllAccess()
299 if (parent->behavior == DEVLIMIT_DEFAULT_ALLOW) { in DevLimitVerifyNewItem()
375 if (!DevLimitParentAllowsAddItem(devParentLimit, walK, devLimit->behavior)) { in DevLimitRevalidateActiveItems()
409 if (devLimit->behavior == DEVLIMIT_DEFAULT_ALLOW && in DevLimitPropagateItem()
410 devLimitChild->behavior == DEVLIMIT_DEFAULT_ALLOW) { in DevLimitPropagateItem()
[all …]
|
| D | los_devicelimit.h | 79 enum DevLimitBehavior behavior; member
|
| /kernel/linux/linux-5.10/arch/parisc/kernel/ |
| D | sys_parisc.c | 459 asmlinkage notrace long parisc_madvise(unsigned long start, size_t len_in, int behavior) in parisc_madvise() argument
461 switch (behavior) { in parisc_madvise()
462 case 65: behavior = MADV_MERGEABLE; break; in parisc_madvise()
463 case 66: behavior = MADV_UNMERGEABLE; break; in parisc_madvise()
464 case 67: behavior = MADV_HUGEPAGE; break; in parisc_madvise()
465 case 68: behavior = MADV_NOHUGEPAGE; break; in parisc_madvise()
466 case 69: behavior = MADV_DONTDUMP; break; in parisc_madvise()
467 case 70: behavior = MADV_DODUMP; break; in parisc_madvise()
468 case 71: behavior = MADV_WIPEONFORK; break; in parisc_madvise()
469 case 72: behavior = MADV_KEEPONFORK; break; in parisc_madvise()
[all …]
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.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.
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.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.
|
| /kernel/linux/linux-5.10/scripts/selinux/mdp/ |
| D | mdp.c | 154 #define FS_USE(behavior, fstype) \ in main() argument
156 behavior, fstype, mls ? ":" SYSTEMLOW : "") in main()
|
| /kernel/linux/linux-5.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.
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.10/drivers/staging/android/ |
| D | Kconfig | 11 POSIX SHM but with different behavior and sporting a simpler
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | jfs.rst | 16 iocharset=none specifies the default behavior explicitly.
34 previously specified in order to restore normal behavior.
|
| /kernel/linux/linux-5.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,
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | mem_alignment.rst | 30 To change the alignment trap behavior, simply echo a number into
34 bit behavior when set
|
| /kernel/linux/linux-5.10/arch/sh/drivers/ |
| D | Kconfig | 11 behavior is platform-dependent, but normally the flash frequency is
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-da8xx-ddrctl.txt | 4 a set of registers which allow to tweak the controller's behavior.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | atmel-matrix.txt | 4 behavior (master/slave priorities, undefined burst length type, ...)
|
| /kernel/linux/linux-5.10/Documentation/ia64/ |
| D | irq-redir.rst | 9 controlled. The behavior on IA64 platforms is slightly different from
45 Initialization and default behavior
|
| /kernel/linux/linux-5.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
|