From owner-freebsd-current Wed Dec 2 16:52:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00626 for freebsd-current-outgoing; Wed, 2 Dec 1998 16:52:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00618 for ; Wed, 2 Dec 1998 16:52:48 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id LAA03177; Thu, 3 Dec 1998 11:52:22 +1100 (EST) Message-ID: <19981203115222.A3051@rf900.physics.usyd.edu.au> Date: Thu, 3 Dec 1998 11:52:22 +1100 From: David Dawes To: Peter Jeremy , mike@smith.net.au Cc: current@FreeBSD.ORG Subject: Re: sio breakage References: <98Dec2.204608est.40351@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <98Dec2.204608est.40351@border.alcanet.com.au>; from Peter Jeremy on Wed, Dec 02, 1998 at 08:46:45PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 02, 1998 at 08:46:45PM +1100, Peter Jeremy wrote: >>> I don't believe this is reasonable. We should provide some safe way >>> for an application program to execute code with interrupts disabled. >>> Amongst other applications, XFree86 needs this. >> >>It shouldn't (ideally). >I agree. And whilst I haven't checked why, XFree86 does appear to >disable interrupts at times. I agree too, but it does disable interrupts when probing for fixed pixel clocks (which is mostly only done for obsolete hardware), and sometimes when programming PLLs. If someone has a better way of handling time critical thing like this (preferably in a portable way), please let me know. I'd love to dump our disable interrupt code. >> If it does, this is clearly indicative of a >>need to move some of the server code into the kernel, >You mean, like GGI :-). There are some tasks that are much better suited to the kernel, and perhaps a better balance could be found by just doing those few selected things in the kernel and leaving the rest of it in user space. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message