From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KYH39-00029E-1o for qemu-devel@nongnu.org; Wed, 27 Aug 2008 05:10:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KYH36-00028i-Ni for qemu-devel@nongnu.org; Wed, 27 Aug 2008 05:10:45 -0400 Received: from [199.232.76.173] (port=39979 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KYH36-00028Z-CZ for qemu-devel@nongnu.org; Wed, 27 Aug 2008 05:10:44 -0400 Received: from il.qumranet.com ([212.179.150.194]:18949) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KYH35-0002QT-WE for qemu-devel@nongnu.org; Wed, 27 Aug 2008 05:10:44 -0400 Message-ID: <48B51A12.3040101@qumranet.com> Date: Wed, 27 Aug 2008 12:10:42 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 01/13] Handle terminating signals. References: <1219336054-15919-1-git-send-email-kraxel@redhat.com> <18612.9061.534326.657959@mariner.uk.xensource.com> <48B42B57.2070301@qumranet.com> <200808261814.57044.jseward@acm.org> <48B50AB4.7030806@qumranet.com> <20080827094935.3ff45e1f@lxorguk.ukuu.org.uk> In-Reply-To: <20080827094935.3ff45e1f@lxorguk.ukuu.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alan Cox Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org, Gerd Hoffmann Alan Cox wrote: >> I agree that it's incredibly easy to write badly threaded code. But I >> don't see a way to avoid it. >> > > Message passing, using the right language tools (in C that unfortunately > means writing your own or going back to 60s textbooks) > Oh, if we're talking languages, then I'm all for pure functional languages. If you are side effects free, you can let the runtime do all the threading for you automatically. I don't see that catching on though. -- error compiling committee.c: too many arguments to function From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Re: [Qemu-devel] [PATCH 01/13] Handle terminating signals. Date: Wed, 27 Aug 2008 12:10:42 +0300 Message-ID: <48B51A12.3040101@qumranet.com> References: <1219336054-15919-1-git-send-email-kraxel@redhat.com> <18612.9061.534326.657959@mariner.uk.xensource.com> <48B42B57.2070301@qumranet.com> <200808261814.57044.jseward@acm.org> <48B50AB4.7030806@qumranet.com> <20080827094935.3ff45e1f@lxorguk.ukuu.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080827094935.3ff45e1f@lxorguk.ukuu.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Alan Cox Cc: Julian Seward , xen-devel@lists.xensource.com, qemu-devel@nongnu.org, Gerd Hoffmann List-Id: xen-devel@lists.xenproject.org Alan Cox wrote: >> I agree that it's incredibly easy to write badly threaded code. But I >> don't see a way to avoid it. >> > > Message passing, using the right language tools (in C that unfortunately > means writing your own or going back to 60s textbooks) > Oh, if we're talking languages, then I'm all for pure functional languages. If you are side effects free, you can let the runtime do all the threading for you automatically. I don't see that catching on though. -- error compiling committee.c: too many arguments to function