Searched full:restrictions (Results 1 – 25 of 131) sorted by relevance
123456
| /Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 22 exceptional buggy platforms, special restrictions and exceptions should be
23 taken into account. This document describes the restrictions and the
27 Restrictions of the returning value of the _LID control method
39 Restrictions of the lid state change notifications
|
| /Documentation/gpu/amdgpu/display/ |
| D | mpo-overview.rst | 62 every DCN has different restrictions; here, we are just trying to provide the
65 Plane Restrictions
68 AMDGPU imposes restrictions on the use of DRM planes in the driver.
71 restrictions:
83 Cursor Restrictions
86 Before we start to describe some restrictions around cursor and MPO, see the
184 many more restrictions for a multi-display scenario. The below example shows a
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | msi.txt | 22 MSI controllers may have restrictions on permitted payloads.
70 If a device has restrictions on the allocation of MSIs, these restrictions
|
| /Documentation/gpu/rfc/ |
| D | i915_small_bar.rst | 37 Error Capture restrictions
39 With error capture we have two new restrictions:
|
| D | i915_small_bar.h | 110 * page-size restrictions (larger than 4K), like for device local-memory.
165 * such there are zero restrictions on where the object can be placed.
|
| /Documentation/admin-guide/ |
| D | abi-stable.rst | 7 restrictions, and backward compatibility for them will be guaranteed
|
| D | edid.rst | 22 restrictions later on.
|
| /Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 6 system-wide allowlist. These restrictions also prohibit the given UIDs/GIDs
37 additional restrictions imposed by this LSM would mean it is a "safer" version
114 setgroups() calls for processes with CAP_SETGID restrictions. Until we add
116 policies add no meaningful security. setgroups() restrictions will be enforced
|
| D | Yama.rst | 45 restrictions, it can call ``prctl(PR_SET_PTRACER, PR_SET_PTRACER_ANY, ...)``
75 The original children-only logic was based on the restrictions in grsecurity.
|
| D | apparmor.rst | 33 For AppArmor to enforce any restrictions beyond standard Linux DAC permissions
|
| D | LoadPin.rst | 10 restrictions without needing to sign the files individually.
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-system-xen_cpu | 20 logic restrictions and assumptions.
|
| /Documentation/userspace-api/ |
| D | landlock.rst | 58 space may not know each other's supported restrictions), hence the need
221 security policy; only adding more restrictions is allowed. These threads are
294 restrictions from its parent. This is similar to seccomp inheritance (cf.
307 Ptrace restrictions
311 then be subject to additional restrictions when manipulating another process.
319 Similar to the implicit `Ptrace restrictions`_, we may want to further restrict
479 Threads sandboxed with filesystem restrictions cannot modify filesystem
492 restricted. However, thanks to the `ptrace restrictions`_, access to such
545 restrict access to files, also implies inheritance of the ruleset restrictions
672 Using user space processes to enforce restrictions on kernel resources can lead
[all …]
|
| /Documentation/mm/ |
| D | highmem.rst | 88 come with restrictions about the pointers validity. Contrary to kmap()
108 restrictions imposed on kmap_local_page(). Furthermore, the code between
134 restrictions imposed on kmap_local_page(). In particular, it is necessary to
141 restrictions on preemption or migration. It comes with an overhead as mapping
|
| /Documentation/core-api/ |
| D | memory-allocation.rst | 84 driver for a device with such restrictions, avoid using these flags.
85 And even with hardware with restrictions it is preferable to use
164 will be retried with `vmalloc`. There are restrictions on which GFP
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | samsung,battery.yaml | 16 the physical restrictions make it impossible to use another battery with the
|
| /Documentation/arch/powerpc/ |
| D | vas-api.rst | 105 error codes and restrictions.
162 restrictions.
174 Only restrictions on mmap for a NX-GZIP device fd are:
179 Refer to mmap(2) man page for additional details/restrictions.
|
| /Documentation/misc-devices/ |
| D | xilinx_sdfec.rst | 138 Setting the order can only be done if the following restrictions are met:
155 Adding LDPC codes can only be done if the following restrictions are met:
166 Adding Turbo decode can only be done if the following restrictions are met:
186 Bypassing the SD-FEC can only be done if the following restrictions are met:
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | common.yaml | 33 due to restrictions in a specific system, such as mounting conditions.
|
| /Documentation/security/ |
| D | landlock.rst | 22 on the system, only add more restrictions.
91 Userspace tests for backward compatibility, ptrace restrictions and filesystem
|
| /Documentation/devicetree/bindings/pwm/ |
| D | pwm-sifive.yaml | 16 run at the same period. The period also has significant restrictions on
|
| /Documentation/devicetree/bindings/mtd/ |
| D | vf610-nfc.txt | 17 there might be restrictions on maximum rates when using hardware ECC.
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | cpm.txt | 40 Ranges must be set up subject to the following restrictions:
|
| /Documentation/networking/devlink/ |
| D | devlink-resource.rst | 8 can allow administrators to see the device restrictions for a given
|
| /Documentation/gpu/ |
| D | vkms.rst | 186 Atomic drivers have lots of restrictions which are not exposed to userspace in
192 implement a library of different restrictions.
|
123456