Searched full:vm (Results 1 – 25 of 120) sorted by relevance
12345
| /Documentation/virt/ |
| 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 …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | moortec,mr75203.yaml | 28 - const: vm
30 intel,vm-map:
32 PVT controller has 5 VM (voltage monitor) sensors.
33 vm-map defines CPU core to VM instance mapping. A
34 value of 0xff means that VM sensor is unused.
51 - intel,vm-map
66 reg-names = "common", "ts", "pd", "vm";
67 intel,vm-map = [03 01 04 ff ff];
|
| /Documentation/virt/kvm/devices/ |
| 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
|
| 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 :
|
| D | index.rst | 17 vm
|
| /Documentation/vm/ |
| 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 …]
|
| D | hwpoison.rst | 14 This patchkit implements the necessary infrastructure in the VM.
30 here is that we can access any page asynchronous to other VM
44 a new page poison bit and various checks in the VM to handle poisoned
61 vm.memory_failure_recovery sysctl set to zero:
81 vm.memory_failure_recovery
84 vm.memory_failure_early_kill
|
| D | overcommit-accounting.rst | 34 The overcommit policy is set via the sysctl ``vm.overcommit_memory``.
36 The overcommit amount can be set via ``vm.overcommit_ratio`` (percentage)
37 or ``vm.overcommit_kbytes`` (absolute value).
|
| D | page_owner.rst | 66 more accurately. On 2GB memory x86-64 VM box, 13343 early allocated pages
76 cd tools/vm
|
| D | active_mm.rst | 37 switching the VM state around. Currently only the old-style bdflush
72 no real VM has yet been created. So code that used to check
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| 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
|
| /Documentation/s390/ |
| 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 …]
|
| 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,
98 with emulated 3270s, as soon as you dial into your vm guest using the
104 3. Define graphic devices to your vm guest machine, if you
149 x3270 vm-esa-domain-name &
155 The screen you should now see contains a VM logo with input
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-mm | 3 Contact: Nishanth Aravamudan <nacc@us.ibm.com>, VM maintainers
5 /sys/kernel/mm/ should contain any and all VM
|
| /Documentation/powerpc/ |
| 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 …]
|
| /Documentation/admin-guide/laptops/ |
| D | laptop-mode.rst | 82 Laptop mode is controlled by the knob /proc/sys/vm/laptop_mode. This knob is
95 /proc/sys/vm to about 10 minutes (by default), which means that pages that are
105 gather information by setting the flag /proc/sys/vm/block_dump. When this flag
170 the /proc/sys/vm/dirty_ratio sysctl.
176 this nice and low. This corresponds to the /proc/sys/vm/dirty_background_ratio
429 if [ ! -e /proc/sys/vm/laptop_mode ] ; then
434 if [ ! -w /proc/sys/vm/laptop_mode ] ; then
555 if [ -d /proc/sys/vm/pagebuf ] ; then
559 echo $XFS_AGE > /proc/sys/vm/pagebuf/lm_flush_age
583 echo 1 > /proc/sys/vm/laptop_mode
[all …]
|
| /Documentation/virt/kvm/ |
| 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 …]
|
| 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
|
| 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.
|
| /Documentation/devicetree/bindings/regulator/ |
| D | mt6380-regulator.txt | 13 ldo-vm ,ldo-va , ldo-vphy, ldo-vddr, ldo-vt
45 mt6380_vm_reg: ldo-vm {
46 regulator-name = "vm";
|
| /Documentation/admin-guide/mm/ |
| D | hugetlbpage.rst | 60 the pool above the value in ``/proc/sys/vm/nr_hugepages``. The
62 ``/proc/sys/vm/nr_overcommit_hugepages``.
77 ``/proc/sys/vm/nr_hugepages`` indicates the current number of "persistent" huge
149 When multiple huge page sizes are supported, ``/proc/sys/vm/nr_hugepages``
154 echo 20 > /proc/sys/vm/nr_hugepages
185 ``/proc/sys/vm/nr_overcommit_hugepages`` specifies how large the pool of
186 huge pages can grow, if more huge pages than ``/proc/sys/vm/nr_hugepages`` are
214 the huge page userspace interface in ``/proc/sys/vm`` has been duplicated in
253 >/proc/sys/vm/nr_hugepages_mempolicy
257 numactl -m <node-list> echo 20 >/proc/sys/vm/nr_hugepages_mempolicy
[all …]
|
| /Documentation/networking/ |
| 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
|
| /Documentation/admin-guide/sysctl/ |
| D | vm.rst | 2 Documentation for /proc/sys/vm/
16 /proc/sys/vm and is valid for Linux kernel version 2.6.29.
19 of the virtual memory (VM) subsystem of the Linux kernel and
25 Currently, these files are in /proc/sys/vm:
244 echo 1 > /proc/sys/vm/drop_caches
248 echo 2 > /proc/sys/vm/drop_caches
252 echo 3 > /proc/sys/vm/drop_caches
256 `sync` prior to writing to /proc/sys/vm/drop_caches. This will minimize the
314 This parameter tells the VM to keep extra free memory between the threshold
377 % cat /proc/sys/vm/lowmem_reserve_ratio
[all …]
|
| /Documentation/hwmon/ |
| D | ltc2947.rst | 41 in0_input VP-VM voltage (mV).
49 in0_label Channel label (VP-VM)
|
| /Documentation/accounting/ |
| D | taskstats-struct.rst | 162 * Same as acct_rss_mem1 above except that we keep track of VM usage.
164 __u64 virtmem; /* accumulated VM usage in MB-usec */
169 /* High watermark of VM usage in duration of a task, in KBytes. */
|
12345