Adrian Danis b40d95ed89 x86: Send explicit TCB when handling remote VMs withs pending notifications ... Previously if the `ksCurThread` of the destination core is not the thread that is receiving the notification in `sendSignal` then the notification would be delayed until the VMM for that VM next did a `seL4_VMEnter`. This adds a `tcb_t*` parameter to `VMCheckBoundNotification` instead of having it implicitly talk about `ksCurThread`. A TCB parameter is safe to send here as the `doRemoteVMCheckBoundNotification` happens synchronously and so the TCB is guaranteed to still exist.		2017-02-06 15:04:43 +11:00
..
arm	Unify arch_shared_types.bf from the libsel	2017-02-06 09:08:35 +11:00
x86/arch	x86: Send explicit TCB when handling remote VMs withs pending notifications	2017-02-06 15:04:43 +11:00