| /Linux-v5.15/drivers/gpu/drm/amd/amdgpu/ |
| D | gmc_v7_0.c | 779 u32 protections = REG_GET_FIELD(status, VM_CONTEXT1_PROTECTION_FAULT_STATUS, in gmc_v7_0_vm_decode_fault() local
789 protections, vmid, pasid, addr, in gmc_v7_0_vm_decode_fault()
1305 u32 protections = REG_GET_FIELD(status, in gmc_v7_0_process_interrupt() local
1315 info->prot_valid = protections & 0x7 ? true : false; in gmc_v7_0_process_interrupt()
1316 info->prot_read = protections & 0x8 ? true : false; in gmc_v7_0_process_interrupt()
1317 info->prot_write = protections & 0x10 ? true : false; in gmc_v7_0_process_interrupt()
1318 info->prot_exec = protections & 0x20 ? true : false; in gmc_v7_0_process_interrupt()
|
| D | gmc_v8_0.c | 1013 u32 protections = REG_GET_FIELD(status, VM_CONTEXT1_PROTECTION_FAULT_STATUS, in gmc_v8_0_vm_decode_fault() local
1023 protections, vmid, pasid, addr, in gmc_v8_0_vm_decode_fault()
1480 u32 protections = REG_GET_FIELD(status, in gmc_v8_0_process_interrupt() local
1490 info->prot_valid = protections & 0x7 ? true : false; in gmc_v8_0_process_interrupt()
1491 info->prot_read = protections & 0x8 ? true : false; in gmc_v8_0_process_interrupt()
1492 info->prot_write = protections & 0x10 ? true : false; in gmc_v8_0_process_interrupt()
1493 info->prot_exec = protections & 0x20 ? true : false; in gmc_v8_0_process_interrupt()
|
| D | gmc_v6_0.c | 619 u32 protections = REG_GET_FIELD(status, VM_CONTEXT1_PROTECTION_FAULT_STATUS, in gmc_v6_0_vm_decode_fault() local
628 protections, vmid, addr, in gmc_v6_0_vm_decode_fault()
|
| /Linux-v5.15/Documentation/core-api/ |
| D | protection-keys.rst | 17 protections, but without requiring modification of the page tables
25 thread a different set of protections from every other thread.
|
| D | dma-api-howto.rst | 475 mappings can be marked with, much like page protections in the user
|
| /Linux-v5.15/Documentation/ABI/obsolete/ |
| D | sysfs-selinux-checkreqprot | 20 check the actual protections being applied upon mmap/mprotect calls.
|
| /Linux-v5.15/Documentation/security/ |
| D | self-protection.rst | 150 kind of attack exist, and protections exist to defend against them.
169 important changes need to be made for better protections: moving the
199 While many protections can be considered deterministic (e.g. read-only
200 memory cannot be written to), some protections provide only statistical
|
| /Linux-v5.15/Documentation/admin-guide/LSM/ |
| D | Yama.rst | 6 protections that are not handled by the core kernel itself. This is
|
| /Linux-v5.15/Documentation/x86/x86_64/ |
| D | fsgs.rst | 19 limits. The limits can be used to enforce address space protections.
|
| /Linux-v5.15/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 332 - The swapgs protections are disabled; otherwise it has
340 However, the protections are put in place on a case by case basis,
583 the user space protections.
|
| D | mds.rst | 211 have their own protections.
|
| D | l1tf.rst | 89 The fact that L1TF breaks all domain protections allows malicious guest
|
| /Linux-v5.15/Documentation/x86/ |
| D | intel_txt.rst | 152 - As one of the checks/protections provided by TXT, it makes a copy
|
| /Linux-v5.15/drivers/gpu/drm/radeon/ |
| D | ni.c | 2523 u32 protections = (status & PROTECTIONS_MASK) >> PROTECTIONS_SHIFT; in cayman_vm_decode_fault() local
2665 protections, vmid, addr, in cayman_vm_decode_fault()
|
| D | si.c | 4821 u32 protections = (status & PROTECTIONS_MASK) >> PROTECTIONS_SHIFT; in si_vm_decode_fault() local
5066 protections, vmid, addr, in si_vm_decode_fault()
|
| D | cik.c | 5656 u32 protections = (status & PROTECTIONS_MASK) >> PROTECTIONS_SHIFT; in cik_vm_decode_fault() local
5666 protections, vmid, addr, in cik_vm_decode_fault()
|
| /Linux-v5.15/Documentation/trace/ |
| D | ftrace-uses.rst | 42 as well as what protections the callback will perform and not require
|
| /Linux-v5.15/Documentation/vm/ |
| D | unevictable-lru.rst | 376 Because the VMA access protections could have been changed to PROT_NONE after
490 memory range accounted as locked_vm, as the protections could be changed later
|
| /Linux-v5.15/Documentation/locking/ |
| D | locktypes.rst | 77 can have suffixes which apply further protections:
|
| /Linux-v5.15/tools/objtool/Documentation/ |
| D | stack-validation.txt | 307 access user space pages with protections against doing so disabled.
|
| /Linux-v5.15/arch/powerpc/ |
| D | Kconfig | 839 bool "Support setting protections for 4k subpages (subpage_prot syscall)"
943 page-based protections, but without requiring modification of the
|
| /Linux-v5.15/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 375 These protections are added to score to judge whether this zone should be used
523 default this value is set to 0 and no protections will be enforced by the
|
| /Linux-v5.15/lib/ |
| D | Kconfig.debug | 2277 tristate "Test user/kernel boundary protections"
2284 protections.
|
| /Linux-v5.15/arch/x86/ |
| D | Kconfig | 1510 page mappings when mapping protections are changed.
1845 page-based protections, but without requiring modification of the
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 644 As protections can be over-committed, all configuration combinations
|
