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

[Avi Kivity <avi@xxxxxxxxxxxx>]

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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel