Searched full:container (Results 1 – 25 of 100) sorted by relevance
1234
| /Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 15 container. This allows programs to interact with a TPM in a container
17 container gets its own unique, emulated, software TPM.
22 To make an emulated software TPM available to each container, the container
25 descriptor. The former is moved into the container by creating a character
27 is passed to the TPM emulator. Software inside the container can then send
|
| /Documentation/driver-api/ |
| D | vfio.rst | 80 a container class, which may hold one or more groups. A container
83 On its own, the container provides little functionality, with all
85 The user needs to add a group into the container for the next level
99 Once the group is ready, it may be added to the container by opening
102 previously opened container file. If desired and if the IOMMU driver
104 be set to the same container. If a group fails to set to a container
105 with existing groups, a new empty container will need to be used
108 With a group (or groups) attached to a container, the remaining
169 int container, group, device, i;
176 /* Create a new container */
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | sky81452.txt | 8 - backlight : container node for backlight following the binding
10 - regulator : container node for regulators following the binding
|
| D | brcm,bcm59056.txt | 16 - regulators: container node for regulators following the generic
|
| /Documentation/driver-api/driver-model/ |
| D | design-patterns.rst | 9 1. State Container
13 1. State Container
21 The most common way to achieve this is to use the state container design
41 called. This is our state container for this instance of the device driver.
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,trx.txt | 1 Broadcom TRX Container Partition
13 Container can hold up to 4 partitions. The first partition has to contain a
|
| D | ubi-volume.yaml | 30 This container may reference an NVMEM layout parser.
|
| D | brcm,bcm963xx-imagetag.txt | 1 Broadcom BCM963XX ImageTag Partition Container
|
| D | partitions.yaml | 10 This binding is generic and describes the content of the partitions container
|
| D | brcm,bcm947xx-cfe-partitions.yaml | 27 4) TRX firmware container which can hold up to 4 subpartitions
|
| /Documentation/filesystems/nfs/ |
| D | localio.rst | 34 as possible, this is particularly useful for container use cases
213 objects to span from the host kernel's nfsd to per-container knfsd
224 net-ns in the client because that prevents a server container from
274 instance running in a container, with a LOCALIO client mounted, is
275 shutdown. Upon restart of the container and associated NFSD the client
299 recovery is needed if/when an nfsd instance running in a container were
354 - Client on host, server within a container (for both v3 and v4.2).
355 The container testing was in terms of podman managed containers and
356 includes successful container stop/restart scenario.
|
| D | client-identifier.rst | 137 - "Containers" within a single Linux host. If each container has
162 container system has access to some sort of per-container identity
164 be formed at boot using the container's internal identifier:
|
| /Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | overview.rst | 80 DPRC (Datapath Resource Container)
83 A DPRC is a container object that holds all the other
86 in the container.
124 All objects in a container share the same hardware "isolation context".
126 is at the DPRC (container) level, not at the individual object
269 same container/DPRC share the same 'device-id'.
280 As described previously, a DPRC is a container that holds the other
350 and handles interrupts for container events such as hot plug by
|
| /Documentation/devicetree/bindings/net/ |
| D | lpc-eth.txt | 14 - mdio : specifies the mdio bus, used as a container for phy nodes according to
|
| /Documentation/userspace-api/ |
| D | iommufd.rst | 38 The IOAS is a functional replacement for the VFIO container, and like the VFIO
39 container it copies an IOVA map to a list of iommu_domains held within it.
196 container IOCTLs by mapping them into io_pagetable operations. Doing so allows
199 container fd.
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-fc | 9 machine or container group. The application or logical
|
| D | sysfs-bus-iio-cros-ec | 28 HAL) through the Android container on ChromeOS.
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | nvmem-layout.yaml | 18 perform their parsing. The nvmem-layout container is here to describe these.
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | ti,da850-pupd.txt | 12 The controller node also acts as a container for pin group configuration nodes.
|
| D | pinctrl-sirf.txt | 16 SiRFprimaII's pinmux nodes act as a container for an arbitrary number of subnodes.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | freezer-subsystem.rst | 112 to freeze all tasks in the container::
120 to unfreeze all tasks in the container::
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 162 - VP8 parsed frame, including the frame header, as extracted from the container.
184 - VP9 parsed frame, including the frame header, as extracted from the container.
265 - AV1 parsed frame, including the frame header, as extracted from the container.
|
| D | pixfmt-packed-yuv.rst | 293 components horizontally by 2, storing 2 pixels in a container. The container
306 .. flat-table:: Packed YUV 4:2:2 Formats in 32-bit container
375 .. flat-table:: Packed YUV 4:2:2 Formats in 64-bit container
|
| /Documentation/devicetree/bindings/csky/ |
| D | cpus.txt | 18 Description: Container of cpu nodes
|
| /Documentation/devicetree/bindings/sound/ |
| D | mediatek,mt8365-mt6357.yaml | 34 Container for dai-link level properties and CODEC sub-nodes.
|
1234