| /linux-6.3-rc2/drivers/cxl/ |
| A D | acpi.c | 123 static unsigned long cfmws_to_decoder_flags(int restrictions) in cfmws_to_decoder_flags() argument
127 if (restrictions & ACPI_CEDT_CFMWS_RESTRICT_TYPE2) in cfmws_to_decoder_flags()
129 if (restrictions & ACPI_CEDT_CFMWS_RESTRICT_TYPE3) in cfmws_to_decoder_flags()
131 if (restrictions & ACPI_CEDT_CFMWS_RESTRICT_VOLATILE) in cfmws_to_decoder_flags()
133 if (restrictions & ACPI_CEDT_CFMWS_RESTRICT_PMEM) in cfmws_to_decoder_flags()
135 if (restrictions & ACPI_CEDT_CFMWS_RESTRICT_FIXED) in cfmws_to_decoder_flags()
260 cxld->flags = cfmws_to_decoder_flags(cfmws->restrictions); in cxl_parse_cfmws()
|
| /linux-6.3-rc2/Documentation/gpu/rfc/ |
| A D | i915_small_bar.rst | 37 Error Capture restrictions
39 With error capture we have two new restrictions:
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/interrupt-controller/ |
| A 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
|
| /linux-6.3-rc2/Documentation/admin-guide/ |
| A D | abi-stable.rst | 7 restrictions, and backward compatibility for them will be guaranteed
|
| /linux-6.3-rc2/tools/testing/cxl/test/ |
| A D | cxl.c | 206 .restrictions = ACPI_CEDT_CFMWS_RESTRICT_TYPE3 |
221 .restrictions = ACPI_CEDT_CFMWS_RESTRICT_TYPE3 |
236 .restrictions = ACPI_CEDT_CFMWS_RESTRICT_TYPE3 |
251 .restrictions = ACPI_CEDT_CFMWS_RESTRICT_TYPE3 |
266 .restrictions = ACPI_CEDT_CFMWS_RESTRICT_TYPE3 |
281 .restrictions = ACPI_CEDT_CFMWS_RESTRICT_TYPE3 |
298 .restrictions = ACPI_CEDT_CFMWS_RESTRICT_TYPE3 |
314 .restrictions = ACPI_CEDT_CFMWS_RESTRICT_TYPE3 |
330 .restrictions = ACPI_CEDT_CFMWS_RESTRICT_TYPE3 |
|
| /linux-6.3-rc2/Documentation/userspace-api/ |
| A D | landlock.rst | 43 kernel and user space may not know each other's supported restrictions), hence
173 security policy; only adding more restrictions is allowed. These threads are
246 restrictions from its parent. This is similar to the seccomp inheritance (cf.
259 Ptrace restrictions
263 then be subject to additional restrictions when manipulating another process.
403 restricted. However, thanks to the `ptrace restrictions`_, access to such
434 restrict access to files, also implies inheritance of the ruleset restrictions
478 Using user space process to enforce restrictions on kernel resources can lead
488 fine-grained restrictions). Moreover, their complexity can lead to security
|
| /linux-6.3-rc2/Documentation/ABI/testing/ |
| A D | sysfs-devices-system-xen_cpu | 20 logic restrictions and assumptions.
|
| /linux-6.3-rc2/Documentation/admin-guide/LSM/ |
| A 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
|
| A 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.
|
| A D | apparmor.rst | 33 For AppArmor to enforce any restrictions beyond standard Linux DAC permissions
|
| A D | LoadPin.rst | 10 restrictions without needing to sign the files individually.
|
| /linux-6.3-rc2/security/safesetid/ |
| A D | Kconfig | 10 approved by a system-wide whitelist. These restrictions also prohibit
|
| /linux-6.3-rc2/Documentation/gpu/amdgpu/display/ |
| A D | mpo-overview.rst | 62 every DCN has different restrictions; here, we are just trying to provide the
68 AMDGPU imposes restrictions on the use of DRM planes in the driver.
71 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
|
| /linux-6.3-rc2/fs/minix/ |
| A D | Kconfig | 11 because of certain built-in restrictions, but it is sometimes found
|
| /linux-6.3-rc2/LICENSES/exceptions/ |
| A D | GCC-exception-2.0 | 16 this file. (The General Public License restrictions do apply in other
|
| /linux-6.3-rc2/LICENSES/deprecated/ |
| A D | Zlib | 20 to the following restrictions:
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/leds/backlight/ |
| A D | common.yaml | 33 due to restrictions in a specific system, such as mounting conditions.
|
| /linux-6.3-rc2/Documentation/mm/ |
| A D | highmem.rst | 85 comes with restrictions about the pointers validity. Contrary to kmap()
105 restrictions imposed on kmap_local_page(). Furthermore, the code between
131 restrictions imposed on kmap_local_page(). In particular, it is necessary to
138 restrictions on preemption or migration. It comes with an overhead as mapping
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/power/supply/ |
| A D | samsung,battery.yaml | 16 the physical restrictions make it impossible to use another battery with the
|
| /linux-6.3-rc2/Documentation/powerpc/ |
| A 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.
|
| /linux-6.3-rc2/Documentation/misc-devices/ |
| A 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:
|
| /linux-6.3-rc2/io_uring/ |
| A D | io_uring.c | 2126 if (!test_bit(req->opcode, ctx->restrictions.sqe_op)) in io_check_restriction()
2130 ctx->restrictions.sqe_flags_required) in io_check_restriction()
2133 if (sqe_flags & ~(ctx->restrictions.sqe_flags_allowed | in io_check_restriction()
2134 ctx->restrictions.sqe_flags_required)) in io_check_restriction()
3927 if (ctx->restrictions.registered) in io_register_restrictions()
3952 ctx->restrictions.register_op); in io_register_restrictions()
3960 __set_bit(res[i].sqe_op, ctx->restrictions.sqe_op); in io_register_restrictions()
3977 memset(&ctx->restrictions, 0, sizeof(ctx->restrictions)); in io_register_restrictions()
3979 ctx->restrictions.registered = true; in io_register_restrictions()
4000 if (ctx->restrictions.registered) in io_register_enable_rings()
[all …]
|
| /linux-6.3-rc2/Documentation/core-api/ |
| A D | memory-allocation.rst | 83 driver for a device with such restrictions, avoid using these flags.
84 And even with hardware with restrictions it is preferable to use
161 will be retried with `vmalloc`. There are restrictions on which GFP
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/pwm/ |
| A D | pwm-sifive.yaml | 16 run at the same period. The period also has significant restrictions on
|
| /linux-6.3-rc2/Documentation/security/ |
| A D | landlock.rst | 22 enforced on the system, only add more restrictions.
91 Userspace tests for backward compatibility, ptrace restrictions and filesystem
|