From owner-freebsd-emulation@FreeBSD.ORG Sun May 11 11:03:38 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 0B00C106564A for ; Sun, 11 May 2008 11:03:38 +0000 (UTC) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn.kn-bremen.de [212.63.36.242]) by mx1.freebsd.org (Postfix) with ESMTP id B68488FC1A for ; Sun, 11 May 2008 11:03:37 +0000 (UTC) (envelope-from nox@saturn.kn-bremen.de) Received: by gwyn.kn-bremen.de (Postfix, from userid 10) id C44842D1FC5; Sun, 11 May 2008 13:03:36 +0200 (CEST) Received: from saturn.kn-bremen.de (nox@localhost [127.0.0.1]) by saturn.kn-bremen.de (8.14.2/8.13.8) with ESMTP id m4BB1Ntt031241; Sun, 11 May 2008 13:01:23 +0200 (CEST) (envelope-from nox@saturn.kn-bremen.de) Received: (from nox@localhost) by saturn.kn-bremen.de (8.14.2/8.13.6/Submit) id m4BB1MEe031240; Sun, 11 May 2008 13:01:22 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Sun, 11 May 2008 13:01:22 +0200 To: Teufel Message-ID: <20080511110122.GA31223@saturn.kn-bremen.de> Mail-Followup-To: Teufel , freebsd-emulation@freebsd.org References: <20080507162713.73A3A5B47@mail.bitblocks.com> <20080508195843.G17500@delplex.bde.org> <20080509220922.GA13480@saturn.kn-bremen.de> <48260CF7.5050700@kuehlbox.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48260CF7.5050700@kuehlbox.de> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-emulation@freebsd.org 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: Sun, 11 May 2008 11:03:38 -0000 On Sat, May 10, 2008 at 11:00:39PM +0200, Teufel wrote: > >> 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. Thanx! :) And I just committed the update. Juergen