diff options
author | Christoffer Dall <christoffer.dall@linaro.org> | 2017-12-23 21:53:48 +0100 |
---|---|---|
committer | Marc Zyngier <marc.zyngier@arm.com> | 2018-03-19 10:53:17 +0000 |
commit | d47533dab9f50eeb7289a38035c39c9eadb1e048 (patch) | |
tree | 951f327c633328c72877d7bd6be8a53d5cd349f8 /virt/kvm | |
parent | 8d404c4c246137531f94dfee352f350d59d0e5a7 (diff) | |
download | linux-d47533dab9f50eeb7289a38035c39c9eadb1e048.tar.gz linux-d47533dab9f50eeb7289a38035c39c9eadb1e048.tar.bz2 linux-d47533dab9f50eeb7289a38035c39c9eadb1e048.zip |
KVM: arm64: Introduce framework for accessing deferred sysregs
We are about to defer saving and restoring some groups of system
registers to vcpu_put and vcpu_load on supported systems. This means
that we need some infrastructure to access system registes which
supports either accessing the memory backing of the register or directly
accessing the system registers, depending on the state of the system
when we access the register.
We do this by defining read/write accessor functions, which can handle
both "immediate" and "deferrable" system registers. Immediate registers
are always saved/restored in the world-switch path, but deferrable
registers are only saved/restored in vcpu_put/vcpu_load when supported
and sysregs_loaded_on_cpu will be set in that case.
Note that we don't use the deferred mechanism yet in this patch, but only
introduce infrastructure. This is to improve convenience of review in
the subsequent patches where it is clear which registers become
deferred.
Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
Reviewed-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions