Searched full:vcpu0 (Results 1 – 10 of 10) sorted by relevance
160 * 2. All other channels notify vcpu0 by default. This default is set when162 * has its binding reset to vcpu0).
86 * allocated to VCPU0 but can subsequently be re-bound.
67 In the output above, for vcpu0, there have been 6839 dispatches since
210 struct kvm_vcpu *vcpu0 = kvm_get_vcpu(kvm, 0); in kvm_vgic_dist_init() local233 irq->target_vcpu = vcpu0; in kvm_vgic_dist_init()
223 /* Somewhat arbitrarily make vcpu0 the owner of the PIT. */ in __kvm_migrate_pit_timer()
3089 * VCPU0 on CPU0 | VCPU1 on CPU1
1213 * New interdomain events are initially bound to vCPU0 This in bind_evtchn_to_irq_chip()
657 " E.g. to create 3 vCPUs, pin vCPU0=>pCPU22, vCPU1=>pCPU23,\n" in kvm_print_vcpu_pinning_help()
999 * index, clamping the index to 0 would return vCPU0, not NULL. in kvm_get_vcpu()
1809 * Make sure the dummy vCPU values for multi-MSI don't all point to vCPU0.