From owner-freebsd-current Fri May 15 17:04:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00128 for freebsd-current-outgoing; Fri, 15 May 1998 17:04:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29924; Fri, 15 May 1998 17:03:59 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id TAA17395; Fri, 15 May 1998 19:03:52 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805160003.TAA17395@dyson.iquest.net> Subject: Re: People having problems with X windows? In-Reply-To: <19980516092352.17035@rf900.physics.usyd.edu.au> from David Dawes at "May 16, 98 09:23:52 am" To: dawes@rf900.physics.usyd.edu.au (David Dawes) Date: Fri, 15 May 1998 19:03:52 -0500 (EST) Cc: dyson@FreeBSD.ORG, sos@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The 771 uses the 968, and falls into the second category. To be safe, > memory not marked as prefetchable can only have WC enabled with both > knowledge of the hardware and knowledge of how the application is using > the memory. Having a way of letting the X server indicate this is > probably the best solution. > It seems that I'll need to supply a system call or ioctl or something that will allow for reconfig of the CPU registers. The new P6 processors allow for easier control, but with the P6 and earlier PII processors, I'll have to do an IPI. I'll put this on my list (and am willing to accept ideas from other OSen that you support, to help minimize support issues for you.) Madvise doesn't seem to be quite "right", but I am willing to support it with that system call, if you think that it is best. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message