From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35138) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bZGr2-0002Iy-9v for qemu-devel@nongnu.org; Mon, 15 Aug 2016 08:18:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bZGr0-0006xO-D2 for qemu-devel@nongnu.org; Mon, 15 Aug 2016 08:18:55 -0400 Date: Mon, 15 Aug 2016 14:18:46 +0200 From: Kevin Wolf Message-ID: <20160815121846.GF6024@noname.str.redhat.com> References: <1470932542-12311-1-git-send-email-kwolf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1470932542-12311-1-git-send-email-kwolf@redhat.com> Subject: Re: [Qemu-devel] [PATCH 0/2] coroutine: Assertions and debugging aids List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-block@nongnu.org Cc: stefanha@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org Am 11.08.2016 um 18:22 hat Kevin Wolf geschrieben: > A while ago we were debugging a hang where coroutines were waiting for a mutex > to be unlocked, but we couldn't find out who held the lock. This series adds > some information to Coroutine and CoMutex that both allows to add a few > assertions to check locking behaviour and can be used to find the culprit when > analysing a core dump. Applied to block-next. Kevin