| /Linux-v6.6/drivers/cxl/ |
| 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-v6.6/Documentation/gpu/rfc/ |
| D | i915_small_bar.rst | 37 Error Capture restrictions
39 With error capture we have two new restrictions:
|
| /Linux-v6.6/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
|
| /Linux-v6.6/tools/testing/cxl/test/ |
| 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-v6.6/Documentation/admin-guide/ |
| D | abi-stable.rst | 7 restrictions, and backward compatibility for them will be guaranteed
|
| /Linux-v6.6/Documentation/userspace-api/ |
| 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-v6.6/Documentation/ABI/testing/ |
| D | sysfs-devices-system-xen_cpu | 20 logic restrictions and assumptions.
|
| /Linux-v6.6/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.
|
| /Linux-v6.6/security/safesetid/ |
| D | Kconfig | 10 approved by a system-wide whitelist. These restrictions also prohibit
|
| /Linux-v6.6/Documentation/gpu/amdgpu/display/ |
| 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-v6.6/LICENSES/exceptions/ |
| D | GCC-exception-2.0 | 16 this file. (The General Public License restrictions do apply in other
|
| /Linux-v6.6/fs/minix/ |
| D | Kconfig | 12 because of certain built-in restrictions, but it is sometimes found
|
| /Linux-v6.6/LICENSES/deprecated/ |
| D | Zlib | 20 to the following restrictions:
|
| /Linux-v6.6/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
|
| /Linux-v6.6/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:
|
| /Linux-v6.6/Documentation/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.
|
| /Linux-v6.6/Documentation/security/ |
| D | landlock.rst | 22 enforced on the system, only add more restrictions.
91 Userspace tests for backward compatibility, ptrace restrictions and filesystem
|
| /Linux-v6.6/io_uring/ |
| D | io_uring.c | 2110 if (!test_bit(req->opcode, ctx->restrictions.sqe_op)) in io_check_restriction()
2113 if ((sqe_flags & ctx->restrictions.sqe_flags_required) != in io_check_restriction()
2114 ctx->restrictions.sqe_flags_required) in io_check_restriction()
2117 if (sqe_flags & ~(ctx->restrictions.sqe_flags_allowed | in io_check_restriction()
2118 ctx->restrictions.sqe_flags_required)) in io_check_restriction()
4184 if (ctx->restrictions.registered) in io_register_restrictions()
4209 ctx->restrictions.register_op); in io_register_restrictions()
4217 __set_bit(res[i].sqe_op, ctx->restrictions.sqe_op); in io_register_restrictions()
4220 ctx->restrictions.sqe_flags_allowed = res[i].sqe_flags; in io_register_restrictions()
4223 ctx->restrictions.sqe_flags_required = res[i].sqe_flags; in io_register_restrictions()
[all …]
|
| /Linux-v6.6/Documentation/devicetree/bindings/mtd/ |
| D | vf610-nfc.txt | 17 there might be restrictions on maximum rates when using hardware ECC.
|
| /Linux-v6.6/Documentation/devicetree/bindings/i2c/ |
| D | i2c.txt | 91 states that additional SMBus restrictions and features apply to this bus.
92 An example of feature is SMBusHostNotify. Examples of restrictions are
|
| /Linux-v6.6/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
|
| /Linux-v6.6/Documentation/core-api/ |
| 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
|
