Home
last modified time | relevance | path

Searched +full:secure +full:- +full:regions (Results 1 – 18 of 18) sorted by relevance

/Documentation/devicetree/bindings/mtd/
Dnand-chip.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mtd/nand-chip.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Miquel Raynal <miquel.raynal@bootlin.com>
13 - $ref: mtd.yaml#
18 SPI-NAND devices are concerned by this description.
23 Contains the chip-select IDs.
25 nand-ecc-engine:
31 2/ The ECC engine is part of the NAND part (on-die), in this
[all …]
/Documentation/devicetree/bindings/mailbox/
Dti,secure-proxy.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mailbox/ti,secure-proxy.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Texas Instruments' Secure Proxy
10 - Nishanth Menon <nm@ti.com>
13 The Texas Instruments' secure proxy is a mailbox controller that has
15 Message manager is broken up into different address regions that are
16 called "threads" or "proxies" - each instance is unidirectional and is
22 pattern: "^mailbox@[0-9a-f]+$"
[all …]
/Documentation/networking/devlink/
Diosm.rst1 .. SPDX-License-Identifier: GPL-2.0
13 The ``iosm`` driver implements the following driver-specific parameters.
15 .. list-table:: Driver-specific parameters implemented
18 * - Name
19 - Type
20 - Mode
21 - Description
22 * - ``erase_full_flash``
23 - u8
24 - runtime
[all …]
/Documentation/devicetree/bindings/sram/
Dsram.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic on-chip SRAM
10 - Rob Herring <robh@kernel.org>
13 Simple IO memory regions to be managed by the genalloc API.
19 Following the generic-names recommended practice, node names should
30 - mmio-sram
31 - amlogic,meson-gxbb-sram
32 - arm,juno-sram-ns
[all …]
/Documentation/admin-guide/
Dthunderbolt.rst1 .. SPDX-License-Identifier: GPL-2.0
25 -----------------------------------
27 should be a userspace tool that handles all the low-level details, keeps
31 found in ``Documentation/ABI/testing/sysfs-bus-thunderbolt``.
35 ``/etc/udev/rules.d/99-local.rules``::
66 secure
68 addition to UUID the device (if it supports secure connect) is sent
92 If the security level reads as ``user`` or ``secure`` the connected
101 Authorizing devices when security level is ``user`` or ``secure``
102 -----------------------------------------------------------------
[all …]
Dperf-security.rst7 --------
50 -------------------------------
66 independently enabled and disabled on per-thread basis for processes and
74 observability operations in the kernel and provides a secure approach to
79 processes but CAP_SYS_ADMIN usage for secure monitoring and observability
84 is recommended as the preferred secure approach to resolve double access
103 ---------------------------------
105 Mechanisms of capabilities, privileged capability-dumb files [6]_,
118 # ls -alhF
119 -rwxr-xr-x 2 root root 11M Oct 19 15:12 perf
[all …]
Dkernel-parameters.txt16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
41 If set to vendor, prefer vendor-specific driver
73 Documentation/firmware-guide/acpi/debug.rst for more information about
[all …]
/Documentation/arch/s390/
Dmm.rst1 .. SPDX-License-Identifier: GPL-2.0
12 - Some aspects of the virtual memory layout setup are not
15 - Unused gaps in the virtual memory layout could be present
16 or not - depending on how partucular system is configured.
19 - The virtual memory regions are tracked or untracked by KASAN
28 +- 0 --------------+- 0 --------------+
29 | | S390_lowcore | Low-address memory
30 | +- 8 KB -----------+
35 +- AMODE31_START --+- AMODE31_START --+ .amode31 rand. phys/virt start
37 +- AMODE31_END ----+- AMODE31_END ----+ .amode31 rand. phys/virt end (<2GB)
[all …]
/Documentation/arch/arm64/
Dbooting.rst13 (EL0 - EL3), with EL0, EL1 and EL2 having a secure and a non-secure
15 level and exists only in secure mode. Both are architecturally optional.
19 is passed to the Linux kernel. This may include secure monitor and
33 ---------------------------
46 -------------------------
50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
59 ------------------------------
71 ------------------------
75 The decompressed kernel image contains a 64-byte header as follows::
91 - As of v3.17, all fields are little endian unless stated otherwise.
[all …]
/Documentation/arch/x86/
Dtdx.rst1 .. SPDX-License-Identifier: GPL-2.0
16 TDX introduces a new CPU mode called Secure Arbitration Mode (SEAM) and
18 CPU-attested software module called 'the TDX module' runs inside the new
22 TDX also leverages Intel Multi-Key Total Memory Encryption (MKTME) to
23 provide crypto-protection to the VMs. TDX reserves part of MKTME KeyIDs
32 TDX boot-time detection
33 -----------------------
41 ---------------------------------------
59 Besides initializing the TDX module, a per-cpu initialization SEAMCALL
103 ------------------------------------------
[all …]
/Documentation/userspace-api/
Dvduse.rst2 VDUSE - "vDPA Device in Userspace"
9 possible to implement software-emulated vDPA devices in userspace. And
10 to make the device emulation more secure, the emulated vDPA device's
21 ----------------------------
49 .. code-block:: c
59 return -ENOMEM;
92 return -1;
96 ---------------
104 add per-virtqueue configuration such as the max size of virtqueue to the device.
111 .. code-block:: c
[all …]
/Documentation/devicetree/bindings/display/msm/
Dgpu.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Rob Clark <robdclark@gmail.com>
14 # as a work-around:
20 - qcom,adreno
21 - amd,imageon
23 - compatible
28 - description: |
30 figure out the chip-id.
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-etm4x76 Description: (Read) Indicates the number of single-shot comparator controls that
135 Description: (RW) Controls which regions in the memory map are enabled to
148 Description: (RW) In Secure state, each bit controls whether instruction
155 Description: (RW) In non-secure state, each bit controls whether instruction
289 Description: (RW) Set the Exception Level matching bits for secure and
290 non-secure exception levels.
486 Description: (Read) Returns the number of P0 right-hand keys that the trace unit
493 Description: (Read) Returns the number of P1 right-hand keys that the trace unit
500 Description: (Read) Returns the number of special P1 right-hand keys that the
508 Description: (Read) Returns the number of conditional P1 right-hand keys that
[all …]
Dsysfs-bus-cxl4 Contact: linux-cxl@vger.kernel.org
14 Contact: linux-cxl@vger.kernel.org
17 Memory Device Output Payload in the CXL-2.0
24 Contact: linux-cxl@vger.kernel.org
28 Payload in the CXL-2.0 specification.
34 Contact: linux-cxl@vger.kernel.org
40 class-ids can be compared against a similar "qos_class"
42 that the endpoints map their local memory-class to a
45 side-effects that may result. First class-id is displayed.
51 Contact: linux-cxl@vger.kernel.org
[all …]
/Documentation/driver-api/
Dvfio.rst2 VFIO - "Virtual Function I/O" [1]_
7 allotted. This includes x86 hardware with AMD-Vi and Intel VT-d,
11 a secure, IOMMU protected environment. In other words, this allows
12 safe [2]_, non-privileged, userspace drivers.
19 bare-metal device drivers [3]_.
22 field, also benefit from low-overhead, direct device access from
23 userspace. Examples include network adapters (often non-TCP/IP based)
33 secure, more featureful userspace driver environment than UIO.
36 ---------------------------
41 by far the most critical aspect for maintaining a secure environment
[all …]
/Documentation/admin-guide/kdump/
Dvmcoreinfo.rst11 section and used by user-space tools like crash and makedumpfile to
18 ------------------------
25 ---------
32 -----------
39 User-space tools can get the kernel name, host name, kernel release
43 ---------------------
49 ---------------
56 --------------
62 ------
69 -------------
[all …]
/Documentation/gpu/
Ddrm-mm.rst6 frame buffers, textures, vertices and other graphics-related data. Given
13 manager to be developed and tried to be a one-size-fits-them all
20 GEM started as an Intel-sponsored project in reaction to TTM's
22 providing a solution to every graphics memory-related problems, GEM
31 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_module.c
34 .. kernel-doc:: include/drm/ttm/ttm_caching.h
38 ---------------------------
40 .. kernel-doc:: include/drm/ttm/ttm_device.h
43 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_device.c
47 --------------------------------
[all …]
/Documentation/virt/kvm/
Dapi.rst1 .. SPDX-License-Identifier: GPL-2.0
4 The Definitive KVM (Kernel-based Virtual Machine) API Documentation
13 - System ioctls: These query and set global attributes which affect the
17 - VM ioctls: These query and set attributes that affect an entire virtual
24 - vcpu ioctls: These query and set attributes that control the operation
32 - device ioctls: These query and set attributes that control the operation
80 facility that allows backward-compatible extensions to the API to be
104 the ioctl returns -ENOTTY.
122 -----------------------
139 -----------------
[all …]