| /linux-4.4.14/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-4.4.14/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
78 are not handled by KVM need to by imlemented in the VM driver code.
|
| D | xics.txt | 66 Only one XICS instance may be created per VM.
|
| D | arm-vgic.txt | 9 legacy KVM_CREATE_IRQCHIP api. The created VGIC will act as the VM interrupt
|
| /linux-4.4.14/drivers/s390/net/ |
| D | Kconfig | 22 It also supports virtual CTCs when running under VM.
31 prompt "IUCV network device support (VM only)"
35 vehicle networking under VM or VIF. It enables a fast communication
36 link between VM guests. Using ifconfig a point-to-point connection
38 running on the other VM guest. To compile as a module, choose M.
43 prompt "IUCV special message support (VM only)"
47 from other VM guest systems.
51 prompt "Deliver IUCV special messages as uevents (VM only)"
66 in QDIO mode (all media types), HiperSockets interfaces and z/VM
|
| /linux-4.4.14/drivers/s390/char/ |
| D | Kconfig | 165 prompt "Support for the z/VM recording system services (VM only)"
169 by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
175 prompt "Support for the z/VM CP interface"
179 program on z/VM
183 prompt "API for reading z/VM monitor service records"
186 Character device driver for reading z/VM monitor service records
190 prompt "API for writing z/VM monitor service records"
193 Character device driver for writing z/VM monitor service records
197 prompt "z/VM unit record device driver"
200 Character device driver for z/VM reader, puncher and printer.
|
| /linux-4.4.14/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-4.4.14/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.
|
| D | qeth.txt | 9 "z/VM Connectivity, SC24-6174".
|
| D | DASD | 26 sizes, under VM and on the bare hardware (LPAR), using internal disks
|
| D | s390dbf.txt | 479 under VM or at the Service Element.
|
| /linux-4.4.14/arch/s390/ |
| D | Kconfig | 748 handling under VM. If running native or in LPAR, this option
749 has no effect. If your VM does not support PFAULT, PAGEEX
751 Note that VM 4.2 supports PFAULT but has a bug in its
753 Everybody who wants to run Linux under VM != VM4.2 should select
757 bool "VM shared kernel support"
761 Linux kernel between different VM guests. This reduces memory
775 makes sense for a system running under VM where the unused pages
776 will be reused by VM for other guest systems. The interface
778 Everybody who wants to run Linux under VM should select this
791 prompt "Linux - VM Monitor Stream, base infrastructure"
[all …]
|
| /linux-4.4.14/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-4.4.14/arch/arc/ |
| D | Kconfig.debug | 12 on the VM subsystem for higher order allocations.
|
| /linux-4.4.14/Documentation/features/vm/pmdp_splitting_flush/ |
| D | arch-support.txt | 4 # description: arch supports the pmdp_splitting_flush() VM API
|
| /linux-4.4.14/Documentation/features/vm/pte_special/ |
| D | arch-support.txt | 4 # description: arch supports the pte_special()/pte_mkspecial() VM APIs
|
| /linux-4.4.14/Documentation/features/vm/huge-vmap/ |
| D | arch-support.txt | 4 # description: arch supports the ioremap_pud_enabled() and ioremap_pmd_enabled() VM APIs
|
| /linux-4.4.14/drivers/s390/block/ |
| D | Kconfig | 62 Disks under VM. If you are not running under VM or unsure what it is,
|
| /linux-4.4.14/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-4.4.14/Documentation/virtual/kvm/arm/ |
| D | vgic-mapped-irqs.txt | 6 allowing software to inject virtual interrupts to a VM, which the guest
64 - KVM clears the LR on VM exits when the physical distributor
88 always run the VM with interrupts enabled on the CPU, a pending
129 for physical LPIs that are forwarded to a VM as virtual interrupts,
173 4. At T+100 the timer fires and a physical IRQ causes the VM to exit
|
| /linux-4.4.14/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. */
|
| /linux-4.4.14/arch/mips/kvm/ |
| D | Kconfig | 42 A histogram of COP0 accesses is printed when the VM is
|
| /linux-4.4.14/arch/metag/ |
| D | Kconfig.debug | 16 on the VM subsystem for higher order allocations. This option
|
| /linux-4.4.14/Documentation/vm/ |
| D | hwpoison.txt | 7 This patchkit implements the necessary infrastructure in the VM.
23 * here is that we can access any page asynchronous to other VM
37 a new page poison bit and various checks in the VM to handle poisoned
|
| D | active_mm.txt | 29 switching the VM state around. Currently only the old-style bdflush
64 no real VM has yet been created. So code that used to check
|
| D | page_owner.txt | 59 more accurately. On 2GB memory x86-64 VM box, 13343 early allocated pages
|
| D | transhuge.txt | 49 immediately in the buddy or through the VM), guest physical memory
69 and all other advanced VM features to be available on the
106 It's also possible to limit defrag efforts in the VM to generate
325 calling split_huge_page(page). This is what the Linux VM does before
|
| D | highmem.txt | 36 VM space so that we don't have to pay the full TLB invalidation costs for
|
| /linux-4.4.14/Documentation/ja_JP/ |
| D | SubmitChecklist | 110 VM, VFS およびその他のサブシステムに関する様々な変更と、現時点でも共存
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | vfs.txt | 313 the VM is trying to reclaim under GFP_NOFS conditions, hence this
512 The first can be used independently to the others. The VM can try to
545 cause various VM routines to make extra calls into the address_space
607 writepage: called by the VM to write a dirty page to backing store.
620 should return AOP_WRITEPAGE_ACTIVATE so that the VM will not keep
625 readpage: called by the VM to read a page from backing store.
633 writepages: called by the VM to write out pages associated with the
642 set_page_dirty: called by the VM to set a page dirty.
650 readpages: called by the VM to read pages associated with the address_space
725 first is when the VM finds a clean page with no active users and
[all …]
|
| D | Locking | 265 currently, and VM should stop calling ->writepage() on this page for some
266 time. VM does this by moving page to the head of the active list, hence the
546 locked. The VM will unlock the page.
548 ->map_pages() is called when VM asks to map easy accessible pages.
562 will cause the VM to retry the fault.
|
| D | ramfs-rootfs-initramfs.txt | 18 store, but kept around for caching purposes until the VM reallocates the
25 VM when it's looking to recycle memory.
61 up all memory, and the VM can't free it because the VM thinks that files
|
| D | proc.txt | 929 by the VM and can be used at any time by the allocating
|
| /linux-4.4.14/arch/arc/mm/ |
| D | tlbex.S | 332 ; Let Linux VM know that the page was accessed
387 ; UPDATE_PTE: Let Linux VM know that page was accessed/dirty
|
| /linux-4.4.14/Documentation/ |
| D | nommu-mmap.txt | 21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write
24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
36 In the MMU case: VM regions backed by pages read from file; changes to
71 In the MMU case: VM regions backed by pages read from file; changes to
|
| D | robust-futexes.txt | 124 over every vma (!), which the VM-based method has to do. Only a very
127 - no VM changes are needed - 'struct address_space' is left alone.
142 interactions with the VM.
|
| D | SubmitChecklist | 93 changes in the VM, VFS, and other subsystems.
|
| D | gdb-kernel-debugging.txt | 40 - at VM startup time by appending "-s" to the QEMU command line
|
| D | java.txt | 178 /* From Sun's Java VM Specification, as tag entries in the constant pool. */
|
| D | kernel-parameters.txt | 1334 hvc_iucv= [S390] Number of z/VM IUCV hypervisor console (HVC)
1336 hvc_iucv_allow= [S390] Comma-separated list of z/VM user IDs.
1337 If specified, z/VM IUCV HVC accepts connections
1338 from listed z/VM user IDs only.
3018 Param: "kvm" - profile VM exits.
4035 vmhalt= [KNL,S390] Perform z/VM CP command after system halt.
4038 vmpanic= [KNL,S390] Perform z/VM CP command after kernel panic.
4041 vmpoff= [KNL,S390] Perform z/VM CP command after power off.
|
| D | cachetlb.txt | 7 by the Linux VM subsystem. It enumerates over each interface,
|
| D | vfio.txt | 15 turns the VM into a userspace driver, with the benefits of
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | head.S | 225 # reset files in VM reader
228 tm .Lcpuid,0xff # running VM ?
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | memory.txt | 36 for fun (to learn and hack on the VM subsystem).
171 are not accounted. We just account pages under usual VM management.
191 of used pages; not-on-LRU pages tend to be out-of-control from VM view.
244 global VM. When a cgroup goes over its limit, we first try
521 recent_rotated_anon - VM internal parameter. (see mm/vmscan.c)
522 recent_rotated_file - VM internal parameter. (see mm/vmscan.c)
523 recent_scanned_anon - VM internal parameter. (see mm/vmscan.c)
524 recent_scanned_file - VM internal parameter. (see mm/vmscan.c)
|
| D | memcg_test.txt | 5 Because VM is getting complex (one of reasons is memcg...), memcg's behavior
110 VM's control (means that it's handled under global zone->lru_lock).
|
| /linux-4.4.14/arch/sh/ |
| D | Kconfig.debug | 38 on the VM subsystem for higher order allocations. This option
|
| /linux-4.4.14/Documentation/networking/ |
| D | ixgbe.txt | 316 KVM Hypervisor/VMM supports direct assignment of a PCIe device to a VM. This
321 to a Linux-based VM running 2.6.32 or later kernel works fine, there is a
322 known issue with Microsoft Windows Server 2008 VM that results in a "yellow
|
| /linux-4.4.14/arch/cris/arch-v10/ |
| D | README.mm | 13 Added discussion of paging and VM.
212 The VM system
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | api.txt | 14 - VM ioctls: These query and set attributes that affect an entire virtual
15 machine, for example memory layout. In addition a VM ioctl is used to
18 Only run VM ioctls from the same process (address space) that was used
19 to create the VM.
34 handle will create a VM file descriptor which can be used to issue VM
35 ioctls. A KVM_CREATE_VCPU ioctl on a VM fd will create a virtual cpu
111 Returns: a VM fd that can be used to control the new virtual machine.
113 The new VM has no virtual cpus and no memory. An mmap() of a VM fd
115 corresponds to guest physical address zero. Use of mmap() on a VM fd
1311 Assigns a host PCI device to the VM.
[all …]
|
| D | locking.txt | 175 When VT-d posted-interrupts is supported and the VM has assigned
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | ramdisk.txt | 23 so that the VM subsystem does not try to reclaim them later.
|
| /linux-4.4.14/arch/frv/ |
| D | Kconfig | 98 The VM uses one page of memory for each page table. For systems
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | vm.txt | 13 of the virtual memory (VM) subsystem of the Linux kernel and
426 This is used to force the Linux VM to keep a minimum number
427 of kilobytes free. The VM uses this number to compute a
|
| /linux-4.4.14/mm/ |
| D | Kconfig | 587 architecture (ex, ARM) performs VM mapping faster than copying,
614 This is the maximum stack size in Megabytes in the VM layout of 32-bit
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 557 bool "Debug VM"
576 bool "Debug VM red-black trees"
579 Enable VM red-black tree debugging information and extra validations.
584 bool "Debug VM translations"
604 The sanity checks verify aspects of the VM such as the memory model
|
| /linux-4.4.14/arch/m68k/ |
| D | Kconfig.cpu | 366 Ignore all but the first contiguous chunk of physical memory for VM
|
| D | Kconfig.machine | 322 on the VM subsystem for higher order allocations.
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | thin-provisioning.txt | 210 One use case for this is VM hosts that want to run guests on
|
| /linux-4.4.14/init/ |
| D | Kconfig | 1685 bool "Enable VM event counters for /proc/vmstat" if EXPERT
1687 VM event counters are needed for event counts to be shown.
1688 This option allows the disabling of the VM event counters
1690 if VM event counters are disabled.
|
| /linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/ce/fuc/ |
| D | com.fuc | 218 // set context pointer, from within channel VM
|
| /linux-4.4.14/Documentation/block/ |
| D | biodoc.txt | 592 deadlock-free allocations during extreme VM load. For example, the VM
1162 8.9. VM reservations patch (Ben LaHaise)
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi_fc_transport.txt | 136 a hypervisor could set this string to "Xen Domain 2 VM 5 Vport 2",
|
| /linux-4.4.14/Documentation/RCU/ |
| D | RTFP.txt | 24 of "quiescent states" in the VM/XA hypervisor that are guaranteed not
878 Described the relationship of the VM/XA passive serialization to RCU.
|
| /linux-4.4.14/drivers/net/wireless/ipw2x00/ |
| D | ipw2200.c | 53 #define VM "m" macro
55 #define VM macro
76 #define IPW2200_VERSION "1.2.2" VK VD VM VP VR VQ
|
| /linux-4.4.14/drivers/watchdog/ |
| D | Kconfig | 1447 IBM s/390 and zSeries machines running under z/VM 5.1 or later
|
| /linux-4.4.14/ |
| D | CREDITS | 135 D: VM hacker
3056 D: kswapd fixes, random kernel hacker, rmap VM,
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig | 1684 The VM uses one page of physical memory for each page table.
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig | 1462 The VM uses one page table entry for each page of physical memory.
|