From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id 404C3BB9A for ; Fri, 28 Oct 2005 23:41:31 +0200 (CEST) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.205]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id j9SLfUbU013884 for ; Fri, 28 Oct 2005 23:41:30 +0200 Received: by xproxy.gmail.com with SMTP id s15so442500wxc for ; Fri, 28 Oct 2005 14:41:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oEIiZFrXJDsONhHadNja3p5kIwe98xBwSgF3OwJ/EyBVLCIURjLKTlJl/ZdI7bcSJYvymZLelDlVIw8jYmsKP1+l0NfmSXSAdKdbVUq9dRNy9FjrVi07jBE34ZqKT35HQ2/u1LY2jd8K2sP0XtTq1s853mgNKTktfbWLUnFNb/o= Received: by 10.64.210.20 with SMTP id i20mr442637qbg; Fri, 28 Oct 2005 14:41:30 -0700 (PDT) Received: by 10.65.23.20 with HTTP; Fri, 28 Oct 2005 14:41:30 -0700 (PDT) Message-ID: Date: Sat, 29 Oct 2005 10:41:30 +1300 From: Jonathan Roewen To: Damien Doligez Subject: Re: [Caml-list] The Bytecode Interpreter... Cc: caml-list@yquem.inria.fr In-Reply-To: <5636A978-D095-489D-A20D-8E762F133240@inria.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <5636A978-D095-489D-A20D-8E762F133240@inria.fr> X-Miltered: at nez-perce with ID 43629B0A.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; caml-list:01 bytecode:01 threads:01 ...:98 ...:98 descriptor:02 thread:02 triggered:05 interpreter:06 file:08 framework:09 somehow:10 question:11 i've:11 source:12 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=RCVD_BY_IP autolearn=disabled version=3.0.3 Hi, I have a question about the vmthreads package. I've been looking at the source of schedule.c, and am making a small understanding of how it works. Is it true that this supports true pre-emption of threads (e.g. even during a GC cycle)? Also, would it be safe to build an ISR framework that could wake up a thread waiting on an interrupt to be triggered? Like if I somehow got it to act like a file descriptor... Jonathan