From owner-freebsd-hackers Sat Oct 30 7:24:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id 397B614E48 for ; Sat, 30 Oct 1999 07:24:30 -0700 (PDT) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id KAA00290; Sat, 30 Oct 1999 10:22:49 -0400 (EDT) (envelope-from cyouse@paradox.nexuslabs.com) Date: Sat, 30 Oct 1999 10:22:48 -0400 (EDT) From: Chuck Youse To: Oren Sarig Cc: hackers@FreeBSD.ORG Subject: Re: Limitations in FreeBSD In-Reply-To: <3.0.6.32.19991029210744.007da290@mail.bezeqint.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 Oct 1999, Oren Sarig wrote: > actual physical addresses, by using paging tables. Most of the addresses > are mapped outside of the actual memory, and so whenever somebody wants to > access them, a general protection fault occurs. The kernel taps the GPF, > gets the page from the swap, loads it into memory, remaps the linear > address, and gives the program back the control, but now the program has > the data in memory. IA32 supports up to 4Gb of physical memory with > protected mode, and a whole lot more virtual memory than that with paging. Well, just a minor technicality: when a non-present page is referenced, a page fault is generated, not a general protection fault. GPFs are the catch-all fault that is primarily used to flag security violations. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message