From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 5 01:57:11 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F74016A41F for ; Wed, 5 Oct 2005 01:57:11 +0000 (GMT) (envelope-from stephanie@sosdg.org) Received: from mail.sosdg.org (everest.sosdg.org [66.93.203.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id F32DE43D45 for ; Wed, 5 Oct 2005 01:57:10 +0000 (GMT) (envelope-from stephanie@sosdg.org) Received: from adsl-144-172-8.rmo.bellsouth.net ([70.144.172.8] helo=[192.168.0.199]) by mail.sosdg.org with esmtpa (Exim 4.51-SOSDG) id 1EMyWp-0003RN-Sp by authid ; Tue, 04 Oct 2005 20:57:08 -0500 Message-ID: <43433302.7050206@sosdg.org> Date: Tue, 04 Oct 2005 21:57:22 -0400 From: Stephanie Daugherty User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Wemm References: <200509292212.15953.stephanie@sosdg.org> <00ad01c5c564$fde0d960$0c64a8c0@opteron> <200510041722.50741.peter@wemm.org> In-Reply-To: <200510041722.50741.peter@wemm.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: softfail (everest.sosdg.org: transitioning domain of sosdg.org does not designate 70.144.172.8 as permitted sender) client-ip=70.144.172.8; envelope-from=stephanie@sosdg.org; helo=[192.168.0.199]; X-Scan-Signature: 7b1bcffb8e935917f4dd3178f61920aa X-SA-Exim-Connect-IP: 70.144.172.8 X-SA-Exim-Mail-From: stephanie@sosdg.org Cc: freebsd-amd64@freebsd.org Subject: Re: Wine on AMD64 - Any status or success stories? 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, 05 Oct 2005 01:57:11 -0000 Peter Wemm wrote: >On Thursday 29 September 2005 07:16 pm, K Anderson wrote: > > >>----- Original Message ----- >>From: "Stephanie Daugherty" >>To: >>Sent: Thursday, September 29, 2005 7:12 PM >>Subject: Wine on AMD64 - Any status or success stories? >> >> >> >>>I know this pops up a lot, but is anyone actively trying to fix Wine >>>under AMD64? I've googled through the list archives quickly and >>>haven't seen much >>>change in in over a year... >>> >>>Any progress? Any pointers on where to start or on what has to be >>>done to get >>>it working? What can be done to help? >>> >>> >>I'm not sure if it is the 64 bit version of Wine (WINE, or wine) but >>on my SuSe 9.2 system it works. I have only putzed around with it. >>The only application I am using it for at the moment is winamp. >> >>I really didn't have to config anything I think it did it for me, I >>may have had to tweak a few config files but that's about it. >> >>So that's my sucess. >> >> > >We don't have the required kernel infrastructure to make this work. > >There are two problems. 1) Getting the application to execute code in >32 bit mode. 2) managing the 16/32 bit windows segments. > >#2 is the big problem. We don't have the i386_set_ldt() infrastructure. >We might be able to get #1 working by having the process do a far jump >to the 32 bit code user segment selector in the GDT, but I haven't >messed with this yet. There are so many problems to deal with it isn't >funny, eg: delivering signals in 64 bit sigframe format on a stack of a >process that is currently executing in a 32 bit %cs segment. > >The problem set could probably be reduced by running 32 bit binaries, >but again, we can't do without the i386_set_ldt() infrastructure. I >was reminded about this again today while checking out a different >problem... I think its time to do something about this missing >feature. > > > Its possible that I'm not reading or understanding this right, but would it help at all to remove the compatability with 16bit apps? I think this is something that WinXP-64 did... Obviously you'd still have to work on some things, but would it then be within reach to make it work under COMPAT_IA32 ?