Lines Matching refs:guest
38 actually running guest code.
115 corresponds to guest physical address zero. Use of mmap() on a VM fd
141 This ioctl returns the guest msrs that are supported. The list varies
223 Userspace can control the threading (SMT) mode of the guest by its
225 single-threaded guest vcpus, it should make all vcpu ids be a multiple
279 This ioctl is used to run a guest virtual cpu. While there are no
421 This injects an edge type external interrupt into the guest once it's ready
432 This injects a level type external interrupt into the guest context. The
650 should not present interrupts to the guest as active-low unless this
734 Sets the MSR that the Xen HVM guest uses to initialize its hypercall
736 blobs in userspace. When the guest writes the MSR, kvm copies one
737 page of a blob (32- or 64-bit, depending on the vcpu mode) to guest
759 Gets the current timestamp of kvmclock as seen by the current guest. In
909 This ioctl allows the user to create or modify a guest physical memory
910 slot. When changing an existing slot, it may be moved in the guest
912 resized. Slots may not overlap in guest physical address space.
920 be identical. This allows large pages in the guest to be backed by large
931 the memory region are automatically reflected into the guest. For example, an
948 This ioctl defines the physical address of a three-page region in the guest
950 guest physical address space and must not conflict with any memory slot
951 or any mmio address. The guest may malfunction if it accesses this memory
968 can enable an extension, making it available to the guest.
1067 This ioctl defines the physical address of a one-page region in the guest
1069 guest physical address space and must not conflict with any memory slot
1070 or any mmio address. The guest may malfunction if it accesses this memory
1258 This ioctl fetches PV specific information that need to be passed to the guest
1305 guest's view on the INTx mask, see KVM_ASSIGN_SET_INTX_MASK for details.
1370 It is not valid to specify multiple types per host or guest IRQ. However, the
1371 IRQ type of host and guest can differ or can even be null.
1392 KVM_ASSIGN_DEV_IRQ. Partial deassignment of host or guest IRQ is allowed.
1521 Returns the tsc frequency of the guest. The unit of the return value is
1569 within the guest. A guest write in the registered address will signal the
1641 kernel will not deliver INTx interrupts to the guest between setting and
1647 read value of the INTx disable bit in the guest visible PCI command register.
1654 therefore not match the expected value. Writes should always use the guest
1659 guest.
1676 logical addresses used in virtual I/O into guest physical addresses,
1690 When the guest issues an H_PUT_TCE hcall on a liobn for which a TCE
1713 will be accessed by real-mode (MMU off) accesses in a KVM guest.
2052 always accessed according to the current guest FPU mode (Status.FR and
2053 Config5.FRE), i.e. as the guest would see them, and they become unpredictable
2054 if the guest FPU mode is changed. MIPS SIMD Architecture (MSA) vector
2095 This signals to the host kernel that the specified guest is being paused by
2098 is shared between guest and host, specifically the second bit of the flags
2100 the host and read/cleared exclusively by the guest. The guest operation of
2103 where the guest will clear the flag: when the soft lockup watchdog timer resets
2114 Returns: >0 on delivery, 0 if guest blocked the MSI, and -1 on error
2156 When running a guest with elevated priorities, the scheduling parameters of
2212 device-tree properties for the guest operating system.
2227 When that flag is set, guest page sizes must "fit" the backing
2279 Allows setting an eventfd to directly trigger a guest interrupt.
2283 the guest using the specified gsi pin. The irqfd is removed using
2313 guest using the PAPR paravirtualization interface. This only does
2334 return the hash table order in the parameter. (If the guest is using
2346 Allows to inject an interrupt to the guest. Interrupts can be floating
2390 entries in the guest's hashed page table (HPT), or to write entries to
2517 This tells KVM what type of CPU to present to the guest, and what
2533 and execute guest code when KVM_RUN is called.
2580 This ioctl returns the guest registers that are supported for the
2595 E2BIG: Address outside guest physical address space
2603 Specify a device address in the guest's physical address space where guests
2616 as the device id. When setting the base address for the guest's
2639 subsequent RTAS calls by the guest specifying that token will be
2642 calls by the guest for that service will be passed to userspace to be
2660 handling guest debug events. There are two parts to the structure, the
2664 - KVM_GUESTDBG_ENABLE: guest debugging is enabled
2674 - KVM_GUESTDBG_EXIT_PENDING: trigger an immediate guest exit [s390]
2679 running off into the normal guest vector. For KVM_GUESTDBG_USE_HW_BP
2680 we need to ensure the guest vCPUs architecture specific registers are
2775 __u64 gaddr; /* the guest address */
2790 access exception occurred while walking the MMU tables of the guest, the
2812 Returns: 0 on success, KVM_S390_GET_KEYS_NONE if guest is not using storage
2815 This ioctl is used to get guest storage key values on the s390
2826 The start_gfn field is the number of the first guest frame whose storage keys
2845 This ioctl is used to set guest storage key values on the s390
2849 The start_gfn field is the number of the first guest frame whose storage keys
2881 Allows to inject an interrupt to the guest.
2973 for each interrupt to be injected into the guest.
2995 interrupts into the guest. Useful in conjunction with KVM_INTERRUPT.
3098 operations are complete (and guest state is consistent) only after userspace
3101 can re-enter the guest with an unmasked signal pending to complete
3176 hypercalls and exit with this exit struct that contains all the guest gprs.
3180 necessary. Upon guest entry all guest GPRs will then be replaced by the values
3192 guest does a hypercall using the 'sc 1' instruction. The 'nr' field
3193 contains the hypercall number (from the guest R3), and 'args' contains
3194 the arguments (from the guest R4 - R12). Userspace should put the
3232 external interrupt has just been delivered into the guest. User space
3251 KVM_SYSTEM_EVENT_SHUTDOWN -- the guest has requested a shutdown of the
3255 KVM_SYSTEM_EVENT_RESET -- the guest has requested a reset of the VM.
3278 certain guest registers without having to call SET/GET_*REGS. Thus we can
3322 be treated as normal system calls to be injected into the guest. OSI hypercalls
3324 between the guest and the host.
3339 It also sets the guest privilege level to "supervisor" mode. Usually the guest
3344 HTAB invisible to the guest.
3375 the guest's TLB. If userspace makes any changes, it must call KVM_DIRTY_TLB
3420 When enabled (args[0] != 0), every time the guest gets an external interrupt
3460 This capability allows the use of the host Floating Point Unit by the guest. It
3461 allows the Config1.FP bit to be set to enable the FPU in the guest. Once this is
3463 (depending on the current guest FPU register mode), and the Status.FR,
3464 Config5.FRE bits are accessible via the KVM API and also from the guest,
3473 This capability allows the use of the MIPS SIMD Architecture (MSA) by the guest.
3474 It allows the Config3.MSAP bit to be set to enable the use of MSA by the guest.
3477 the guest.
3569 @addr - guest address of STSI SYSIB
3591 If present, the kernel H_RANDOM handler can be enabled for guest use