Searched full:container (Results 1 – 17 of 17) sorted by relevance
| /cloud-hypervisor/scripts/ |
| H A D | dev_cli.sh | 26 # Container paths
32 # Container networking option
37 # because we want to persist the cargo registry across container invocations.
121 # Make sure we're using the latest dev container, by just pulling it.
130 ok_or_die "Error pulling/building container image. Aborting."
134 # Fix main directory permissions after a container ran as root.
135 # Since the container ran as root, any files it creates will be owned by root.
180 echo " --local Set the container image version being used to \"local\"."
208 echo " build-container [--type]"
209 echo " Build the Cloud Hypervisor container."
[all …]
|
| /cloud-hypervisor/docs/ |
| H A D | coverage.md | 60 pass RUSTFLAGS to the container.
62 Since the `profraw` files are generated from within the container, the file
64 the data processing from within the container if you don't want to fight the
|
| H A D | custom-image.md | 17 `az storage blob upload --account-name cloudhypervisorstorages --container-name '$web' --name jammy…
|
| H A D | uefi.md | 7 …s otherwise suitable, however it is suggested to use a temporary Docker container with Ubuntu 18.0…
|
| H A D | building.md | 65 first invocation, this script will pull a fairly large container image.
|
| H A D | performance_metrics.md | 9 fairly large container image.
|
| /cloud-hypervisor/pci/src/ |
| H A D | vfio.rs | 1447 container: Arc<VfioContainer>, field
1462 container: Arc<VfioContainer>, in new()
1491 container, in new()
1696 self.container in map_mmio_regions()
1716 // Unmap from vfio container in unmap_mmio_regions()
1719 .container in unmap_mmio_regions()
1724 "Could not unmap mmio region from vfio container: \ in unmap_mmio_regions()
1768 self.container in dma_map()
1778 self.container in dma_unmap()
1901 // Unmap the old MMIO region from vfio container in move_bar()
[all …]
|
| /cloud-hypervisor/.github/workflows/ |
| H A D | openapi.yaml | 7 container: openapitools/openapi-generator-cli
|
| H A D | integration-arm64.yaml | 49 …az storage blob download --container-name private-images --file "$IMG_GZ_PATH" --name "$IMG_GZ_BLO…
|
| H A D | integration-windows.yaml | 39 …az storage blob download --container-name private-images --file "$HOME/workloads/windows-server-20…
|
| /cloud-hypervisor/virtio-devices/src/ |
| H A D | iommu.rs | 422 // make sure to issue these mappings for the new endpoint/container in parse()
496 // For viommu all endpoints receive their own VFIO container, as a result in parse()
498 // mapping is done on a per-container level, not a per-domain level in parse()
|
| H A D | mem.rs | 683 Container, enumerator
|
| /cloud-hypervisor/vmm/src/ |
| H A D | device_manager.rs | 985 // VFIO container
986 // Only one container can be created, therefore it is stored as part of the
3627 // Here we create a new VFIO container for two reasons. Either this is in add_vfio_device()
3628 // the first VFIO device, meaning we need a new VFIO container, which in add_vfio_device()
3631 // container. In the vIOMMU use case, we can't let all devices under in add_vfio_device()
3632 // the same VFIO container since we couldn't map/unmap memory for each in add_vfio_device()
3634 // VFIO container level. in add_vfio_device()
3694 VirtioMemMappingSource::Container, in add_vfio_device()
4451 // No need to remove any virtio-mem mapping here as the container outlives all devices in eject_device()
|
| /cloud-hypervisor/vm-device/src/ |
| H A D | bus.rs | 114 /// A device container for routing reads and writes over some address space.
|
| /cloud-hypervisor/ |
| H A D | README.md | 353 not limited to container/serverless or client workloads.
|
| H A D | release-notes.md | 830 container, allowing PCIe P2P between all VFIO devices on the same
|
| /cloud-hypervisor/arch/src/aarch64/ |
| H A D | fdt.rs | 473 // Cluster is the container of cores, and it is mandatory in the CPU topology. in create_cpu_nodes()
|