// SPDX-License-Identifier: GPL-2.0-only /* * Copyright (C) 2016,2017 ARM Limited, All Rights Reserved. * Author: Marc Zyngier <marc.zyngier@arm.com>
*/
/* * WARNING: The blurb below assumes that you understand the * intricacies of GICv3, GICv4, and how a guest's view of a GICv3 gets * translated into GICv4 commands. So it effectively targets at most * two individuals. You know who you are. * * The core GICv4 code is designed to *avoid* exposing too much of the * core GIC code (that would in turn leak into the hypervisor code), * and instead provide a hypervisor agnostic interface to the HW (of * course, the astute reader will quickly realize that hypervisor * agnostic actually means KVM-specific - what were you thinking?). * * In order to achieve a modicum of isolation, we try to hide most of * the GICv4 "stuff" behind normal irqchip operations: * * - Any guest-visible VLPI is backed by a Linux interrupt (and a * physical LPI which gets unmapped when the guest maps the * VLPI). This allows the same DevID/EventID pair to be either * mapped to the LPI (host) or the VLPI (guest). Note that this is * exclusive, and you cannot have both. * * - Enabling/disabling a VLPI is done by issuing mask/unmask calls. * * - Guest INT/CLEAR commands are implemented through * irq_set_irqchip_state(). * * - The *bizarre* stuff (mapping/unmapping an interrupt to a VLPI, or * issuing an INV after changing a priority) gets shoved into the * irq_set_vcpu_affinity() method. While this is quite horrible * (let's face it, this is the irqchip version of an ioctl), it * confines the crap to a single location. And map/unmap really is * about setting the affinity of a VLPI to a vcpu, so only INV is * majorly out of place. So there. * * A number of commands are simply not provided by this interface, as * they do not make direct sense. For example, MAPD is purely local to * the virtual ITS (because it references a virtual device, and the * physical ITS is still very much in charge of the physical * device). Same goes for things like MAPC (the physical ITS deals * with the actual vPE affinity, and not the braindead concept of * collection). SYNC is not provided either, as each and every command * is followed by a VSYNC. This could be relaxed in the future, should * this be seen as a bottleneck (yes, this means *never*). * * But handling VLPIs is only one side of the job of the GICv4 * code. The other (darker) side is to take care of the doorbell * interrupts which are delivered when a VLPI targeting a non-running * vcpu is being made pending. * * The choice made here is that each vcpu (VPE in old northern GICv4 * dialect) gets a single doorbell LPI, no matter how many interrupts * are targeting it. This has a nice property, which is that the * interrupt becomes a handle for the VPE, and that the hypervisor * code can manipulate it through the normal interrupt API: * * - VMs (or rather the VM abstraction that matters to the GIC) * contain an irq domain where each interrupt maps to a VPE. In * turn, this domain sits on top of the normal LPI allocator, and a * specially crafted irq_chip implementation. * * - mask/unmask do what is expected on the doorbell interrupt. * * - irq_set_affinity is used to move a VPE from one redistributor to * another. * * - irq_set_vcpu_affinity once again gets hijacked for the purpose of * creating a new sub-API, namely scheduling/descheduling a VPE * (which involves programming GICR_V{PROP,PEND}BASER) and * performing INVALL operations.
*/
int its_make_vpe_non_resident(struct its_vpe *vpe, bool db)
{ struct irq_desc *desc = irq_to_desc(vpe->irq); struct its_cmd_info info = { }; int ret;
WARN_ON(preemptible());
info.cmd_type = DESCHEDULE_VPE; if (has_v4_1()) { /* GICv4.1 can directly deal with doorbells */
info.req_db = db;
} else { /* Undo the nested disable_irq() calls... */ while (db && irqd_irq_disabled(&desc->irq_data))
enable_irq(vpe->irq);
}
ret = its_send_vpe_cmd(vpe, &info); if (!ret)
vpe->resident = false;
vpe->ready = false;
return ret;
}
int its_make_vpe_resident(struct its_vpe *vpe, bool g0en, bool g1en)
{ struct its_cmd_info info = { }; int ret;
WARN_ON(preemptible());
info.cmd_type = SCHEDULE_VPE; if (has_v4_1()) {
info.g0en = g0en;
info.g1en = g1en;
} else { /* Disabled the doorbell, as we're about to enter the guest */
disable_irq_nosync(vpe->irq);
}
ret = its_send_vpe_cmd(vpe, &info); if (!ret)
vpe->resident = true;
return ret;
}
int its_commit_vpe(struct its_vpe *vpe)
{ struct its_cmd_info info = {
.cmd_type = COMMIT_VPE,
}; int ret;
WARN_ON(preemptible());
ret = its_send_vpe_cmd(vpe, &info); if (!ret)
vpe->ready = true;
return ret;
}
int its_invall_vpe(struct its_vpe *vpe)
{ struct its_cmd_info info = {
.cmd_type = INVALL_VPE,
};
return its_send_vpe_cmd(vpe, &info);
}
int its_map_vlpi(int irq, struct its_vlpi_map *map)
{ struct its_cmd_info info = {
.cmd_type = MAP_VLPI,
{
.map = map,
},
}; int ret;
/* * The host will never see that interrupt firing again, so it * is vital that we don't do any lazy masking.
*/
irq_set_status_flags(irq, IRQ_DISABLE_UNLAZY);
ret = irq_set_vcpu_affinity(irq, &info); if (ret)
irq_clear_status_flags(irq, IRQ_DISABLE_UNLAZY);
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.