Home
last modified time | relevance | path

Searched +full:shared +full:- +full:memory (Results 1 – 25 of 1096) sorted by relevance

12345678910>>...44

/openbmc/linux/include/linux/
H A Dtee_drv.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Copyright (c) 2015-2022 Linaro Limited
23 #define TEE_SHM_DYNAMIC BIT(0) /* Dynamic shared memory registered */
25 #define TEE_SHM_USER_MAPPED BIT(1) /* Memory mapped in user space */
26 #define TEE_SHM_POOL BIT(2) /* Memory allocated from pool */
27 #define TEE_SHM_PRIV BIT(3) /* Memory private to TEE driver */
35 * struct tee_context - driver specific context on file pointer data
37 * @list_shm: List of shared memory object owned by this context
42 * shared memory release.
44 * wait for tee-supplicant daemon to be started if not present
[all …]
/openbmc/linux/Documentation/admin-guide/mm/
H A Dnuma_memory_policy.rst2 NUMA Memory Policy
5 What is NUMA Memory Policy?
8 In the Linux kernel, "memory policy" determines from which node the kernel will
9 allocate memory in a NUMA system or in an emulated NUMA system. Linux has
10 supported platforms with Non-Uniform Memory Access architectures since 2.4.?.
11 The current memory policy support was added to Linux 2.6 around May 2004. This
12 document attempts to describe the concepts and APIs of the 2.6 memory policy
15 Memory policies should not be confused with cpusets
16 (``Documentation/admin-guide/cgroup-v1/cpusets.rst``)
18 memory may be allocated by a set of processes. Memory policies are a
[all …]
H A Dnommu-mmap.rst2 No-MMU memory mapping support
5 The kernel has limited support for memory mapping under no-MMU conditions, such
6 as are used in uClinux environments. From the userspace point of view, memory
12 Memory mapping behaviour also involves the way fork(), vfork(), clone() and
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write
24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
30 shared across fork() or clone() without CLONE_VM in the MMU case. Since
31 the no-MMU case doesn't support these, behaviour is identical to
39 In the no-MMU case:
[all …]
/openbmc/linux/drivers/tee/
H A Dtee_shm.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (c) 2015-2017, 2019-2021 Linaro Limited
33 return -EINVAL; in shm_get_kernel_pages()
46 if (shm->pages) { in release_registered_pages()
47 if (shm->flags & TEE_SHM_USER_MAPPED) in release_registered_pages()
48 unpin_user_pages(shm->pages, shm->num_pages); in release_registered_pages()
50 shm_put_kernel_pages(shm->pages, shm->num_pages); in release_registered_pages()
52 kfree(shm->pages); in release_registered_pages()
58 if (shm->flags & TEE_SHM_POOL) { in tee_shm_release()
59 teedev->pool->ops->free(teedev->pool, shm); in tee_shm_release()
[all …]
/openbmc/linux/include/uapi/linux/
H A Dtee.h2 * Copyright (c) 2015-2016, Linaro Limited
49 #define TEE_GEN_CAP_REG_MEM (1 << 2)/* Supports registering shared memory */
52 #define TEE_MEMREF_NULL (__u64)(-1) /* NULL MemRef Buffer */
61 * OP-TEE specific capabilities
66 * struct tee_ioctl_version_data - TEE version
82 * TEE_IOC_VERSION - query version of TEE
91 * struct tee_ioctl_shm_alloc_data - Shared memory allocate argument
92 * @size: [in/out] Size of shared memory to allocate
94 * @id: [out] Identifier of the shared memory
107 * TEE_IOC_SHM_ALLOC - allocate shared memory
[all …]
/openbmc/u-boot/include/
H A Dtee.h1 /* SPDX-License-Identifier: GPL-2.0+ */
12 #define TEE_GEN_CAP_REG_MEM BIT(1) /* Supports registering shared memory */
14 #define TEE_SHM_REGISTER BIT(0) /* In list of shared memory */
15 #define TEE_SHM_SEC_REGISTER BIT(1) /* TEE notified of this memory */
16 #define TEE_SHM_ALLOC BIT(2) /* The memory is malloced() and must */
55 * struct tee_optee_ta_uuid - OP-TEE Trusted Application (TA) UUID format
57 * Used to identify an OP-TEE TA and define suitable to initialize structs
60 * OP-TEE. See RFC4122 for details on the format.
70 * struct tee_shm - memory shared with the TEE
73 * @addr: Pointer to the shared memory
[all …]
/openbmc/linux/Documentation/arch/x86/
H A Dtdx.rst1 .. SPDX-License-Identifier: GPL-2.0
9 encrypting the guest memory. In TDX, a special module running in a special
13 Since the host cannot directly access guest registers or memory, much
19 TDX includes new hypercall-like mechanisms for communicating from the
25 TDX guests behave differently from bare-metal and traditional VMX guests.
26 In TDX guests, otherwise normal instructions or memory accesses can cause
32 Instruction-based #VE
33 ---------------------
35 - Port I/O (INS, OUTS, IN, OUT)
36 - HLT
[all …]
/openbmc/u-boot/drivers/tee/optee/
H A Doptee_smc.h1 /* SPDX-License-Identifier: BSD-2-Clause */
3 * Copyright (c) 2015-2018, Linaro Limited
9 #include <linux/arm-smccc.h>
14 * https://github.com/OP-TEE/optee_os/blob/master/core/arch/arm/include/sm/optee_smc.h
35 * Normal cached memory (write-back), shareable for SMP systems and not
43 * 32-bit registers.
51 * 65cb6b93-af0c-4617-8ed6-644a8d1140f8
82 * Used by non-secure world to figure out which Trusted OS is installed.
85 * Returns UUID in a0-4 in the same way as OPTEE_SMC_CALLS_UID
95 * Used by non-secure world to figure out which version of the Trusted OS
[all …]
H A Doptee_msg.h1 /* SPDX-License-Identifier: BSD-2-Clause */
3 * Copyright (c) 2015-2018, Linaro Limited
13 * This file defines the OP-TEE message protocol used to communicate with
14 * an instance of OP-TEE running in secure world. This file is based on
15 * https://github.com/OP-TEE/optee_os/blob/master/core/include/optee_msg.h
22 * tee-supplicant.
26 * Part 1 - formatting of messages
51 * Pointer to a list of pages used to register user-defined SHM buffer.
54 * list of page addresses. OP-TEE core can reconstruct contiguous buffer from
66 * uint64_t pages_array[OPTEE_MSG_NONCONTIG_PAGE_SIZE/sizeof(uint64_t) - 1];
[all …]
/openbmc/linux/Documentation/devicetree/bindings/reserved-memory/
H A Dxen,shared-memory.txt1 * Xen hypervisor reserved-memory binding
3 Expose one or more memory regions as reserved-memory to the guest
5 to be a shared memory area across multiple virtual machines for
8 For each of these pre-shared memory regions, a range is exposed under
9 the /reserved-memory node as a child node. Each range sub-node is named
10 xen-shmem@<address> and has the following properties:
12 - compatible:
13 compatible = "xen,shared-memory-v1"
15 - reg:
16 the base guest physical address and size of the shared memory region
[all …]
H A Dshared-dma-pool.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/shared-dma-pool.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: /reserved-memory DMA pool
10 - devicetree-spec@vger.kernel.org
13 - $ref: reserved-memory.yaml
18 - const: shared-dma-pool
20 This indicates a region of memory meant to be used as a shared
25 - const: restricted-dma-pool
[all …]
/openbmc/qemu/docs/system/devices/
H A Divshmem.rst1 Inter-VM Shared Memory device
2 -----------------------------
4 On Linux hosts, a shared memory device is available. The basic syntax
7 .. parsed-literal::
9 |qemu_system_x86| -device ivshmem-plain,memdev=hostmem
11 where hostmem names a host memory backend. For a POSIX shared memory
16 -object memory-backend-file,size=1M,share,mem-path=/dev/shm/ivshmem,id=hostmem
19 shared memory region. Interrupt support requires using a shared memory
21 shared memory server is qemu.git/contrib/ivshmem-server. An example
22 syntax when using the shared memory server is:
[all …]
/openbmc/linux/drivers/soc/qcom/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
15 the low-power state for resources related to the remoteproc
24 Command DB queries shared memory by key string for shared system
25 resources. Platform drivers that require to set state of a shared
26 resource on a RPM-hardened platform must use this database to get
27 SoC specific identifier and information for the shared resources.
43 be called qcom-cpr
82 tristate "Qualcomm On Chip Memory (OCMEM) driver"
86 The On Chip Memory (OCMEM) allocator allows various clients to
87 allocate memory from OCMEM based on performance, latency and power
[all …]
/openbmc/linux/drivers/tee/optee/
H A Doptee_smc.h1 /* SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) */
3 * Copyright (c) 2015-2021, Linaro Limited
8 #include <linux/arm-smccc.h>
28 * Normal cached memory (write-back), shareable for SMP systems and not
36 * 32-bit registers.
44 * 384fb3e0-e7f8-11e3-af63-0002a5d5c51b.
75 * Used by non-secure world to figure out which Trusted OS is installed.
78 * Returns UUID in a0-4 in the same way as OPTEE_SMC_CALLS_UID
88 * Used by non-secure world to figure out which version of the Trusted OS
92 * Returns revision in a0-1 in the same way as OPTEE_SMC_CALLS_REVISION
[all …]
H A Doptee_ffa.h1 /* SPDX-License-Identifier: BSD-2-Clause */
3 * Copyright (c) 2019-2021, Linaro Limited
7 * This file is exported by OP-TEE and is kept in sync between secure world
8 * and normal world drivers. We're using ARM FF-A 1.0 specification.
23 * defined in FF-A specification:
27 * w3-w7: Implementation defined, free to be used below
38 * Returns the API version implemented, currently follows the FF-A version.
41 * w4-w7: Not used (MBZ)
46 * w5-w7: Not used (MBZ)
51 * Returns the revision of OP-TEE.
[all …]
H A Doptee_msg.h1 /* SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) */
3 * Copyright (c) 2015-2021, Linaro Limited
12 * This file defines the OP-TEE message protocol (ABI) used to communicate
13 * with an instance of OP-TEE running in secure world.
21 * Part 1 - formatting of messages
49 * Pointer to a list of pages used to register user-defined SHM buffer.
52 * list of page addresses. OP-TEE core can reconstruct contiguous buffer from
64 * uint64_t pages_array[OPTEE_MSG_NONCONTIG_PAGE_SIZE/sizeof(uint64_t) - 1];
77 * Memory attributes for caching passed with temp memrefs. The actual value
80 * defined for the memory range should be used. If optee_smc.h is used as
[all …]
/openbmc/linux/arch/arm64/boot/dts/ti/
H A Dk3-j721e-som-p0.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2019-2020 Texas Instruments Incorporated - https://www.ti.com/
8 /dts-v1/;
10 #include "k3-j721e.dtsi"
13 memory@80000000 {
14 device_type = "memory";
20 reserved_memory: reserved-memory {
21 #address-cells = <2>;
22 #size-cells = <2>;
28 no-map;
[all …]
H A Dk3-j784s4-evm.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2022 Texas Instruments Incorporated - https://www.ti.com/
8 /dts-v1/;
10 #include <dt-bindings/net/ti-dp83867.h>
11 #include <dt-bindings/gpio/gpio.h>
12 #include "k3-j784s4.dtsi"
15 compatible = "ti,j784s4-evm", "ti,j784s4";
19 stdout-path = "serial2:115200n8";
32 memory@80000000 {
33 device_type = "memory";
[all …]
H A Dk3-am642-tqma64xxl.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2021 Texas Instruments Incorporated - https://www.ti.com/
4 * Copyright (c) 2022-2023 TQ-Systems GmbH <linux@ew.tq-group.com>, D-82229 Seefeld, Germany.
7 #include "k3-am642.dtsi"
16 memory@80000000 {
17 device_type = "memory";
18 /* 1G RAM - default variant */
23 reserved-memory {
24 #address-cells = <2>;
25 #size-cells = <2>;
[all …]
/openbmc/u-boot/arch/arm/include/asm/arch-tegra/
H A Divc.h1 /* SPDX-License-Identifier: GPL-2.0 */
12 * Tegra IVC is a communication protocol that transfers fixed-size frames
13 * bi-directionally and in-order between the local CPU and some remote entity.
14 * Communication is via a statically sized and allocated buffer in shared
15 * memory and a notification mechanism.
17 * This API handles all aspects of the shared memory buffer's metadata, and
19 * typically contain some higher-level protocol. The notification mechanism is
24 * frame, process that frame's memory buffer (fill or read it), and then
33 * struct tegra_ivc - In-memory shared memory layout.
40 * struct tegra_ivc - Software state of an IVC channel.
[all …]
/openbmc/qemu/docs/devel/migration/
H A DCPR.rst8 cpr-reboot is the only available mode.
15 CPR unconditionally stops VM execution before memory is saved, and
18 cpr-reboot mode
19 ---------------
23 resumes by running QEMU with the ``-incoming`` option. Because the
27 Guest RAM can be saved in place if backed by shared memory, or can be
31 After state and memory are saved, the user may update userland host
33 the RAM is backed by persistent shared memory, such as a DAX device,
38 ``guest-suspend-ram`` command to the QEMU guest agent. The agent
39 must be pre-installed in the guest, and the guest must support
[all …]
/openbmc/qemu/backends/
H A Dhostmem-shm.c2 * QEMU host POSIX shared memory object backend
10 * See the COPYING file in the top-level directory.
17 #define TYPE_MEMORY_BACKEND_SHM "memory-backend-shm"
34 if (!backend->size) { in shm_backend_memory_alloc()
39 if (!backend->share) { in shm_backend_memory_alloc()
46 * memory unless we share the file descriptor with them. in shm_backend_memory_alloc()
53 * Some operating systems allow creating anonymous POSIX shared memory in shm_backend_memory_alloc()
57 * From Linux's shm_open(3) man-page: in shm_backend_memory_alloc()
58 * For portable use, a shared memory object should be identified in shm_backend_memory_alloc()
61 g_string_printf(shm_name, "/qemu-" FMT_pid "-shm-%s", getpid(), in shm_backend_memory_alloc()
[all …]
/openbmc/linux/Documentation/virt/hyperv/
H A Doverview.rst1 .. SPDX-License-Identifier: GPL-2.0
6 enlightened guest on Microsoft's Hyper-V hypervisor. Hyper-V
7 consists primarily of a bare-metal hypervisor plus a virtual machine
10 partitions. In this documentation, references to Hyper-V usually
15 Hyper-V runs on x86/x64 and arm64 architectures, and Linux guests
16 are supported on both. The functionality and behavior of Hyper-V is
19 Linux Guest Communication with Hyper-V
20 --------------------------------------
21 Linux guests communicate with Hyper-V in four different ways:
24 some guest actions trap to Hyper-V. Hyper-V emulates the action and
[all …]
/openbmc/qemu/docs/specs/
H A Divshmem-spec.rst2 Device Specification for Inter-VM shared memory device
5 The Inter-VM shared memory device (ivshmem) is designed to share a
6 memory region between multiple QEMU processes running different guests
8 shared memory area, it is modeled by QEMU as a PCI device exposing
9 said memory to the guest as a PCI BAR.
11 The device can use a shared memory object on the host directly, or it
27 --------
31 - BAR0 holds device registers (256 Byte MMIO)
32 - BAR1 holds MSI-X table and PBA (only ivshmem-doorbell)
33 - BAR2 maps the shared memory object
[all …]
/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Dgoogle,cros-ec-codec.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/sound/google,cros-ec-codec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Cheng-Yi Chiang <cychiang@chromium.org>
11 - Tzung-Bi Shih <tzungbi@kernel.org>
15 Embedded Controller (EC) and is controlled via a host-command
17 subnode of a cros-ec node.
18 (see Documentation/devicetree/bindings/mfd/google,cros-ec.yaml).
21 - $ref: dai-common.yaml#
[all …]

12345678910>>...44