KVM: arm64: Drop the CPU_FTR_REG_HYP_COPY infrastructure
Now that the read_ctr macro has been specialised for nVHE, the whole CPU_FTR_REG_HYP_COPY infrastrcture looks completely overengineered. Simplify it by populating the two u64 quantities (MMFR0 and 1) that the hypervisor need. Reviewed-by:Quentin Perret <qperret@google.com> Signed-off-by:
Marc Zyngier <maz@kernel.org>
Loading
Please register or sign in to comment