From owner-freebsd-java Wed Mar 20 16:13: 3 2002 Delivered-To: freebsd-java@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 8596037B404 for ; Wed, 20 Mar 2002 16:12:59 -0800 (PST) Received: from caddis.yogotech.com (caddis.yogotech.com [206.127.123.130]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id RAA04800; Wed, 20 Mar 2002 17:12:50 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g2L0Cne02159; Wed, 20 Mar 2002 17:12:49 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15513.9601.805260.607979@caddis.yogotech.com> Date: Wed, 20 Mar 2002 17:12:49 -0700 To: Bill Huey Cc: Nate Williams , Richard Tobin , java@FreeBSD.ORG Subject: Re: Mozilla core... & HotSpot update In-Reply-To: <20020321000145.GA4319@gnuppy.monkey.org> References: <200203201509.PAA29782@sorley.cogsci.ed.ac.uk> <20020320201858.GA3125@gnuppy.monkey.org> <15512.61557.26582.852492@caddis.yogotech.com> <20020320233301.GA4011@gnuppy.monkey.org> <15513.7648.287464.414451@caddis.yogotech.com> <20020321000145.GA4319@gnuppy.monkey.org> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > > It's kind of funny way of dealing with EINTRs and I suspect that they did > > > that to avoid dealing with syscall return value specifics. I'm not sure > > > how valid that is for FreeBSD. I wonder if I can do something else to get > > > around using this rather hackish macro and if the return valids of those > > > functions would be sufficient for reporting interrupts thrown by a Unix > > > signal. That's currently under examination. > > > > It seems to me that it's not even necessary, since syscalls can't be > > interrupted, you have nothing to handle. Unless I'm misunderstanding > > what you're saying. > > Right, the BSD behavior prevents this, which might be a problem for > implementing interruptable IO. The Linux code just omits that stuff > completely. Then we can as well. (Although, it might make things interesting for the new nsio stuff in 1.4). > > > The basic thing here is to handle the delivery of a SIGUSR1 to a > > > thread in a syscall > > > > See above. You can't interrupt an IO syscall in BSDs. However, that > > may change in 5.0, but that's a ways off, so it may end up being a 6.0 > > feature. > > I know. I'm wonder if I should mess with this at all right now. You > definitely gave me some clarity on this issue. Ok, here's some more clarity. Don't even mess with this at all right now. :) :) > > How about making diffs available for folks to review? > > I might as well commit it if that's the case. If there are that much of a mess, then diffs might be easier. However, if you get hit by a truck or find some chickie-poo who drags you away from your computer for long stretches of time, we'd like to have access to your bits, if not your brain. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message