From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Pereira Habkost Subject: Re: EDE - Personal Suggestions and Ideas Date: Thu, 27 May 2004 12:51:28 -0300 Sender: linux-8086-owner@vger.kernel.org Message-ID: <20040527155128.GE21172@duckman.distro.conectiva> References: <20040526115733.GQ12951@vega.vega.lgb.hu> <200405261517.47059.dg@cowlark.com> <20040526151030.GC15905@vega.vega.lgb.hu> <200405261749.42017.dg@cowlark.com> <40B4D6F9.4070507@i.com.ua> <40B52614.10908@cowlark.com> <40B585AE.101@codito.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3XA6nns4nE4KvaS/" Return-path: Content-Disposition: inline In-Reply-To: <40B585AE.101@codito.com> List-Id: To: linux-8086@vger.kernel.org --3XA6nns4nE4KvaS/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 27, 2004 at 11:37:42AM +0530, sandeep wrote: > hi, > may be i don't quite understand ELKS much being a newbie here, but what's= =20 > complex issue in having multiple segments on elks-8086? >=20 > let's assume well behaved program running on elks, that has 4 different= =20 > segments in use (CS, DS, ES, SS) and all the accesses made by it are wrt= =20 > segment registers. >=20 > when this program is taken off, it's all the segment registers are also= =20 > saved in context info. apart from this elks kernel also keeps track of th= e=20 > extent of these segments used, so that moving segments around in the memo= ry=20 > is convenient. >=20 > next time when the program is brought in, whereever it's corresponding=20 > segments > have been placed in memory, segment registers are appropriately set and= =20 > control is passed back to the program via an iret call. >=20 > of course some information manipulation is required for implementation of= =20 > this. but we get the flexibility to move the segments around. >=20 You are right, but this is true only if you assume that the program don't try to mess with the segment registers by itself, or store in memory the values of the segment registers for using them later. That is what was being discussed. --=20 Eduardo --3XA6nns4nE4KvaS/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAtg6AcaRJ66w1lWgRAuIhAJwMdRfcO/hoWpXsWsxF0ioWHJEZewCdGHyR BZZImWpUiW8DJiruZA9YJ68= =Lusd -----END PGP SIGNATURE----- --3XA6nns4nE4KvaS/--