Searched full:privilege (Results 1 – 25 of 53) sorted by relevance
123
| /Documentation/devicetree/bindings/powerpc/ |
| D | ibm,powerpc-cpu-features.txt | 13 enablement, privilege, and compatibility metadata.
94 - usable-privilege
104 This property describes the privilege levels and/or software components
118 This property describes the HV privilege support required to enable the
119 feature to lesser privilege levels. If the property does not exist then no
137 This property describes the OS privilege support required to enable the
138 feature to lesser privilege levels. If the property does not exist then no
179 This property may exist when the usable-privilege property value has PR bit set.
213 usable-privilege = <1 | 2 | 4>;
219 usable-privilege = <1 | 2>;
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | riscv,imsics.yaml | 18 for each privilege level (machine or supervisor). The configuration of
22 which is same for given privilege level across CPUs (or HARTs).
25 for each privilege level (machine or supervisor) which collectively describe
26 IMSIC interrupt files at that privilege level across CPUs (or HARTs).
33 privilege level (machine or supervisor) encodes group index, HART index,
|
| D | sifive,plic-1.0.0.yaml | 17 A hart context is a privilege mode in a hardware execution thread. For example,
19 privilege modes per hart; machine mode and supervisor mode.
|
| /Documentation/userspace-api/ |
| D | no_new_privs.rst | 26 promises not to grant the privilege to do anything that could not have
41 Note that ``no_new_privs`` does not prevent privilege changes that do not
|
| D | spec_ctrl.rst | 7 privilege domains.
|
| /Documentation/devicetree/bindings/bus/ |
| D | st,stm32mp25-rifsc.yaml | 21 any security domains (secure, privilege, compartment).
30 security domains (secure, privilege, compartment).
|
| /Documentation/devicetree/bindings/arm/firmware/ |
| D | sdei.txt | 11 privilege level of the SDEI firmware (specified as part of the binding
|
| /Documentation/ABI/testing/ |
| D | configfs-tsm | 83 different privilege levels, like SEV-SNP "VMPL", specify the
84 privilege level via this attribute. The minimum acceptable
|
| /Documentation/arch/x86/ |
| D | amd-memory-encryption.rst | 135 SNP provides a feature called Virtual Machine Privilege Levels (VMPL) which
136 defines four privilege levels at which guest software can run. The most
139 Privilege Levels", docID: 24593.
|
| /Documentation/driver-api/firmware/ |
| D | other_interfaces.rst | 24 Some features of the Intel Stratix10 SoC require a level of privilege
|
| /Documentation/admin-guide/LSM/ |
| D | Smack.rst | 425 Privilege:
427 policy is said to have privilege. As of this writing a task can
428 have privilege either by possessing capabilities or by having an
614 only be changed by a process with privilege.
616 Privilege section in Smack Basics
779 privilege.
793 program has appropriate privilege::
798 packets will be checked if the program has appropriate privilege.
|
| D | SafeSetID.rst | 72 initial system user namespace, affectively preventing privilege escalation.
|
| /Documentation/arch/powerpc/ |
| D | ultravisor.rst | 26 | Privilege States |
68 * The privilege of a process is now determined by three MSR bits,
70 from least privilege to highest privilege. The higher privilege
71 modes can access all the resources of the lower privilege modes.
76 | S | HV| PR|Privilege |
90 | S | HV| PR|Privilege |
|
| D | dexcr.rst | 169 - The process does not have sufficient privilege to perform the operation.
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 34 dictated to the privilege models managed by GenieZone hypervisor for security
|
| /Documentation/admin-guide/hw-vuln/ |
| D | srso.rst | 10 tricking the elevated privilege domain (the kernel) into leaking
96 privilege domain crossings (User->Kernel, Guest->Host).
|
| D | gather_data_sampling.rst | 39 lower-privilege contexts like guests and when running outside SGX enclaves.
|
| /Documentation/admin-guide/sysctl/ |
| D | fs.rst | 194 is to cross privilege boundaries when following a given hardlink (i.e. a
230 is to cross privilege boundaries when following a given symlink (i.e. a
252 privilege levels or is execute only will not be dumped.
|
| /Documentation/security/ |
| D | credentials.rst | 238 * UNIX exec privilege escalation bits (SUID/SGID);
239 * File capabilities exec privilege escalation bits.
243 privilege escalation bits come into play, and may allow the resulting process
550 To avoid "confused deputy" privilege escalation attacks, access control checks
|
| D | snp-tdx-threat-model.rst | 173 privilege to create, destroy, or pause the guest, part of the goal of
239 --> guest kernel privilege escalation. This includes traditional
|
| /Documentation/arch/x86/x86_64/ |
| D | fred.rst | 11 privilege level (ring transitions). The FRED architecture was
|
| /Documentation/arch/parisc/ |
| D | registers.rst | 70 H (Higher-privilege trap) 0
71 L (Lower-privilege trap) 0
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 86 frozen by a user with root privilege.
|
| /Documentation/core-api/ |
| D | dma-attributes.rst | 130 subsystem that the buffer is fully accessible at the elevated privilege
|
| /Documentation/devicetree/bindings/arm/ |
| D | psci.yaml | 21 Functions are invoked by trapping to the privilege level of the PSCI
|
123