diff options
| author |   Marc Zyngier <maz@kernel.org> | 2019-10-27 14:41:59 +0000 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2019-10-28 16:20:58 +0000 |
| commit | 8e01d9a396e6db153d94a6004e6473d9ff251a6a (patch) | |
| tree | a7b0bba9a91ac8544ee28ba101864f5a8486e87e /include/linux/irqchip | |
| parent | KVM: arm64: Don't set HCR_EL2.TVM when S2FWB is supported (diff) | |
| download | linux-dev-8e01d9a396e6db153d94a6004e6473d9ff251a6a.tar.xz linux-dev-8e01d9a396e6db153d94a6004e6473d9ff251a6a.zip | |
KVM: arm64: vgic-v4: Move the GICv4 residency flow to be driven by vcpu_load/put
When the VHE code was reworked, a lot of the vgic stuff was moved around,
but the GICv4 residency code did stay untouched, meaning that we come
in and out of residency on each flush/sync, which is obviously suboptimal.
To address this, let's move things around a bit:
- Residency entry (flush) moves to vcpu_load
- Residency exit (sync) moves to vcpu_put
- On blocking (entry to WFI), we "put"
- On unblocking (exit from WFI), we "load"
Because these can nest (load/block/put/load/unblock/put, for example),
we now have per-VPE tracking of the residency state.
Additionally, vgic_v4_put gains a "need doorbell" parameter, which only
gets set to true when blocking because of a WFI. This allows a finer
control of the doorbell, which now also gets disabled as soon as
it gets signaled.
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20191027144234.8395-2-maz@kernel.org
Diffstat (limited to 'include/linux/irqchip')
| -rw-r--r-- | include/linux/irqchip/arm-gic-v4.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/include/linux/irqchip/arm-gic-v4.h b/include/linux/irqchip/arm-gic-v4.h index e6b155713b47..ab1396afe08a 100644 --- a/include/linux/irqchip/arm-gic-v4.h +++ b/include/linux/irqchip/arm-gic-v4.h @@ -35,6 +35,8 @@ struct its_vpe { /* Doorbell interrupt */ int irq; irq_hw_number_t vpe_db_lpi; + /* VPE resident */ + bool resident; /* VPE proxy mapping */ int vpe_proxy_event; /* |