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
284 This ioctl is used to run a guest virtual cpu. While there are no
432 This injects an edge type external interrupt into the guest once it's ready
443 This injects a level type external interrupt into the guest context. The
661 should not present interrupts to the guest as active-low unless this
745 Sets the MSR that the Xen HVM guest uses to initialize its hypercall
747 blobs in userspace. When the guest writes the MSR, kvm copies one
748 page of a blob (32- or 64-bit, depending on the vcpu mode) to guest
770 Gets the current timestamp of kvmclock as seen by the current guest. In
933 This ioctl allows the user to create or modify a guest physical memory
934 slot. When changing an existing slot, it may be moved in the guest
936 resized. Slots may not overlap in guest physical address space.
951 be identical. This allows large pages in the guest to be backed by large
962 the memory region are automatically reflected into the guest. For example, an
979 This ioctl defines the physical address of a three-page region in the guest
981 guest physical address space and must not conflict with any memory slot
982 or any mmio address. The guest may malfunction if it accesses this memory
1000 can enable an extension, making it available to the guest.
1099 This ioctl defines the physical address of a one-page region in the guest
1101 guest physical address space and must not conflict with any memory slot
1102 or any mmio address. The guest may malfunction if it accesses this memory
1290 This ioctl fetches PV specific information that need to be passed to the guest
1337 guest's view on the INTx mask, see KVM_ASSIGN_SET_INTX_MASK for details.
1402 It is not valid to specify multiple types per host or guest IRQ. However, the
1403 IRQ type of host and guest can differ or can even be null.
1424 KVM_ASSIGN_DEV_IRQ. Partial deassignment of host or guest IRQ is allowed.
1553 Returns the tsc frequency of the guest. The unit of the return value is
1601 within the guest. A guest write in the registered address will signal the
1631 the kernel will ignore the length of guest write and may get a faster vmexit.
1677 kernel will not deliver INTx interrupts to the guest between setting and
1683 read value of the INTx disable bit in the guest visible PCI command register.
1690 therefore not match the expected value. Writes should always use the guest
1695 guest.
1712 logical addresses used in virtual I/O into guest physical addresses,
1726 When the guest issues an H_PUT_TCE hcall on a liobn for which a TCE
1749 will be accessed by real-mode (MMU off) accesses in a KVM guest.
2088 always accessed according to the current guest FPU mode (Status.FR and
2089 Config5.FRE), i.e. as the guest would see them, and they become unpredictable
2090 if the guest FPU mode is changed. MIPS SIMD Architecture (MSA) vector
2131 This signals to the host kernel that the specified guest is being paused by
2134 is shared between guest and host, specifically the second bit of the flags
2136 the host and read/cleared exclusively by the guest. The guest operation of
2139 where the guest will clear the flag: when the soft lockup watchdog timer resets
2150 Returns: >0 on delivery, 0 if guest blocked the MSI, and -1 on error
2192 When running a guest with elevated priorities, the scheduling parameters of
2248 device-tree properties for the guest operating system.
2263 When that flag is set, guest page sizes must "fit" the backing
2315 Allows setting an eventfd to directly trigger a guest interrupt.
2319 the guest using the specified gsi pin. The irqfd is removed using
2349 guest using the PAPR paravirtualization interface. This only does
2370 return the hash table order in the parameter. (If the guest is using
2382 Allows to inject an interrupt to the guest. Interrupts can be floating
2426 entries in the guest's hashed page table (HPT), or to write entries to
2553 This tells KVM what type of CPU to present to the guest, and what
2569 and execute guest code when KVM_RUN is called.
2616 This ioctl returns the guest registers that are supported for the
2631 E2BIG: Address outside guest physical address space
2639 Specify a device address in the guest's physical address space where guests
2652 as the device id. When setting the base address for the guest's
2675 subsequent RTAS calls by the guest specifying that token will be
2678 calls by the guest for that service will be passed to userspace to be
2696 handling guest debug events. There are two parts to the structure, the
2700 - KVM_GUESTDBG_ENABLE: guest debugging is enabled
2710 - KVM_GUESTDBG_EXIT_PENDING: trigger an immediate guest exit [s390]
2715 running off into the normal guest vector. For KVM_GUESTDBG_USE_HW_BP
2716 we need to ensure the guest vCPUs architecture specific registers are
2816 __u64 gaddr; /* the guest address */
2831 access exception occurred while walking the MMU tables of the guest, the
2853 Returns: 0 on success, KVM_S390_GET_KEYS_NONE if guest is not using storage
2856 This ioctl is used to get guest storage key values on the s390
2867 The start_gfn field is the number of the first guest frame whose storage keys
2886 This ioctl is used to set guest storage key values on the s390
2890 The start_gfn field is the number of the first guest frame whose storage keys
2922 Allows to inject an interrupt to the guest.
3014 for each interrupt to be injected into the guest.
3046 interrupts into the guest. Useful in conjunction with KVM_INTERRUPT.
3156 operations are complete (and guest state is consistent) only after userspace
3159 can re-enter the guest with an unmasked signal pending to complete
3234 hypercalls and exit with this exit struct that contains all the guest gprs.
3238 necessary. Upon guest entry all guest GPRs will then be replaced by the values
3250 guest does a hypercall using the 'sc 1' instruction. The 'nr' field
3251 contains the hypercall number (from the guest R3), and 'args' contains
3252 the arguments (from the guest R4 - R12). Userspace should put the
3290 external interrupt has just been delivered into the guest. User space
3310 KVM_SYSTEM_EVENT_SHUTDOWN -- the guest has requested a shutdown of the
3314 KVM_SYSTEM_EVENT_RESET -- the guest has requested a reset of the VM.
3317 KVM_SYSTEM_EVENT_CRASH -- the guest crash occurred and the guest
3353 certain guest registers without having to call SET/GET_*REGS. Thus we can
3397 be treated as normal system calls to be injected into the guest. OSI hypercalls
3399 between the guest and the host.
3414 It also sets the guest privilege level to "supervisor" mode. Usually the guest
3419 HTAB invisible to the guest.
3450 the guest's TLB. If userspace makes any changes, it must call KVM_DIRTY_TLB
3495 When enabled (args[0] != 0), every time the guest gets an external interrupt
3535 This capability allows the use of the host Floating Point Unit by the guest. It
3536 allows the Config1.FP bit to be set to enable the FPU in the guest. Once this is
3538 (depending on the current guest FPU register mode), and the Status.FR,
3539 Config5.FRE bits are accessible via the KVM API and also from the guest,
3548 This capability allows the use of the MIPS SIMD Architecture (MSA) by the guest.
3549 It allows the Config3.MSAP bit to be set to enable the use of MSA by the guest.
3552 the guest.
3644 @addr - guest address of STSI SYSIB
3686 If present, the kernel H_RANDOM handler can be enabled for guest use