Searched hist:"7 db21530479f071ee0e0a4d5fcf5e6bc6c0352ba" (Results 1 – 5 of 5) sorted by relevance
/openbmc/linux/arch/arm64/kvm/hyp/nvhe/ |
H A D | host.S | diff 7db21530479f071ee0e0a4d5fcf5e6bc6c0352ba Tue Sep 15 05:46:34 CDT 2020 Andrew Scull <ascull@google.com> KVM: arm64: Restore hyp when panicking in guest context
If the guest context is loaded when a panic is triggered, restore the hyp context so e.g. the shadow call stack works when hyp_panic() is called and SP_EL0 is valid when the host's panic() is called.
Use the hyp context's __hyp_running_vcpu field to track when hyp transitions to and from the guest vcpu so the exception handlers know whether the context needs to be restored.
Signed-off-by: Andrew Scull <ascull@google.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20200915104643.2543892-11-ascull@google.com
|
/openbmc/linux/arch/arm64/kvm/hyp/ |
H A D | entry.S | diff 7db21530479f071ee0e0a4d5fcf5e6bc6c0352ba Tue Sep 15 05:46:34 CDT 2020 Andrew Scull <ascull@google.com> KVM: arm64: Restore hyp when panicking in guest context
If the guest context is loaded when a panic is triggered, restore the hyp context so e.g. the shadow call stack works when hyp_panic() is called and SP_EL0 is valid when the host's panic() is called.
Use the hyp context's __hyp_running_vcpu field to track when hyp transitions to and from the guest vcpu so the exception handlers know whether the context needs to be restored.
Signed-off-by: Andrew Scull <ascull@google.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20200915104643.2543892-11-ascull@google.com
|
H A D | hyp-entry.S | diff 7db21530479f071ee0e0a4d5fcf5e6bc6c0352ba Tue Sep 15 05:46:34 CDT 2020 Andrew Scull <ascull@google.com> KVM: arm64: Restore hyp when panicking in guest context
If the guest context is loaded when a panic is triggered, restore the hyp context so e.g. the shadow call stack works when hyp_panic() is called and SP_EL0 is valid when the host's panic() is called.
Use the hyp context's __hyp_running_vcpu field to track when hyp transitions to and from the guest vcpu so the exception handlers know whether the context needs to be restored.
Signed-off-by: Andrew Scull <ascull@google.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20200915104643.2543892-11-ascull@google.com
|
/openbmc/linux/arch/arm64/kvm/hyp/include/hyp/ |
H A D | switch.h | diff 7db21530479f071ee0e0a4d5fcf5e6bc6c0352ba Tue Sep 15 05:46:34 CDT 2020 Andrew Scull <ascull@google.com> KVM: arm64: Restore hyp when panicking in guest context
If the guest context is loaded when a panic is triggered, restore the hyp context so e.g. the shadow call stack works when hyp_panic() is called and SP_EL0 is valid when the host's panic() is called.
Use the hyp context's __hyp_running_vcpu field to track when hyp transitions to and from the guest vcpu so the exception handlers know whether the context needs to be restored.
Signed-off-by: Andrew Scull <ascull@google.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20200915104643.2543892-11-ascull@google.com
|
/openbmc/linux/arch/arm64/include/asm/ |
H A D | kvm_asm.h | diff 7db21530479f071ee0e0a4d5fcf5e6bc6c0352ba Tue Sep 15 05:46:34 CDT 2020 Andrew Scull <ascull@google.com> KVM: arm64: Restore hyp when panicking in guest context
If the guest context is loaded when a panic is triggered, restore the hyp context so e.g. the shadow call stack works when hyp_panic() is called and SP_EL0 is valid when the host's panic() is called.
Use the hyp context's __hyp_running_vcpu field to track when hyp transitions to and from the guest vcpu so the exception handlers know whether the context needs to be restored.
Signed-off-by: Andrew Scull <ascull@google.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20200915104643.2543892-11-ascull@google.com
|