xen/arm: traps: Update the correct PC when inject a virtual SError to the guest

When injecting a virtual Abort to the guest, we want to update the guest
PC so it can re-execute the HVC/SMC once it has handled the SError.

This is unfortunately not the case when the SError is synchronized on
entry from the guest. As the SError will be received while running in
hypervisor context, we will update the PC of hypervisor context (i.e
the trap).

Rework inject_vabt_exception so it uses the guest context rather than
the current one.

Signed-off-by: Julien Grall <julien.grall@arm.com>
Acked-by: Stefano Stabellini <sstabellini@kernel.org>
Release-acked-by: Juergen Gross <jgross@suse.com>
This commit is contained in:
Julien Grall committed 2019-11-01 13:57:26 +00:00
1 parent dfdb006636
commit 0ae24912ac
1 file changed
+11 -4
+11 -4
View File
@@ -629,11 +629,18 @@ static void inject_dabt_exception(struct cpu_user_regs *regs,
#endif
}
/* Inject a virtual Abort/SError into the guest. */
static void inject_vabt_exception(struct cpu_user_regs *regs)
/*
* Inject a virtual Abort/SError into the guest.
*
* This should only be called with 'current'.
*/
static void inject_vabt_exception(struct vcpu *v)
{
struct cpu_user_regs *regs = guest_cpu_user_regs();
const union hsr hsr = { .bits = regs->hsr };
ASSERT(v == current);
/*
* SVC/HVC/SMC already have an adjusted PC (See ARM ARM DDI 0487A.j
* D1.10.1 for more details), which we need to correct in order to
@@ -656,7 +663,7 @@ static void inject_vabt_exception(struct cpu_user_regs *regs)
break;
}
vcpu_hcr_set_flags(current, HCR_VA);
vcpu_hcr_set_flags(v, HCR_VA);
}
/*
@@ -683,7 +690,7 @@ static void __do_trap_serror(struct cpu_user_regs *regs, bool guest)
* forwarded to the currently running vCPU.
*/
if ( serrors_op == SERRORS_DIVERSE && guest )
return inject_vabt_exception(regs);
return inject_vabt_exception(current);
do_unexpected_trap("SError", regs);
}
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.