Searched hist:b4f18c063a13dfb33e3a63fe1844823e19c2265e (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/arch/arm64/kvm/hyp/ |
| H A D | hyp-entry.S | diff b4f18c063a13dfb33e3a63fe1844823e19c2265e Tue May 29 07:11:17 CDT 2018 Marc Zyngier <marc.zyngier@arm.com> arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
In order to forward the guest's ARCH_WORKAROUND_2 calls to EL3,
add a small(-ish) sequence to handle it at EL2. Special care must
be taken to track the state of the guest itself by updating the
workaround flags. We also rely on patching to enable calls into
the firmware.
Note that since we need to execute branches, this always executes
after the Spectre-v2 mitigation has been applied.
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|
| /openbmc/linux/arch/arm64/kernel/ |
| H A D | asm-offsets.c | diff b4f18c063a13dfb33e3a63fe1844823e19c2265e Tue May 29 07:11:17 CDT 2018 Marc Zyngier <marc.zyngier@arm.com> arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests
In order to forward the guest's ARCH_WORKAROUND_2 calls to EL3,
add a small(-ish) sequence to handle it at EL2. Special care must
be taken to track the state of the guest itself by updating the
workaround flags. We also rely on patching to enable calls into
the firmware.
Note that since we need to execute branches, this always executes
after the Spectre-v2 mitigation has been applied.
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|