From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54213) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f8ivL-0005IX-DO for qemu-devel@nongnu.org; Wed, 18 Apr 2018 04:58:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f8ivI-0003sE-Br for qemu-devel@nongnu.org; Wed, 18 Apr 2018 04:58:43 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:49340 helo=mx1.redhat.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1f8ivI-0003rq-8b for qemu-devel@nongnu.org; Wed, 18 Apr 2018 04:58:40 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 9B1CB81A88B4 for ; Wed, 18 Apr 2018 08:58:39 +0000 (UTC) From: Peter Xu Date: Wed, 18 Apr 2018 16:58:28 +0800 Message-Id: <20180418085831.12058-1-peterx@redhat.com> Subject: [Qemu-devel] [PATCH 0/3] monitor: let Monitor be thread safe List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: peterx@redhat.com Stefan reported this problem that in the future we might start to have more threads operating on the same Monitor object. This seris try to add fundamental support for it. Patch 1 renames the old out_lock to mon_lock, so that it can cover more things. Patch 2 uses the mon_lock to protect Monitor object, at least all the APIs exported in monitor.h Patch 3 introduces mon_fdsets_lock to protect mon_fdsets global. Tests: x86 only, make check, raw iotests, windows build. Please review. Thanks, Peter Xu (3): monitor: rename out_lock to mon_lock monitor: take mon_lock where proper monitor: add lock to protect mon_fdsets monitor.c | 120 +++++++++++++++++++++++++++++++++++++++++++++----------------- 1 file changed, 87 insertions(+), 33 deletions(-) -- 2.14.3