From owner-freebsd-emulation@FreeBSD.ORG Sat May 10 21:01:46 2008 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C595410656AA for ; Sat, 10 May 2008 21:01:46 +0000 (UTC) (envelope-from bsd@kuehlbox.de) Received: from samael.qmail-ldap.de (mail.kuehlbox.de [62.159.47.22]) by mx1.freebsd.org (Postfix) with ESMTP id 2D6768FC12 for ; Sat, 10 May 2008 21:01:45 +0000 (UTC) (envelope-from bsd@kuehlbox.de) Received: (qmail 59150 invoked from network); 10 May 2008 21:01:32 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlbox.de; b=vonNly46BRZOLGSL5zao4vZonPg6iRNVsSfK1lpIzsVWGyM57S6XsephK4RsyNNy17/ms94Biyd7IlN5zUK/r0SkaNbZ/1EINxpOd+V5oYWCv9Yl6ZY9uePIOu3xh29i ; Received: from unknown (HELO [192.168.200.128]) (bsd@kuehlbox.de@[10.0.48.22]) (envelope-sender ) by samael.qmail-ldap.de (qmail-ldap-1.03) with SMTP for ; 10 May 2008 21:01:32 -0000 Received: from: ppp-88-217-15-6.dynamic.mnet-online.de RECURED ([88.217.15.6]) by HSF smtp proxy with AES256-SHA encrypted SMTP Message-ID: <48260CF7.5050700@kuehlbox.de> Date: Sat, 10 May 2008 23:00:39 +0200 From: Teufel User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: freebsd-emulation@freebsd.org, Juergen Lock References: <20080507162713.73A3A5B47@mail.bitblocks.com> <20080508195843.G17500@delplex.bde.org> <20080509220922.GA13480@saturn.kn-bremen.de> In-Reply-To: <20080509220922.GA13480@saturn.kn-bremen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: seems I finally found what upset kqemu on amd64 SMP... shared gdt! (please test patch :) X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2008 21:01:46 -0000 > Okay I _think_ I know a little more about this now... kqemu itself > doesn't use the fpu, but the guest code it runs can, and in that case the > DNA trap is just used for (host) lazy fpu context switching like as if the > code was running in userland regularly. And I just tested the following > patch that should get rid of the message by calling fpudna/npxdna directly > (files/patch-fpucontext is the interesting part:) Applied the patch today and I can confirm, there are no more dna messages as expected. A win2k3 guest runs now couple of hours with some stress test and the kernel is still fine. I think this patch solves the broken kqemu on amd64. Great work.