From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 27 18:45:27 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A466106566C for ; Wed, 27 Feb 2008 18:45:26 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by mx1.freebsd.org (Postfix) with ESMTP id 3B0498FC12 for ; Wed, 27 Feb 2008 18:45:26 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail13.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m1RIjNl9016880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Feb 2008 05:45:24 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m1RIjNWZ071612; Thu, 28 Feb 2008 05:45:23 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m1RIjNYN071611; Thu, 28 Feb 2008 05:45:23 +1100 (EST) (envelope-from peter) Date: Thu, 28 Feb 2008 05:45:23 +1100 From: Peter Jeremy To: Jeff Isaac Message-ID: <20080227184522.GE83599@server.vk2pj.dyndns.org> References: <443D814E-04F3-411C-9DF9-E799A39FAEB3@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1BdFSKqAqVdu8k/" Content-Disposition: inline In-Reply-To: <443D814E-04F3-411C-9DF9-E799A39FAEB3@gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-amd64@freebsd.org Subject: Re: "freebsd-amd64" X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 18:45:27 -0000 --k1BdFSKqAqVdu8k/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 27, 2008 at 07:34:48AM -0600, Jeff Isaac wrote: >doodle with, not BIOS), BUT, from a general knowledge perspective, what=20 >advantages does virtual 86 mode have over real mode? Essentially, why did= =20 >the FreeBSD project choose the virtual implementation? More portable?=20 >Easier to write? None of the above? Thanks! :) The kernel run in 32-bit protected mode. Switching between protected mode and real mode requires a reasonable degree of voodoo which does not currently exist in the kernel (the loader handles the initial real to protected transition and the kernel then never leaves protected mode). Plus you need to either ensure that exceptions/interrupts won't occur or handle them in real mode. OTOH, virtual86 mode is part of the hardware - you create a task descriptor and set the VM86 bit. Any exceptions etc are delivered to the kernel. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --k1BdFSKqAqVdu8k/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHxa/C/opHv/APuIcRAgUeAKCTVGSNOk0mTV6OpXPdRpkg8BOVqgCfcR3q SmeCq7J+0bGmjJ8EuWiITWg= =dowN -----END PGP SIGNATURE----- --k1BdFSKqAqVdu8k/--