This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [Qemu-devel] [PATCH 01/13] Handle terminating signal

To: Julian Seward <jseward@xxxxxxx>
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 01/13] Handle terminating signals.
From: Avi Kivity <avi@xxxxxxxxxxxx>
Date: Wed, 27 Aug 2008 11:05:08 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, qemu-devel@xxxxxxxxxx, Gerd Hoffmann <kraxel@xxxxxxxxxx>
Delivery-date: Wed, 27 Aug 2008 01:05:32 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200808261814.57044.jseward@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1219336054-15919-1-git-send-email-kraxel@xxxxxxxxxx> <18612.9061.534326.657959@xxxxxxxxxxxxxxxxxxxxxxxx> <48B42B57.2070301@xxxxxxxxxxxx> <200808261814.57044.jseward@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080723)
Julian Seward wrote:
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).

Most serious software has to be threaded. The absence of nonblocking libraries, the complexities of compositing nonblocking components when they do exist, and the requirement for utilizing multiple cores, all push towards threading.

I agree that it's incredibly easy to write badly threaded code. But I don't see a way to avoid it.

error compiling committee.c: too many arguments to function

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>