Searched hist:"7 c4199375ae347449fbde43cc8bf174ae6383d8e" (Results 1 – 8 of 8) sorted by relevance
| /openbmc/linux/arch/arm64/kvm/hyp/nvhe/ |
| H A D | hyp-smp.c | diff 7c4199375ae347449fbde43cc8bf174ae6383d8e Mon Mar 22 08:32:34 CDT 2021 Marc Zyngier <maz@kernel.org> 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>
|
| H A D | mem_protect.c | diff 7c4199375ae347449fbde43cc8bf174ae6383d8e Mon Mar 22 08:32:34 CDT 2021 Marc Zyngier <maz@kernel.org> 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>
|
| /openbmc/linux/arch/arm64/include/asm/ |
| H A D | kvm_hyp.h | diff 7c4199375ae347449fbde43cc8bf174ae6383d8e Mon Mar 22 08:32:34 CDT 2021 Marc Zyngier <maz@kernel.org> 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>
|
| H A D | cpufeature.h | diff 7c4199375ae347449fbde43cc8bf174ae6383d8e Mon Mar 22 08:32:34 CDT 2021 Marc Zyngier <maz@kernel.org> 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>
|
| H A D | kvm_host.h | diff 7c4199375ae347449fbde43cc8bf174ae6383d8e Mon Mar 22 08:32:34 CDT 2021 Marc Zyngier <maz@kernel.org> 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>
|
| /openbmc/linux/arch/arm64/kvm/ |
| H A D | arm.c | diff 7c4199375ae347449fbde43cc8bf174ae6383d8e Mon Mar 22 08:32:34 CDT 2021 Marc Zyngier <maz@kernel.org> 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>
|
| H A D | sys_regs.c | diff 7c4199375ae347449fbde43cc8bf174ae6383d8e Mon Mar 22 08:32:34 CDT 2021 Marc Zyngier <maz@kernel.org> 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>
|
| /openbmc/linux/arch/arm64/kernel/ |
| H A D | cpufeature.c | diff 7c4199375ae347449fbde43cc8bf174ae6383d8e Mon Mar 22 08:32:34 CDT 2021 Marc Zyngier <maz@kernel.org> 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>
|