| /Linux-v5.4/drivers/gpu/drm/amd/amdgpu/ |
| D | gmc_v7_0.c | 746 u32 protections = REG_GET_FIELD(status, VM_CONTEXT1_PROTECTION_FAULT_STATUS, in gmc_v7_0_vm_decode_fault() local
756 protections, vmid, pasid, addr, in gmc_v7_0_vm_decode_fault()
1277 u32 protections = REG_GET_FIELD(status, in gmc_v7_0_process_interrupt() local
1287 info->prot_valid = protections & 0x7 ? true : false; in gmc_v7_0_process_interrupt()
1288 info->prot_read = protections & 0x8 ? true : false; in gmc_v7_0_process_interrupt()
1289 info->prot_write = protections & 0x10 ? true : false; in gmc_v7_0_process_interrupt()
1290 info->prot_exec = protections & 0x20 ? true : false; in gmc_v7_0_process_interrupt()
|
| D | gmc_v8_0.c | 990 u32 protections = REG_GET_FIELD(status, VM_CONTEXT1_PROTECTION_FAULT_STATUS, in gmc_v8_0_vm_decode_fault() local
1000 protections, vmid, pasid, addr, in gmc_v8_0_vm_decode_fault()
1462 u32 protections = REG_GET_FIELD(status, in gmc_v8_0_process_interrupt() local
1472 info->prot_valid = protections & 0x7 ? true : false; in gmc_v8_0_process_interrupt()
1473 info->prot_read = protections & 0x8 ? true : false; in gmc_v8_0_process_interrupt()
1474 info->prot_write = protections & 0x10 ? true : false; in gmc_v8_0_process_interrupt()
1475 info->prot_exec = protections & 0x20 ? true : false; in gmc_v8_0_process_interrupt()
|
| D | gmc_v6_0.c | 636 u32 protections = REG_GET_FIELD(status, VM_CONTEXT1_PROTECTION_FAULT_STATUS, in gmc_v6_0_vm_decode_fault() local
645 protections, vmid, addr, in gmc_v6_0_vm_decode_fault()
|
| /Linux-v5.4/Documentation/core-api/ |
| D | protection-keys.rst | 16 protections, but without requiring modification of the page tables
24 thread a different set of protections from every other thread.
|
| /Linux-v5.4/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.4/Documentation/admin-guide/LSM/ |
| D | Yama.rst | 6 protections that are not handled by the core kernel itself. This is
|
| /Linux-v5.4/Documentation/trace/ |
| D | ftrace-uses.rst | 33 The ftrace infrastructure has some protections against recursions and RCU
42 as well as what protections the callback will perform and not require
|
| /Linux-v5.4/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.4/Documentation/x86/ |
| D | intel_txt.rst | 152 - As one of the checks/protections provided by TXT, it makes a copy
|
| /Linux-v5.4/drivers/gpu/drm/radeon/ |
| D | ni.c | 2538 u32 protections = (status & PROTECTIONS_MASK) >> PROTECTIONS_SHIFT; in cayman_vm_decode_fault() local
2680 protections, vmid, addr, in cayman_vm_decode_fault()
|
| D | si.c | 4826 u32 protections = (status & PROTECTIONS_MASK) >> PROTECTIONS_SHIFT; in si_vm_decode_fault() local
5071 protections, vmid, addr, in si_vm_decode_fault()
|
| D | cik.c | 5669 u32 protections = (status & PROTECTIONS_MASK) >> PROTECTIONS_SHIFT; in cik_vm_decode_fault() local
5679 protections, vmid, addr, in cik_vm_decode_fault()
|
| /Linux-v5.4/arch/powerpc/ |
| D | Kconfig | 838 bool "Support setting protections for 4k subpages"
930 page-based protections, but without requiring modification of the
|
| /Linux-v5.4/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 362 These protections are added to score to judge whether this zone should be used
510 default this value is set to 0 and no protections will be enforced by the
|
| /Linux-v5.4/Documentation/vm/ |
| D | unevictable-lru.rst | 382 Because the VMA access protections could have been changed to PROT_NONE after
496 memory range accounted as locked_vm, as the protections could be changed later
|
| /Linux-v5.4/arch/ |
| D | Kconfig | 912 implementation, which can be (slightly) slower but provides protections
|
| /Linux-v5.4/lib/ |
| D | Kconfig.debug | 1888 tristate "Test user/kernel boundary protections"
1895 protections.
|
| /Linux-v5.4/Documentation/ |
| D | DMA-API-HOWTO.txt | 475 mappings can be marked with, much like page protections in the user
|
| /Linux-v5.4/arch/x86/ |
| D | Kconfig | 1528 page mappings when mapping protections are changed.
1936 page-based protections, but without requiring modification of the
|
| /Linux-v5.4/tools/memory-model/Documentation/ |
| D | explanation.txt | 382 The protections provided by READ_ONCE(), WRITE_ONCE(), and others are
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 628 As protections can be over-committed, all configuration combinations
|
| D | kernel-parameters.txt | 4462 the user space protections.
|
| /Linux-v5.4/Documentation/virt/uml/ |
| D | UserModeLinux-HOWTO.txt | 3171 of catching the culprit in the act, I had turned off all protections
|
