From: Andreas Sandberg Date: Thu, 20 Jul 2017 16:32:10 +0000 (+0000) Subject: cpu, kvm: Fix deadlock issue when resuming a drained system X-Git-Tag: v19.0.0.0~2665 X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=9d6d3e5f7dd50e882a503ee4bb2ac7d9b8d21e30;p=gem5.git cpu, kvm: Fix deadlock issue when resuming a drained system The KVM CPU sometimes needs to access devices when drain() is called. This typically happens on ARM when synchronizing devices that use the system register interface. When called from drain(), the event queue isn't locked since drain is called from the outside when the simulator isn't servicing any events. In such cases, performing a migration to the device's queue will unlock a mutex that isn't locked. This typically results in a deadlock when resuming the system since the lock will be in an undefined state. Change-Id: Ibdcc2e034e916a929124f297e72aae306cf66728 Signed-off-by: Andreas Sandberg Reviewed-by: Nikos Nikoleris Reviewed-by: Curtis Dunham Reviewed-on: https://gem5-review.googlesource.com/4286 Reviewed-by: Jason Lowe-Power --- diff --git a/src/cpu/kvm/base.cc b/src/cpu/kvm/base.cc index 250c6a270..6ea99ce4a 100644 --- a/src/cpu/kvm/base.cc +++ b/src/cpu/kvm/base.cc @@ -358,6 +358,13 @@ BaseKvmCPU::drain() return DrainState::Drained; DPRINTF(Drain, "BaseKvmCPU::drain\n"); + + // The event queue won't be locked when calling drain since that's + // not done from an event. Lock the event queue here to make sure + // that scoped migrations continue to work if we need to + // synchronize the thread context. + std::lock_guard lock(*this->eventQueue()); + switch (_status) { case Running: // The base KVM code is normally ready when it is in the