On 20/03/13 20:04, Christopher Covington wrote:
> Hi Marc,
>
> On 03/13/2013 03:59 PM, Christopher Covington wrote:
>
> [...]
>
>> Alternatively, you could consider storing the host registers in a
>> slimmed-down vcpu structure for hosts, rather than on the stack.
I am actively implementing thi
Hi Marc,
On 03/13/2013 03:59 PM, Christopher Covington wrote:
[...]
> Alternatively, you could consider storing the host registers in a
> slimmed-down vcpu structure for hosts, rather than on the stack.
One potential argument for storing the host in the same sort of vcpu structure
as the guest
Hi Marc,
I like how you were able to use a common fpsimd_(save|restore) macro, and
wonder if you can't do the same sort of thing for the general purpose
registers and system registers. In the end, both guest and host are EL1
software, and while they may differ in terms of things like VTTBR setting
The HYP mode world switch in all its glory.
Implements save/restore of host/guest registers, EL2 trapping,
IPA resolution, and additional services (tlb invalidation).
Signed-off-by: Marc Zyngier
---
arch/arm64/kernel/asm-offsets.c | 33 ++
arch/arm64/kvm/hyp.S| 756
