From mboxrd@z Thu Jan 1 00:00:00 1970 From: sandeep Subject: Re: EDE - Personal Suggestions and Ideas Date: Thu, 27 May 2004 11:37:42 +0530 Sender: linux-8086-owner@vger.kernel.org Message-ID: <40B585AE.101@codito.com> 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> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <40B52614.10908@cowlark.com> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Cc: linux-8086@vger.kernel.org hi, may be i don't quite understand ELKS much being a newbie here, but what's complex issue in having multiple segments on elks-8086? let's assume well behaved program running on elks, that has 4 different segments in use (CS, DS, ES, SS) and all the accesses made by it are wrt segment registers. when this program is taken off, it's all the segment registers are also saved in context info. apart from this elks kernel also keeps track of the extent of these segments used, so that moving segments around in the memory is convenient. next time when the program is brought in, whereever it's corresponding segments have been placed in memory, segment registers are appropriately set and control is passed back to the program via an iret call. of course some information manipulation is required for implementation of this. but we get the flexibility to move the segments around. -- regards sandeep -------------------------------------------------------------------------- Loose bits sink chips. --------------------------------------------------------------------------