| /OK3568_Linux_fs/kernel/Documentation/virt/ |
| H A D | ne_overview.rst | 14 For example, an application that processes sensitive data and runs in a VM,
15 can be separated from other applications running in the same VM. This
16 application then runs in a separate VM than the primary VM, namely an enclave.
18 An enclave runs alongside the VM that spawned it. This setup matches low latency
20 memory and CPUs, are carved out of the primary VM. Each enclave is mapped to a
21 process running in the primary VM, that communicates with the NE driver via an
27 VM guest that uses the provided ioctl interface of the NE driver to spawn an
28 enclave VM (that's 2 below).
30 There is a NE emulated PCI device exposed to the primary VM. The driver for this
36 hypervisor running on the host where the primary VM is running. The Nitro
[all …]
|
| /OK3568_Linux_fs/kernel/net/iucv/ |
| H A D | Kconfig | 5 prompt "IUCV support (S390 - z/VM only)"
8 under VM or VIF. If you run on z/VM, say "Y" to enable a fast
9 communication link between VM guests.
14 prompt "AF_IUCV Socket support (S390 - z/VM and HiperSockets transport)"
17 based on z/VM inter-user communication vehicle or based on
|
| /OK3568_Linux_fs/kernel/drivers/s390/char/ |
| H A D | Kconfig | 140 prompt "Support for the z/VM recording system services (VM only)"
144 by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
150 prompt "Support for the z/VM CP interface"
155 program on z/VM
158 int "Memory in MiB reserved for z/VM CP interface"
162 Specify the default amount of memory in MiB reserved for the z/VM CP
169 prompt "API for reading z/VM monitor service records"
172 Character device driver for reading z/VM monitor service records
176 prompt "API for writing z/VM monitor service records"
179 Character device driver for writing z/VM monitor service records
[all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-core/images/build-appliance-image/ |
| H A D | README_VirtualBox_Toaster.txt | 5 Toaster is launched via the command in VM:
18 Find out your VM network IP address:
26 Launch the Toaster web server in VM:
37 Find out your VM network IP address:
45 When using NAT network, the VM web server can be accessed using
64 Now we can launch the Toaster web server in VM:
|
| H A D | README_VirtualBox_Guest_Additions.txt | 9 Make sure VM is configured with an Optical Drive.
12 Build Appliance VM:
14 1. Boot VM, select root "Terminal" instead of the default "Terminal <2>"
16 2. Insert Guest additions CD into VM optical drive:
17 VM menu "Devices"->"Optical Drives"-> Select "VBoxGuestAdditions<version>.iso"
57 Guest VM: create mount point for the shared folder, i.e.:
|
| /OK3568_Linux_fs/kernel/drivers/s390/net/ |
| H A D | Kconfig | 23 It also supports virtual CTCs when running under VM.
32 prompt "IUCV network device support (VM only)"
36 vehicle networking under VM or VIF. It enables a fast communication
37 link between VM guests. Using ifconfig a point-to-point connection
39 running on the other VM guest. To compile as a module, choose M.
44 prompt "IUCV special message support (VM only)"
48 from other VM guest systems.
52 prompt "Deliver IUCV special messages as uevents (VM only)"
67 HiperSockets interfaces and z/VM virtual NICs for Guest LAN and
|
| /OK3568_Linux_fs/kernel/Documentation/virt/kvm/devices/ |
| H A D | vfio.rst | 11 Only one VFIO instance may be created per VM. The created device
12 tracks VFIO groups in use by the VM and features of those groups
13 important to the correctness and acceleration of the VM. As groups
14 are enabled and disabled for use by the VM, KVM should be updated
|
| H A D | xive.rst | 10 This device acts as a VM interrupt controller. It provides the KVM
11 interface to configure the interrupt sources of a VM in the underlying
23 guest in VMAs populated with a custom VM fault handler.
59 number being mapped and then lets the VM fault handler repopulate.
83 migrating the VM.
228 Saving the state of a VM using the XIVE native exploitation mode
229 should follow a specific sequence. When the VM is stopped :
|
| H A D | vm.rst | 9 struct kvm_device_attr as other devices, but targets VM-wide settings
95 are not handled by KVM need to by imlemented in the VM driver code.
127 VM. Features that are not available cannot be enabled.
183 all VCPUs of a VM. This attribute will only be available if kernel and
307 -EINVAL if the state of the VM is invalid (e.g. no memory defined);
|
| /OK3568_Linux_fs/kernel/Documentation/vm/ |
| H A D | page_migration.rst | 167 To overcome the problem, VM supports non-LRU page migration which provides
176 What VM expects from isolate_page() function of driver is to return *true*
177 if driver isolates the page successfully. On returning true, VM marks the page
181 Once page is successfully isolated, VM uses page.lru fields so driver
187 After isolation, VM calls migratepage() of driver with the isolated page.
191 indicate to the VM the oldpage is no longer movable via __ClearPageMovable()
194 can return -EAGAIN. On -EAGAIN, VM will retry page migration in a short time
195 because VM interprets -EAGAIN as "temporary migration failure". On returning
196 any error except -EAGAIN, VM will give up the page migration without
203 If migration fails on the isolated page, VM should return the isolated page
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/reserved-memory/ |
| H A D | xen,shared-memory.txt | 4 virtual machine. Typically, a region is configured at VM creation time
20 memory region used for the mapping in the borrower VM.
24 the VM config file
|
| /OK3568_Linux_fs/kernel/Documentation/s390/ |
| H A D | monreader.rst | 2 Linux API for read access to z/VM Monitor Records
15 usable from user space and allows read access to the z/VM Monitor Records
16 collected by the `*MONITOR` System Service of z/VM.
21 The z/VM guest on which you want to access this API needs to be configured in
25 This item will use the IUCV device driver to access the z/VM services, so you
26 need a kernel with IUCV support. You also need z/VM version 4.4 or 5.1.
78 Refer to the "z/VM Performance" book (SC24-6109-00) on how to create a monitor
79 DCSS if your z/VM doesn't have one already, you need Class E privileges to
147 See "Appendix A: `*MONITOR`" in the "z/VM Performance" document for a description
149 be found here (z/VM 5.1): https://www.vm.ibm.com/pubs/mon510/index.html
[all …]
|
| H A D | 3270.rst | 22 VM-ESA operating system, define a 3270 to your virtual machine by using
31 Your network connection from VM-ESA allows you to use x3270, tn3270, or
56 configuration file under /etc/modprobe.d/. If you are working on a VM
60 other, or neither. If you generate both, the console type under VM is
70 3. (If VM) define devices with DEF GRAF
74 To test that everything works, assuming VM and x3270,
155 The screen you should now see contains a VM logo with input
193 If so, you must issue the command "DEF GRAF 620" from your VM
|
| /OK3568_Linux_fs/kernel/Documentation/powerpc/ |
| H A D | ultravisor.rst | 63 the VM it is returning to is secure.
152 * SVMs are created from normal VM using (open source) tooling supplied
158 * When the UV_ESM ultracall is made the Ultravisor copies the VM into
389 #. When a normal VM switches to secure mode, all its pages residing
497 #. If the value of the PATE for an existing partition (VM) changes,
502 the PATE entries for a normal VM and can change the PATE entry
665 * U_INVALID if VM is not secure.
703 * U_INVALID if the VM is not secure.
752 * U_INVALID if VM is not secure.
795 * U_INVAL if VM is not secure.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-mm | 3 Contact: Nishanth Aravamudan <nacc@us.ibm.com>, VM maintainers
5 /sys/kernel/mm/ should contain any and all VM
|
| /OK3568_Linux_fs/kernel/arch/s390/ |
| H A D | Kconfig | 828 handling under VM. If running native or in LPAR, this option
829 has no effect. If your VM does not support PFAULT, PAGEEX
831 Note that VM 4.2 supports PFAULT but has a bug in its
833 Everybody who wants to run Linux under VM != VM4.2 should select
843 makes sense for a system running under VM where the unused pages
844 will be reused by VM for other guest systems. The interface
846 Everybody who wants to run Linux under VM should select this
859 prompt "Linux - VM Monitor Stream, base infrastructure"
862 This provides a kernel interface for creating and updating z/VM APPLDATA
878 This provides memory management related data to the Linux - VM Monitor
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/networking/ |
| H A D | net_failover.rst | 24 datapath. It also enables hypervisor controlled live migration of a VM with
58 Booting a VM with the above configuration will result in the following 3
59 netdevs created in the VM.
76 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode
|
| /OK3568_Linux_fs/kernel/Documentation/virt/kvm/ |
| H A D | s390-pv-boot.rst | 35 related operations for virtual machines. The VM can set and retrieve
37 request VM memory and subsystem resets, as well as IPLs.
72 UV will clear all memory when a secure VM is removed, and therefore
|
| H A D | running-nested-guests.rst | 31 - L1 – level-1 guest; a VM running on L0; also called the "guest
34 - L2 – level-2 guest; a VM running on L1, this is the "nested guest"
67 - VM image creation tools (e.g. ``virt-install``, etc) often run
68 their own VM, and users expect these to work inside a VM.
|
| H A D | amd-memory-encryption.rst | 12 the memory contents of a VM will be transparently encrypted with a key
13 unique to that VM.
36 When SEV support is available, it can be enabled in a specific VM by
43 SEV hardware uses ASIDs to associate a memory encryption key with a VM.
|
| H A D | api.rst | 17 - VM ioctls: These query and set attributes that affect an entire virtual
18 machine, for example memory layout. In addition a VM ioctl is used to
21 VM ioctls must be issued from the same process (address space) that was
22 used to create the VM.
36 was used to create the VM.
44 handle will create a VM file descriptor which can be used to issue VM
45 ioctls. A KVM_CREATE_VCPU or KVM_CREATE_DEVICE ioctl on a VM fd will
58 It is important to note that althought VM ioctls may only be issued from
59 the process that created the VM, a VM's lifecycle is associated with its
60 file descriptor, not its creator (process). In other words, the VM and
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/tty/hvc/ |
| H A D | Kconfig | 45 bool "z/VM IUCV Hypervisor console support (VM only)"
52 a Linux (console) terminal via a z/VM IUCV communication path.
|
| /OK3568_Linux_fs/kernel/drivers/s390/block/ |
| H A D | Kconfig | 64 Disks under VM. If you are not running under VM or unsure what it is,
|
| /OK3568_Linux_fs/kernel/Documentation/hwmon/ |
| H A D | ltc2947.rst | 41 in0_input VP-VM voltage (mV).
49 in0_label Channel label (VP-VM)
|
| /OK3568_Linux_fs/kernel/Documentation/features/vm/pte_special/ |
| H A D | arch-support.txt | 4 # description: arch supports the pte_special()/pte_mkspecial() VM APIs
|