Searched refs:VM (Results 1 – 25 of 88) sorted by relevance
1234
| /Linux-v4.19/net/iucv/ |
| D | Kconfig | 4 prompt "IUCV support (S390 - z/VM only)"
7 under VM or VIF. If you run on z/VM, say "Y" to enable a fast
8 communication link between VM guests.
13 prompt "AF_IUCV Socket support (S390 - z/VM and HiperSockets transport)"
16 based on z/VM inter-user communication vehicle or based on
|
| /Linux-v4.19/drivers/s390/char/ |
| D | Kconfig | 161 prompt "Support for the z/VM recording system services (VM only)"
165 by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
171 prompt "Support for the z/VM CP interface"
176 program on z/VM
179 int "Memory in MiB reserved for z/VM CP interface"
183 Specify the default amount of memory in MiB reserved for the z/VM CP
190 prompt "API for reading z/VM monitor service records"
193 Character device driver for reading z/VM monitor service records
197 prompt "API for writing z/VM monitor service records"
200 Character device driver for writing z/VM monitor service records
[all …]
|
| /Linux-v4.19/drivers/s390/net/ |
| 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 in QDIO mode (all media types), HiperSockets interfaces and z/VM
|
| /Linux-v4.19/Documentation/virtual/kvm/devices/ |
| D | vfio.txt | 7 Only one VFIO instance may be created per VM. The created device
8 tracks VFIO groups in use by the VM and features of those groups
9 important to the correctness and acceleration of the VM. As groups
10 are enabled and disabled for use by the VM, KVM should be updated
|
| D | vm.txt | 6 struct kvm_device_attr as other devices, but targets VM-wide settings
80 are not handled by KVM need to by imlemented in the VM driver code.
106 VM. Features that are not available cannot be enabled.
154 all VCPUs of a VM. This attribute will only be available if kernel and
258 -EINVAL if the state of the VM is invalid (e.g. no memory defined)
|
| /Linux-v4.19/Documentation/vm/ |
| D | page_migration.rst | 163 To overclome the problem, VM supports non-LRU page migration which provides
172 What VM expects on isolate_page function of driver is to return *true*
173 if driver isolates page successfully. On returing true, VM marks the page
177 Once page is successfully isolated, VM uses page.lru fields so driver
183 After isolation, VM calls migratepage of driver with isolated page.
186 indicate to the VM the oldpage is no longer movable via __ClearPageMovable()
189 can return -EAGAIN. On -EAGAIN, VM will retry page migration in a short time
190 because VM interprets -EAGAIN as "temporal migration failure". On returning
191 any error except -EAGAIN, VM will give up the page migration without retrying
194 Driver shouldn't touch page.lru field VM using in the functions.
[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
|
| 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
|
| /Linux-v4.19/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
|
| /Linux-v4.19/Documentation/s390/ |
| D | monreader.txt | 6 Linux API for read access to z/VM Monitor Records
13 usable from user space and allows read access to the z/VM Monitor Records
14 collected by the *MONITOR System Service of z/VM.
19 The z/VM guest on which you want to access this API needs to be configured in
23 This item will use the IUCV device driver to access the z/VM services, so you
24 need a kernel with IUCV support. You also need z/VM version 4.4 or 5.1.
74 Refer to the "z/VM Performance" book (SC24-6109-00) on how to create a monitor
75 DCSS if your z/VM doesn't have one already, you need Class E privileges to
136 See "Appendix A: *MONITOR" in the "z/VM Performance" document for a description
138 be found here (z/VM 5.1): http://www.vm.ibm.com/pubs/mon510/index.html
[all …]
|
| D | 3270.txt | 18 VM-ESA operating system, define a 3270 to your virtual machine by using
27 Your network connection from VM-ESA allows you to use x3270, tn3270, or
51 configuration file under /etc/modprobe.d/. If you are working on a VM
55 other, or neither. If you generate both, the console type under VM is
64 3. (If VM) define devices with DEF GRAF
68 To test that everything works, assuming VM and x3270,
141 The screen you should now see contains a VM logo with input
176 If so, you must issue the command "DEF GRAF 620" from your VM
|
| D | Debugging390.txt | 29 Debugging under VM
31 Debugging IO on s/390 & z/Architecture under VM
110 ( useful info for debugging under VM ).
219 If using the virtual machine ( VM ) as a debugger it is quite difficult to
744 Debugging under VM
749 Addresses & values in the VM debugger are always hex never decimal
755 The VM Debugger is case insensitive.
757 VM's strengths are usually other debuggers weaknesses you can get at any
762 The VM Debugger displays operators but not operands, and also the debugger
795 Useful VM debugger commands
[all …]
|
| D | 00-INDEX | 20 - information on accessing the z/VM monitor stream from Linux.
|
| /Linux-v4.19/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
|
| /Linux-v4.19/arch/s390/ |
| D | Kconfig | 838 handling under VM. If running native or in LPAR, this option
839 has no effect. If your VM does not support PFAULT, PAGEEX
841 Note that VM 4.2 supports PFAULT but has a bug in its
843 Everybody who wants to run Linux under VM != VM4.2 should select
853 makes sense for a system running under VM where the unused pages
854 will be reused by VM for other guest systems. The interface
856 Everybody who wants to run Linux under VM should select this
869 prompt "Linux - VM Monitor Stream, base infrastructure"
872 This provides a kernel interface for creating and updating z/VM APPLDATA
888 This provides memory management related data to the Linux - VM Monitor
[all …]
|
| /Linux-v4.19/drivers/tty/hvc/ |
| D | Kconfig | 46 bool "z/VM IUCV Hypervisor console support (VM only)"
53 a Linux (console) terminal via a z/VM IUCV communication path.
|
| /Linux-v4.19/Documentation/features/vm/pte_special/ |
| D | arch-support.txt | 4 # description: arch supports the pte_special()/pte_mkspecial() VM APIs
|
| /Linux-v4.19/Documentation/features/vm/huge-vmap/ |
| D | arch-support.txt | 4 # description: arch supports the ioremap_pud_enabled() and ioremap_pmd_enabled() VM APIs
|
| /Linux-v4.19/arch/arc/ |
| D | Kconfig.debug | 10 on the VM subsystem for higher order allocations.
|
| /Linux-v4.19/drivers/s390/block/ |
| D | Kconfig | 65 Disks under VM. If you are not running under VM or unsure what it is,
|
| /Linux-v4.19/Documentation/virtual/kvm/ |
| 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.
|
| /Linux-v4.19/tools/perf/trace/beauty/ |
| D | clone.c | 24 P_FLAG(VM); in clone__scnprintf_flags()
|
| /Linux-v4.19/Documentation/arm/ |
| D | memory.txt | 15 certain regions of VM space for use for new facilities; therefore
16 this document may reserve more VM space over time.
|
| /Linux-v4.19/drivers/firmware/tegra/ |
| D | Kconfig | 7 IVC (Inter-VM Communication) protocol is part of the IPC
|
| /Linux-v4.19/Documentation/accounting/ |
| D | taskstats-struct.txt | 149 * Same as acct_rss_mem1 above except that we keep track of VM usage.
151 __u64 virtmem; /* accumulated VM usage in MB-usec */
156 /* High watermark of VM usage in duration of a task, in KBytes. */
|
1234
