Searched full:shared (Results 1 – 25 of 577) sorted by relevance
12345678910>>...24
| /Documentation/devicetree/bindings/mailbox/ |
| D | nvidia,tegra186-hsp.yaml | 21 The features that HSP supported are shared mailboxes, shared
29 For shared mailboxes, the first cell composed of two fields:
31 A bit mask of flags that further specifies the type of shared
33 specified then, 32-bit shared mailbox is used.
36 TEGRA_HSP_MBOX_TYPE_SM for shared mailboxes.
41 For shared mailboxes, the second cell is composed of two fields:
43 A bit mask of flags that further specify how the shared mailbox
52 The index of the shared mailbox to use. The number of available
83 # shared interrupts are optional
89 - pattern: "^shared[0-7]$"
[all …]
|
| D | mailbox.txt | 26 - shmem : List of phandle pointing to the shared memory(SHM) area between the
27 users of these mailboxes for IPC, one for each mailbox. This shared
39 Example with shared memory(shmem):
|
| D | qcom,apcs-kpss-global.yaml | 47 - qcom,sc7180-apss-shared
48 - qcom,sc8180x-apss-shared
49 - qcom,sm8150-apss-shared
50 - const: qcom,sdm845-apss-shared
63 - qcom,sdm845-apss-shared
173 - qcom,sdm845-apss-shared
|
| /Documentation/filesystems/ |
| D | sharedsubtree.rst | 4 Shared Subtrees
24 that got mounted recently. Shared subtree semantics provide the necessary
33 Shared subtree provides four different flavors of mounts; struct vfsmount to be
36 a. shared mount
42 2a) A shared mount can be replicated to as many mountpoints and all the
47 Let's say /mnt has a mount that is shared::
49 mount --make-shared /mnt
51 Note: mount(8) command now supports the --make-shared flag,
86 2b) A slave mount is like a shared mount except that mount and umount events
89 All slave mounts have a master mount which is a shared.
[all …]
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | xen,shared-memory.txt | 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
13 compatible = "xen,shared-memory-v1"
16 the base guest physical address and size of the shared memory region
19 64 bit integer offset within the owner virtual machine's shared
23 a string that identifies the shared memory region as specified in
|
| D | qcom,cmd-db.yaml | 12 is stored in a shared memory region and is loaded by the remote processor.
15 controlling shared resources. Depending on the board configuration the shared
17 remote processor and made available in the shared memory.
|
| /Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 100 * VMA policies are shared between all tasks that share a
122 Shared Policy
123 Conceptually, shared policies apply to "memory objects" mapped
124 shared into one or more tasks' distinct address spaces. An
125 application installs shared policies the same way as VMA
127 virtual addresses that map the shared object. However, unlike
129 range of a task's address space, shared policies apply
130 directly to the shared object. Thus, all tasks that attach to
132 shared object, by any task, will obey the shared policy.
134 As of 2.6.22, only shared memory segments, created by shmget() or
[all …]
|
| D | nommu-mmap.rst | 30 shared across fork() or clone() without CLONE_VM in the MMU case. Since
67 that a copy is always taken and never shared.
73 mapping; shared across fork.
84 case, a shared-writable memory mapping will be possible. It will work
163 Interprocess shared memory
166 Both SYSV IPC SHM shared memory and POSIX shared memory is supported in NOMMU
191 Shared mappings may not be moved. Shareable mappings may not be moved either,
192 even if they are not currently shared.
221 is removed. An existing mapping will be shared, partially or not, if possible
240 In such a case, care must be taken lest userspace see a shared or a
[all …]
|
| /Documentation/userspace-api/ |
| D | unshare.rst | 37 outside the confinement of all-or-nothing shared resources of legacy
44 shared at the time of their creation. unshare() was conceptualized by
48 shared resources without creating a new process. unshare() is a natural
57 resources is not possible. Since namespaces are shared by default
60 from default shared namespace. The following lists two use-cases
74 of shared-tree feature in the Linux kernel, even regular Linux systems
85 decide what needs to be shared at the time of creating the process
111 be shared, similar flags in unshare(int flags) should specify
135 context that are currently being shared with other processes. Part
136 of execution context, such as the namespace, is shared by default
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | google,cros-ec-codec.yaml | 33 Physical base address and length of shared memory region from EC.
36 The last one integer is the length of the shared memory.
41 Shared memory region to EC. A "shared-dma-pool".
53 compatible = "shared-dma-pool";
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | fsl,ls-msi.yaml | 38 - description: Shared MSI interrupt group 0
39 - description: Shared MSI interrupt group 1
40 - description: Shared MSI interrupt group 2
41 - description: Shared MSI interrupt group 3
|
| D | st,spear3xx-shirq.txt | 1 * SPEAr Shared IRQ layer (shirq)
3 SPEAr3xx architecture includes shared/multiplexed irqs for certain set
13 A single node in the device tree is used to describe the shared
|
| /Documentation/driver-api/ |
| D | reset.rst | 70 Shared and exclusive resets
75 The distinction between shared and exclusive reset controls is made at the time
81 Shared resets behave similarly to clocks in the kernel clock framework.
96 For shared reset controls, calls to the two functions must be balanced.
98 Note that since multiple consumers may be using a shared reset control, there
99 is no guarantee that calling reset_control_assert() on a shared reset control
101 Consumer drivers using shared reset controls should assume that the reset line
111 In general, these resets can not be shared between multiple consumers, since
116 shared, but for those only the first trigger request causes an actual pulse to
120 For shared reset controls, calls to the two functions must be balanced.
|
| /Documentation/devicetree/bindings/net/ |
| D | cavium-mix.txt | 11 AGL registers. The third bank are the AGL registers shared by all
12 MIX devices present. The fourth bank is the AGL_PRT_CTL shared by
15 - cell-index: A single cell specifying which portion of the shared
|
| /Documentation/devicetree/bindings/perf/ |
| D | arm,dsu-pmu.yaml | 8 title: ARM DynamIQ Shared Unit (DSU) Performance Monitor Unit (PMU)
15 ARM DynamIQ Shared Unit (DSU) integrates one or more CPU cores with a shared
|
| /Documentation/virt/hyperv/ |
| D | overview.rst | 31 processor registers or in memory shared between the Linux guest and
45 the Hyper-V host and the Linux guest. It uses memory that is shared
71 allocated memory. Many shared areas are kept to 1 page so that a
72 single GPA is sufficient. Larger shared areas require a list of
83 telling Hyper-V to set the shared GPA to zero.
96 As described in the TLFS, a few memory pages shared between Hyper-V
112 memory shared with Hyper-V should be revoked. Hyper-V could modify
113 a shared page or remove an overlay page after the new kernel is
118 the crash/panic path still has holes in cleanup because some shared
120 mechanism to revoke the shared pages for CPUs other than the CPU
[all …]
|
| /Documentation/arch/x86/ |
| D | tdx.rst | 283 There are essentially two classes of TDX memory: private and shared.
285 against access from the hypervisor. Shared memory is expected to be
286 shared between guest and hypervisor and does not receive full TDX
290 private or shared. It selects the behavior with a bit in its page table
292 information in shared memory, exposing it to the untrusted hypervisor.
294 #VE on Shared Memory
297 Access to shared mappings can cause a #VE. The hypervisor ultimately
298 controls whether a shared memory access causes a #VE, so the guest must be
299 careful to only reference shared pages it can safely handle a #VE. For
300 instance, the guest should be careful not to access shared memory in the
[all …]
|
| D | sva.rst | 4 Shared Virtual Addressing (SVA) with ENQCMD
10 Shared Virtual Addressing (SVA) allows the processor and device to use the
12 addresses to physical addresses. SVA is what PCIe calls Shared Virtual
31 Shared Hardware Workqueues
35 the use of Shared Work Queues (SWQ) by both applications and Virtual
172 Shared Virtual Addressing (SVA) permits I/O hardware and the processor to
173 work in the same address space, i.e., to share it. Some call it Shared
175 POSIX Shared Memory and Secure Virtual Machines which were terms already in
184 * How are shared workqueues different?
192 hardware also manages the queue depth for Shared Work Queues (SWQ), and
[all …]
|
| /Documentation/devicetree/bindings/dma/ |
| D | fsl,imx-sdma.yaml | 70 - Shared SSI: 1
74 - Shared UART: 5
77 - Shared CSPI: 8
83 - Shared Memory Stick Host Controller: 14
93 - Shared ASRC: 23
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smd.yaml | 7 title: Qualcomm Shared Memory Driver
15 The Qualcomm Shared Memory Driver is a FIFO based communication channel for
50 shared-memory {
|
| /Documentation/devicetree/bindings/display/ti/ |
| D | ti,j721e-dss.yaml | 27 - description: common_s0 DSS Shared common 0
28 - description: common_s1 DSS Shared common 1
29 - description: common_s2 DSS Shared common 2
91 - description: common_s0 DSS Shared common 0
92 - description: common_s1 DSS Shared common 1
93 - description: common_s2 DSS Shared common 2
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | index.rst | 8 DRBD is a shared-nothing, synchronously replicated block device. It
10 clusters and in this context, is a "drop-in" replacement for shared
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | ti,bluetooth.yaml | 18 * TI WiLink 7/8 (wl12xx/wl18xx) Shared Transport BT/FM/GPS devices
21 and GPS over what's called "shared transport". The shared transport is
|
| /Documentation/mm/ |
| D | hugetlbfs_reserv.rst | 80 Reservation Map Location (Private or Shared)
83 A huge page mapping or segment is either private or shared. If private,
84 it is typically only available to a single address space (task). If shared,
92 - For shared mappings, the reservation map hangs off the inode. Specifically,
93 inode->i_mapping->private_data. Since shared mappings are always backed
101 Reservations are created when a huge page backed shared memory segment is
121 One of the big differences between PRIVATE and SHARED mappings is the way
124 - For shared mappings, an entry in the reservation map indicates a reservation
139 always the value (to - from). However, for shared mappings it is possible that
166 modified to reflect the reservations. In the case of a shared mapping, a
[all …]
|
| /Documentation/translations/zh_CN/mm/ |
| D | overcommit-accounting.rst | 58 | SHARED or READ-only - 0 cost (该文件是映射而不是交换)
62 | SHARED - 映射的大小
|
12345678910>>...24