From owner-freebsd-hackers Wed Nov 18 20:35:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06226 for freebsd-hackers-outgoing; Wed, 18 Nov 1998 20:35:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from detlev.UUCP (tex-114.camalott.com [208.229.74.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06196 for ; Wed, 18 Nov 1998 20:35:21 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA03217; Wed, 18 Nov 1998 22:34:26 -0600 (CST) (envelope-from joelh) To: Matthew Dillon Cc: Marius Bendiksen , Terry Lambert , rnordier@nordier.com, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model References: <199811171806.LAA03809@usr09.primenet.com> <3.0.5.32.19981118121341.00975ac0@mail.scancall.no> <199811181842.KAA06180@apollo.backplane.com> From: Joel Ray Holveck Date: 18 Nov 1998 22:34:20 -0600 In-Reply-To: Matthew Dillon's message of "Wed, 18 Nov 1998 10:42:50 -0800 (PST)" Message-ID: <86ogq4gv1v.fsf@detlev.UUCP> Lines: 21 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> FreeBSD (and virtually all other operating systems) uses a >> two-layer design, not a multi-layer ring design. About the only >> thing you might see different between OS's is that some processors >> have a separate 'interrupt stack'. On Intel cpu's, however, the >> abstraction is useless due to the completely broken ring design >> because many supervisor instructions only work in ring 0. ring 1 >> and ring 2 are almost completely useless. So they're useless (for our purposes); I don't see why that makes their ring design broken. Could you please explain a bit more? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message