Searched full:vcpu (Results 1 – 25 of 50) sorted by relevance
12
| /Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 4 KVM VCPU Requests
10 KVM supports an internal API enabling threads to request a VCPU thread to
11 perform some activity. For example, a thread may request a VCPU to flush
12 its TLB with a VCPU request. The API consists of the following functions::
14 /* Check if any requests are pending for VCPU @vcpu. */
15 bool kvm_request_pending(struct kvm_vcpu *vcpu);
17 /* Check if VCPU @vcpu has request @req pending. */
18 bool kvm_test_request(int req, struct kvm_vcpu *vcpu);
20 /* Clear request @req for VCPU @vcpu. */
21 void kvm_clear_request(int req, struct kvm_vcpu *vcpu);
[all …]
|
| D | api.rst | 24 - vcpu ioctls: These query and set attributes that control the operation
27 vcpu ioctls should be issued from the same thread that was used to create
28 the vcpu, except for asynchronous vcpu ioctl that are marked as such in
47 the new resource. Finally, ioctls on a vcpu or device fd can be used
48 to control the vcpu or device. For vcpus, this includes the important
111 system, vm, or vcpu.
275 :Returns: size of vcpu mmap area, in bytes
282 the VCPU file descriptor can be mmap-ed, including:
300 :Parameters: vcpu id (apic id on x86)
301 :Returns: vcpu fd on success, -1 on error
[all …]
|
| D | index.rst | 20 vcpu-requests
|
| /Documentation/arch/powerpc/ |
| D | vcpudispatch_stats.rst | 4 VCPU Dispatch Statistics
15 related to the vcpu dispatch behavior. Writing '1' to this file enables
17 By default, the DTLB log for each vcpu is processed 50 times a second so
23 a vcpu as represented by the first field, followed by 8 numbers.
27 1. total vcpu dispatches since the beginning of statistics collection
29 The next 4 numbers represent vcpu dispatch dispersions:
31 2. number of times this vcpu was dispatched on the same processor as last
33 3. number of times this vcpu was dispatched on a different processor core
35 4. number of times this vcpu was dispatched on a different chip
36 5. number of times this vcpu was dispatches on a different socket/drawer
[all …]
|
| D | kvm-nested.rst | 39 call made by the L1 to tell the L0 to start an L2 vCPU with the given
42 the L1 by the L0. The full L2 vCPU state is always transferred from
44 vCPU (except in the short sequence in the L0 on L1 -> L2 entry and L2
52 The L1 may run any L2 or vCPU without first informing the L0. It
53 simply starts the vCPU using h_enter_nested(). The creation of L2s and
68 and setting vCPU state can also be performed using h_guest_{g|s}et
79 - L1 requests the L0 create an L2 vCPU with H_GUEST_CREATE_VCPU()
81 - L1 and L0 communicate the vCPU state using the H_GUEST_{G,S}ET() hcall
83 - L1 requests the L0 runs the vCPU running H_GUEST_VCPU_RUN() hcall
154 H_Not_Enough_Resources: Unable to create Guest VCPU due to not
[all …]
|
| /Documentation/devicetree/bindings/misc/ |
| D | qemu,vcpu-stall-detector.yaml | 4 $id: http://devicetree.org/schemas/misc/qemu,vcpu-stall-detector.yaml#
7 title: VCPU stall detector
19 - qemu,vcpu-stall-detector
39 time spent while the VCPU is not running.
52 compatible = "qemu,vcpu-stall-detector";
|
| /Documentation/virt/kvm/s390/ |
| D | s390-pv-dump.rst | 39 the memory and the vcpu state.
41 The vcpu state contains all the important registers, general, floating
42 point, vector, control and tod/timers of a vcpu. The vcpu dump can
43 contain incomplete data if a vcpu is dumped while an instruction is
46 write out the encrypted vcpu state, but also the unencrypted state
63 decrypt the vcpu and memory data and end the dump process. When this
|
| D | s390-diag.rst | 105 other vcpu. An example is a Linux guest that tries to yield to the vcpu
108 However, on the host the real cpu backing the vcpu may itself not be
112 the guest's vcpu, to be scheduled.
|
| /Documentation/virt/kvm/devices/ |
| D | vcpu.rst | 4 Generic vcpu interface
9 kvm_device_attr as other devices, but targets VCPU-wide settings and controls.
31 -ENODEV KVM_ARM_VCPU_PMU_V3 feature missing from VCPU
38 number for this vcpu. This interrupt could be a PPI or SPI, but the interrupt
39 type must be same for each vcpu. As a PPI, the interrupt number is the same for
40 all vcpus, while as an SPI it must be a separate number per vcpu.
52 -ENXIO PMUv3 not supported, missing VCPU feature or interrupt
73 -EBUSY PMUv3 already initialized or a VCPU has already run
116 -EBUSY PMUv3 already initialized, a VCPU has already run or
124 Request that the VCPU uses the specified hardware PMU when creating guest events
[all …]
|
| D | xics.rst | 20 interrupt server numbers (ie, highest possible vcpu id plus one).
27 -EBUSY A vcpu is already connected to the device.
37 capability for each vcpu, specifying KVM_CAP_IRQ_XICS in args[0] and
38 the interrupt server number (i.e. the vcpu number from the XICS's
41 KVM_GET_ONE_REG and KVM_SET_ONE_REG ioctls on the vcpu. The 64 bit
69 interrupt server number specified for the destination vcpu.
|
| D | index.rst | 15 vcpu
|
| D | vm.rst | 24 :Returns: -EBUSY if a vcpu is already defined, otherwise 0
45 -EBUSY if a vcpu is already defined;
82 Allows user space to retrieve or request to change cpu related information for a vcpu::
85 __u64 cpuid; # CPUID currently (to be) used by this vcpu
86 __u16 ibc; # IBC level currently (to be) used by this vcpu
89 # by this vcpu
135 -EBUSY if at least one VCPU has already been defined;
144 done by a set IBC. These subfunctions are indicated to the guest VCPU via
201 -EBUSY if at least one VCPU has already been defined;
340 EBUSY A vCPU in the VM has already run
|
| D | arm-vgic-v3.rst | 31 VCPU and all of the redistributor pages are contiguous.
62 Note that to obtain reproducible results (the same VCPU being associated
63 with the same redistributor across a save/restore operation), VCPU creation
65 interleaves of VCPU and region creation MUST be preserved. Any change in
212 -EBUSY VCPU is running
249 -ENODEV no online VCPU
284 PPIs are reported per VCPU as specified in the mpidr field, and SPIs are
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 15 kernel for vCPU scheduling, memory management, inter-VM communication and virtio
25 - vCPU Management
28 CPUs. It requires Linux kernel in host VM for vCPU scheduling and VM power
75 - vcpu
77 The vcpu component is the core of virtualizing an aarch64 physical CPU, and it
78 controls the vCPU lifecycle including creating, running and destroying.
|
| /Documentation/virt/kvm/x86/ |
| D | msr.rst | 79 write, or registration, is needed for each VCPU. The interval between
92 the tsc value at the current VCPU at the time
139 | | | guest vcpu has been paused by |
210 when asynchronous page faults are enabled on the vcpu, 0 when disabled.
211 Bit 1 is 1 if asynchronous page faults can be injected when vcpu is in
256 same vcpu as 'page not present' event was, but guest should not rely on
277 write, or registration, is needed for each VCPU. The interval between
296 the amount of time in which this vCPU did not run, in
297 nanoseconds. Time during which the vcpu is idle, will not be
301 indicate the vCPU who owns this struct is running or
[all …]
|
| D | errata.rst | 44 allows sending events to a single vCPU using its x2APIC ID even if the target
45 vCPU has legacy xAPIC enabled, e.g. to bring up hotplugged vCPUs via INIT-SIPI
48 only to the vCPU with the lowest vCPU ID. If KVM_X2APIC_API_USE_32BIT_IDS is
|
| D | hypercalls.rst | 91 :Purpose: Hypercall used to wakeup a vcpu from HLT state
93 A vcpu of a paravirtualized guest that is busywaiting in guest
97 the vcpu to sleep until occurrence of an appropriate event. Another vcpu of the
98 same guest can wakeup the sleeping vcpu by issuing KVM_HC_KICK_CPU hypercall,
99 specifying APIC ID (a1) of the vcpu to be woken up. An additional argument (a0)
166 :Purpose: Hypercall used to yield if the IPI target vCPU is preempted
|
| /Documentation/virt/kvm/arm/ |
| D | fw-pseudo-registers.rst | 30 - Only valid if the vcpu has the KVM_ARM_VCPU_PSCI_0_2 feature set
36 - Affects the whole VM (even if the register view is per-vcpu)
54 is available to the guest, but it is not needed on this VCPU.
71 and can be disabled by a vCPU. If
73 this vCPU.
75 The workaround is always active on this vCPU or it is not needed.
|
| D | pvtime.rst | 40 VCPU. On failure:
49 PV_TIME_ST returns the structure for the calling VCPU.
65 | | | | much time this VCPU thread |
72 The structure will be updated by the hypervisor prior to scheduling a VCPU. It
75 structure per VCPU of the guest.
82 :ref:`Documentation/virt/kvm/devices/vcpu.rst <kvm_arm_vcpu_pvtime_ctrl>`.
|
| D | vcpu-features.rst | 4 vCPU feature selection on arm64
33 ``KVM_RUN`` on at least one vCPU in the VM. Userspace can discover what fields
45 before accessing the rest of the vCPU's CPU register state. KVM may use the
|
| D | pkvm.rst | 74 Protected VMs are instantiated according to a fixed vCPU configuration
79 with the vCPU registers being initialised to their architecturally-defined
82 Where not defined by the architecture, the registers of a protected vCPU
|
| D | index.rst | 16 vcpu-features
|
| /Documentation/virt/ |
| D | guest-halt-polling.rst | 12 a remote vCPU to avoid sending an IPI (and the associated
24 Each vcpu has an adjustable guest_halt_poll_ns
|
| /Documentation/devicetree/bindings/regulator/ |
| D | 88pg86x.txt | 16 vcpu: buck1 {
|
| /Documentation/virt/gunyah/ |
| D | index.rst | 29 1. Hypervisor vCPU scheduling in which Gunyah hypervisor schedules vCPUS on
32 own vCPU's time slice to an owned-VM's vCPU via a hypercall.
|
12