| /Linux-v6.1/drivers/gpu/drm/amd/amdgpu/ |
| D | gmc_v7_0.c | 775 u32 protections = REG_GET_FIELD(status, VM_CONTEXT1_PROTECTION_FAULT_STATUS, in gmc_v7_0_vm_decode_fault() local
785 protections, vmid, pasid, addr, in gmc_v7_0_vm_decode_fault()
1304 u32 protections = REG_GET_FIELD(status, in gmc_v7_0_process_interrupt() local
1314 info->prot_valid = protections & 0x7 ? true : false; in gmc_v7_0_process_interrupt()
1315 info->prot_read = protections & 0x8 ? true : false; in gmc_v7_0_process_interrupt()
1316 info->prot_write = protections & 0x10 ? true : false; in gmc_v7_0_process_interrupt()
1317 info->prot_exec = protections & 0x20 ? true : false; in gmc_v7_0_process_interrupt()
|
| D | gmc_v8_0.c | 1015 u32 protections = REG_GET_FIELD(status, VM_CONTEXT1_PROTECTION_FAULT_STATUS, in gmc_v8_0_vm_decode_fault() local
1025 protections, vmid, pasid, addr, in gmc_v8_0_vm_decode_fault()
1485 u32 protections = REG_GET_FIELD(status, in gmc_v8_0_process_interrupt() local
1495 info->prot_valid = protections & 0x7 ? true : false; in gmc_v8_0_process_interrupt()
1496 info->prot_read = protections & 0x8 ? true : false; in gmc_v8_0_process_interrupt()
1497 info->prot_write = protections & 0x10 ? true : false; in gmc_v8_0_process_interrupt()
1498 info->prot_exec = protections & 0x20 ? true : false; in gmc_v8_0_process_interrupt()
|
| D | gmc_v6_0.c | 615 u32 protections = REG_GET_FIELD(status, VM_CONTEXT1_PROTECTION_FAULT_STATUS, in gmc_v6_0_vm_decode_fault() local
624 protections, vmid, addr, in gmc_v6_0_vm_decode_fault()
|
| /Linux-v6.1/Documentation/core-api/ |
| D | protection-keys.rst | 8 protections, but without requiring modification of the page tables when an
24 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-v6.1/Documentation/ABI/obsolete/ |
| D | sysfs-selinux-checkreqprot | 20 check the actual protections being applied upon mmap/mprotect calls.
|
| /Linux-v6.1/arch/arm64/boot/dts/qcom/ |
| D | sc7280-chrome-common.dtsi | 5 * This file mainly tries to abstract out the memory protections put into
|
| /Linux-v6.1/Documentation/mm/ |
| D | vmalloced-kernel-stacks.rst | 89 protections.
92 with PAGE_KERNEL protections.
|
| /Linux-v6.1/Documentation/security/ |
| D | self-protection.rst | 149 kind of attack exist, and protections exist to defend against them.
168 important changes need to be made for better protections: moving the
198 While many protections can be considered deterministic (e.g. read-only
199 memory cannot be written to), some protections provide only statistical
|
| /Linux-v6.1/Documentation/admin-guide/LSM/ |
| D | Yama.rst | 6 protections that are not handled by the core kernel itself. This is
|
| /Linux-v6.1/Documentation/x86/ |
| D | tdx.rst | 99 Private memory receives full TDX protections. Its content is protected
102 protections.
|
| D | intel_txt.rst | 152 - As one of the checks/protections provided by TXT, it makes a copy
|
| /Linux-v6.1/Documentation/x86/x86_64/ |
| D | fsgs.rst | 19 limits. The limits can be used to enforce address space protections.
|
| /Linux-v6.1/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 345 - The swapgs protections are disabled; otherwise it has
353 However, the protections are put in place on a case by case basis,
605 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-v6.1/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-v6.1/Documentation/trace/ |
| D | ftrace-uses.rst | 42 as well as what protections the callback will perform and not require
|
| /Linux-v6.1/Documentation/locking/ |
| D | locktypes.rst | 77 can have suffixes which apply further protections:
|
| /Linux-v6.1/arch/powerpc/ |
| D | Kconfig | 880 bool "Support setting protections for 4k subpages (subpage_prot syscall)"
985 page-based protections, but without requiring modification of the
|
| /Linux-v6.1/tools/objtool/Documentation/ |
| D | objtool.txt | 385 access user space pages with protections against doing so disabled.
|
| /Linux-v6.1/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 376 These protections are added to score to judge whether this zone should be used
524 default this value is set to 0 and no protections will be enforced by the
|
| /Linux-v6.1/lib/ |
| D | Kconfig.debug | 2332 tristate "Test user/kernel boundary protections"
2339 protections.
|
