From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265103AbUEYWnj (ORCPT ); Tue, 25 May 2004 18:43:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265115AbUEYWnj (ORCPT ); Tue, 25 May 2004 18:43:39 -0400 Received: from mx1.redhat.com ([66.187.233.31]:8863 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S265103AbUEYWni (ORCPT ); Tue, 25 May 2004 18:43:38 -0400 Date: Tue, 25 May 2004 18:43:09 -0400 From: Alan Cox To: Albert Cahalan Cc: linux-kernel mailing list , alan@redhat.com, willy@w.ods.org, hch@lst.de, macro@ds2.pg.gda.pl Subject: Re: i486 emu in mainline? Message-ID: <20040525224309.GA6612@devserv.devel.redhat.com> References: <1085504583.955.1015.camel@cube> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1085504583.955.1015.camel@cube> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 25, 2004 at 01:03:04PM -0400, Albert Cahalan wrote: > The important thing is to correctly handle whatever is > generated by gcc, icc, glibc, uclibc, dietlibc, klibc, > and newlib. Thus you can assume that you're dealing with > a 32-bit app that doesn't play LDT games. Segment selectors > are limited to the pthreads assembly code. The LDT stuff isnt that hard to deal with, you can probably ignore the 16bit code segment funky stuff, but you'd need to parse things like size prefixes.