From owner-freebsd-hackers Wed Oct 21 07:57:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27983 for freebsd-hackers-outgoing; Wed, 21 Oct 1998 07:57:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27978 for ; Wed, 21 Oct 1998 07:57:35 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id HAA10975; Wed, 21 Oct 1998 07:55:22 -0700 (PDT) (envelope-from jdp) Message-Id: <199810211455.HAA10975@austin.polstra.com> To: luigi@labinfo.iet.unipi.it Subject: Re: Handling page faults in user space ? In-Reply-To: <199810210744.IAA09732@labinfo.iet.unipi.it> References: <199810210744.IAA09732@labinfo.iet.unipi.it> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Wed, 21 Oct 1998 07:55:22 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199810210744.IAA09732@labinfo.iet.unipi.it>, Luigi Rizzo wrote: > i was wondering how to handle page faults/segment violations in user > space. Looking at mmap, signal and friends it looks like it is almost > possible. Others have answered your question about how to do it. I'll just confirm that it really does work. The Modula-3 runtime system relies on it to support the incremental garbage collector. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message