/* * Initialization rules: there are multiple stages to the vgic * initialization, both for the distributor and the CPU interfaces. The basic * idea is that even though the VGIC is not functional or not requested from * user space, the critical path of the run loop can still call VGIC functions * that just won't do anything, without them having to check additional * initialization flags to ensure they don't look at uninitialized data * structures. * * Distributor: * * - kvm_vgic_early_init(): initialization of static data that doesn't * depend on any sizing information or emulation type. No allocation * is allowed there. * * - vgic_init(): allocation and initialization of the generic data * structures that depend on sizing information (number of CPUs, * number of interrupts). Also initializes the vcpu specific data * structures. Can be executed lazily for GICv2. * * CPU Interface: * * - kvm_vgic_vcpu_init(): initialization of static data that doesn't depend * on any sizing information. Private interrupts are allocated if not * already allocated at vgic-creation time.
*/
/* EARLY INIT */
/** * kvm_vgic_early_init() - Initialize static VGIC VCPU data structures * @kvm: The VM whose VGIC districutor should be initialized * * Only do initialization of static structures that don't require any * allocation or sizing information from userspace. vgic_init() called * kvm_vgic_dist_init() which takes care of the rest.
*/ void kvm_vgic_early_init(struct kvm *kvm)
{ struct vgic_dist *dist = &kvm->arch.vgic;
/** * kvm_vgic_create: triggered by the instantiation of the VGIC device by * user space, either through the legacy KVM_CREATE_IRQCHIP ioctl (v2 only) * or through the generic KVM_CREATE_DEVICE API ioctl. * irqchip_in_kernel() tells you if this function succeeded or not. * @kvm: kvm struct pointer * @type: KVM_DEV_TYPE_ARM_VGIC_V[23]
*/ int kvm_vgic_create(struct kvm *kvm, u32 type)
{ struct kvm_vcpu *vcpu; unsignedlong i; int ret;
/* * This function is also called by the KVM_CREATE_IRQCHIP handler, * which had no chance yet to check the availability of the GICv2 * emulation. So check this here again. KVM_CREATE_DEVICE does * the proper checks already.
*/ if (type == KVM_DEV_TYPE_ARM_VGIC_V2 &&
!kvm_vgic_global_state.can_emulate_gicv2) return -ENODEV;
/* * Ensure mutual exclusion with vCPU creation and any vCPU ioctls by: * * - Holding kvm->lock to prevent KVM_CREATE_VCPU from reaching * kvm_arch_vcpu_precreate() and ensuring created_vcpus is stable. * This alone is insufficient, as kvm_vm_ioctl_create_vcpu() drops * the kvm->lock before completing the vCPU creation.
*/
lockdep_assert_held(&kvm->lock);
/* * - Acquiring the vCPU mutex for every *online* vCPU to prevent * concurrent vCPU ioctls for vCPUs already visible to userspace.
*/
ret = -EBUSY; if (kvm_trylock_all_vcpus(kvm)) return ret;
/* * - Taking the config_lock which protects VGIC data structures such * as the per-vCPU arrays of private IRQs (SGIs, PPIs).
*/
mutex_lock(&kvm->arch.config_lock);
/* * - Bailing on the entire thing if a vCPU is in the middle of creation, * dropped the kvm->lock, but hasn't reached kvm_arch_vcpu_create(). * * The whole combination of this guarantees that no vCPU can get into * KVM with a VGIC configuration inconsistent with the VM's VGIC.
*/ if (kvm->created_vcpus != atomic_read(&kvm->online_vcpus)) goto out_unlock;
if (irqchip_in_kernel(kvm)) {
ret = -EEXIST; goto out_unlock;
}
kvm_for_each_vcpu(i, vcpu, kvm) { if (vcpu_has_run_once(vcpu)) goto out_unlock;
}
ret = 0;
/** * kvm_vgic_dist_init: initialize the dist data structures * @kvm: kvm struct pointer * @nr_spis: number of spis, frozen by caller
*/ staticint kvm_vgic_dist_init(struct kvm *kvm, unsignedint nr_spis)
{ struct vgic_dist *dist = &kvm->arch.vgic; struct kvm_vcpu *vcpu0 = kvm_get_vcpu(kvm, 0); int i;
dist->spis = kcalloc(nr_spis, sizeof(struct vgic_irq), GFP_KERNEL_ACCOUNT); if (!dist->spis) return -ENOMEM;
/* * In the following code we do not take the irq struct lock since * no other action on irq structs can happen while the VGIC is * not initialized yet: * If someone wants to inject an interrupt or does a MMIO access, we * require prior initialization in case of a virtual GICv3 or trigger * initialization when using a virtual GICv2.
*/ for (i = 0; i < nr_spis; i++) { struct vgic_irq *irq = &dist->spis[i];
/* Default GICv3 Maintenance Interrupt INTID, as per SBSA */ #define DEFAULT_MI_INTID 25
int kvm_vgic_vcpu_nv_init(struct kvm_vcpu *vcpu)
{ int ret;
guard(mutex)(&vcpu->kvm->arch.config_lock);
/* * Matching the tradition established with the timers, provide * a default PPI for the maintenance interrupt. It makes * things easier to reason about.
*/ if (vcpu->kvm->arch.vgic.mi_intid == 0)
vcpu->kvm->arch.vgic.mi_intid = DEFAULT_MI_INTID;
ret = kvm_vgic_set_owner(vcpu, vcpu->kvm->arch.vgic.mi_intid, vcpu);
/* * Enable and configure all SGIs to be edge-triggered and * configure all PPIs as level-triggered.
*/ for (i = 0; i < VGIC_NR_PRIVATE_IRQS; i++) { struct vgic_irq *irq = &vgic_cpu->private_irqs[i];
staticint vgic_allocate_private_irqs(struct kvm_vcpu *vcpu, u32 type)
{ int ret;
mutex_lock(&vcpu->kvm->arch.config_lock);
ret = vgic_allocate_private_irqs_locked(vcpu, type);
mutex_unlock(&vcpu->kvm->arch.config_lock);
return ret;
}
/** * kvm_vgic_vcpu_init() - Initialize static VGIC VCPU data * structures and register VCPU-specific KVM iodevs * * @vcpu: pointer to the VCPU being created and initialized * * Only do initialization, but do not actually enable the * VGIC CPU interface
*/ int kvm_vgic_vcpu_init(struct kvm_vcpu *vcpu)
{ struct vgic_cpu *vgic_cpu = &vcpu->arch.vgic_cpu; struct vgic_dist *dist = &vcpu->kvm->arch.vgic; int ret = 0;
ret = vgic_allocate_private_irqs(vcpu, dist->vgic_model); if (ret) return ret;
/* * If we are creating a VCPU with a GICv3 we must also register the * KVM io device for the redistributor that belongs to this VCPU.
*/ if (dist->vgic_model == KVM_DEV_TYPE_ARM_VGIC_V3) {
mutex_lock(&vcpu->kvm->slots_lock);
ret = vgic_register_redist_iodev(vcpu);
mutex_unlock(&vcpu->kvm->slots_lock);
} return ret;
}
/* * vgic_init: allocates and initializes dist and vcpu data structures * depending on two dimensioning parameters: * - the number of spis * - the number of vcpus * The function is generally called when nr_spis has been explicitly set * by the guest through the KVM DEVICE API. If not nr_spis is set to 256. * vgic_initialized() returns true when this function has succeeded.
*/ int vgic_init(struct kvm *kvm)
{ struct vgic_dist *dist = &kvm->arch.vgic; struct kvm_vcpu *vcpu; int ret = 0; unsignedlong idx;
lockdep_assert_held(&kvm->arch.config_lock);
if (vgic_initialized(kvm)) return 0;
/* Are we also in the middle of creating a VCPU? */ if (kvm->created_vcpus != atomic_read(&kvm->online_vcpus)) return -EBUSY;
/* freeze the number of spis */ if (!dist->nr_spis)
dist->nr_spis = VGIC_NR_IRQS_LEGACY - VGIC_NR_PRIVATE_IRQS;
ret = kvm_vgic_dist_init(kvm, dist->nr_spis); if (ret) goto out;
/* * Ensure vPEs are allocated if direct IRQ injection (e.g. vSGIs, * vLPIs) is supported.
*/ if (vgic_supports_direct_irqs(kvm)) {
ret = vgic_v4_init(kvm); if (ret) goto out;
}
if (vcpu->kvm->arch.vgic.vgic_model == KVM_DEV_TYPE_ARM_VGIC_V3) { /* * If this vCPU is being destroyed because of a failed creation * then unregister the redistributor to avoid leaving behind a * dangling pointer to the vCPU struct. * * vCPUs that have been successfully created (i.e. added to * kvm->vcpu_array) get unregistered in kvm_vgic_destroy(), as * this function gets called while holding kvm->arch.config_lock * in the VM teardown path and would otherwise introduce a lock * inversion w.r.t. kvm->srcu. * * vCPUs that failed creation are torn down outside of the * kvm->arch.config_lock and do not get unregistered in * kvm_vgic_destroy(), meaning it is both safe and necessary to * do so here.
*/ if (kvm_get_vcpu_by_id(vcpu->kvm, vcpu->vcpu_id) != vcpu)
vgic_unregister_redist_iodev(vcpu);
if (kvm->arch.vgic.vgic_model == KVM_DEV_TYPE_ARM_VGIC_V3)
kvm_for_each_vcpu(i, vcpu, kvm)
vgic_unregister_redist_iodev(vcpu);
mutex_unlock(&kvm->slots_lock);
}
/** * vgic_lazy_init: Lazy init is only allowed if the GIC exposed to the guest * is a GICv2. A GICv3 must be explicitly initialized by userspace using the * KVM_DEV_ARM_VGIC_GRP_CTRL KVM_DEVICE group. * @kvm: kvm struct pointer
*/ int vgic_lazy_init(struct kvm *kvm)
{ int ret = 0;
if (unlikely(!vgic_initialized(kvm))) { /* * We only provide the automatic initialization of the VGIC * for the legacy case of a GICv2. Any other type must * be explicitly initialized once setup with the respective * KVM device call.
*/ if (kvm->arch.vgic.vgic_model != KVM_DEV_TYPE_ARM_VGIC_V2) return -EBUSY;
mutex_lock(&kvm->arch.config_lock);
ret = vgic_init(kvm);
mutex_unlock(&kvm->arch.config_lock);
}
return ret;
}
/* RESOURCE MAPPING */
/** * kvm_vgic_map_resources - map the MMIO regions * @kvm: kvm struct pointer * * Map the MMIO regions depending on the VGIC model exposed to the guest * called on the first VCPU run. * Also map the virtual CPU interface into the VM. * v2 calls vgic_init() if not already done. * v3 and derivatives return an error if the VGIC is not initialized. * vgic_ready() returns true if this function has succeeded.
*/ int kvm_vgic_map_resources(struct kvm *kvm)
{ struct vgic_dist *dist = &kvm->arch.vgic; enum vgic_type type;
gpa_t dist_base; int ret = 0;
if (likely(vgic_ready(kvm))) return 0;
mutex_lock(&kvm->slots_lock);
mutex_lock(&kvm->arch.config_lock); if (vgic_ready(kvm)) goto out;
if (!irqchip_in_kernel(kvm)) goto out;
if (dist->vgic_model == KVM_DEV_TYPE_ARM_VGIC_V2) {
ret = vgic_v2_map_resources(kvm);
type = VGIC_V2;
} else {
ret = vgic_v3_map_resources(kvm);
type = VGIC_V3;
}
ret = vgic_register_dist_iodev(kvm, dist_base, type); if (ret) {
kvm_err("Unable to register VGIC dist MMIO regions\n"); goto out_slots;
}
/* * kvm_io_bus_register_dev() guarantees all readers see the new MMIO * registration before returning through synchronize_srcu(), which also * implies a full memory barrier. As such, marking the distributor as * 'ready' here is guaranteed to be ordered after all vCPUs having seen * a completely configured distributor.
*/
dist->ready = true; goto out_slots;
out:
mutex_unlock(&kvm->arch.config_lock);
out_slots: if (ret)
kvm_vm_dead(kvm);
/* * We cannot rely on the vgic maintenance interrupt to be * delivered synchronously. This means we can only use it to * exit the VM, and we perform the handling of EOIed * interrupts on the exit path (see vgic_fold_lr_state). * * Of course, NV throws a wrench in this plan, and needs * something special.
*/ if (vcpu && vgic_state_is_nested(vcpu))
vgic_v3_handle_nested_maint_irq(vcpu);
/** * kvm_vgic_init_cpu_hardware - initialize the GIC VE hardware * * For a specific CPU, initialize the GIC VE hardware.
*/ void kvm_vgic_init_cpu_hardware(void)
{
BUG_ON(preemptible());
/* * We want to make sure the list registers start out clear so that we * only have the program the used registers.
*/ if (kvm_vgic_global_state.type == VGIC_V2) {
vgic_v2_init_lrs();
} elseif (kvm_vgic_global_state.type == VGIC_V3 ||
kvm_vgic_global_state.has_gcie_v3_compat) {
kvm_call_hyp(__vgic_v3_init_lrs);
}
}
/** * kvm_vgic_hyp_init: populates the kvm_vgic_global_state variable * according to the host GIC model. Accordingly calls either * vgic_v2/v3_probe which registers the KVM_DEVICE that can be * instantiated by a guest later on .
*/ int kvm_vgic_hyp_init(void)
{ bool has_mask; int ret;
/* * If we get one of these oddball non-GICs, taint the kernel, * as we have no idea of how they *really* behave.
*/ if (gic_kvm_info->no_hw_deactivation) {
kvm_info("Non-architectural vgic, tainting kernel\n");
add_taint(TAINT_CPU_OUT_OF_SPEC, LOCKDEP_STILL_OK);
kvm_vgic_global_state.no_hw_deactivation = true;
}
switch (gic_kvm_info->type) { case GIC_V2:
ret = vgic_v2_probe(gic_kvm_info); break; case GIC_V3:
ret = vgic_v3_probe(gic_kvm_info); if (!ret) {
static_branch_enable(&kvm_vgic_global_state.gicv3_cpuif);
kvm_info("GIC system register CPU interface enabled\n");
} break; case GIC_V5:
ret = vgic_v5_probe(gic_kvm_info); break; default:
ret = -ENODEV;
}
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.