From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KY1Lr-0005ws-Ad
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 12:25:03 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KY1Lq-0005wa-5b
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 12:25:02 -0400
Received: from [199.232.76.173] (port=45796 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KY1Lp-0005wV-Vh
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 12:25:02 -0400
Received: from server1linux.rebelnetworks.com ([66.135.44.167]:58798)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <jseward@acm.org>) id 1KY1Lp-0003k0-KG
	for qemu-devel@nongnu.org; Tue, 26 Aug 2008 12:25:01 -0400
From: Julian Seward <jseward@acm.org>
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 01/13] Handle terminating
	signals.
Date: Tue, 26 Aug 2008 18:14:56 +0200
References: <1219336054-15919-1-git-send-email-kraxel@redhat.com>
	<18612.9061.534326.657959@mariner.uk.xensource.com>
	<48B42B57.2070301@qumranet.com>
In-Reply-To: <48B42B57.2070301@qumranet.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200808261814.57044.jseward@acm.org>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: xen-devel@lists.xensource.com, Gerd Hoffmann <kraxel@redhat.com>


On Tuesday 26 August 2008, Avi Kivity wrote:

> Threading bugs in the implementation?  In 2008?
>
> Practically all serious software is multithreaded nowadays.

That's not in itself an argument in support of writing threaded code
if you don't have to.

I spent much of the last year developing thread-checking tools
in the Valgrind framework (Helgrind), and testing them on serious
software.  From that I would say that practically all serious
multithreaded software is riddled with threading bugs, mostly
data races and inconsistent lock orderings (potential deadlocks).

J