Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 May 2008 13:01:22 +0200
From:      Juergen Lock <nox@jelal.kn-bremen.de>
To:        Teufel <bsd@kuehlbox.de>
Cc:        freebsd-emulation@freebsd.org
Subject:   Re: seems I finally found what upset kqemu on amd64 SMP... shared gdt! (please test patch :)
Message-ID:  <20080511110122.GA31223@saturn.kn-bremen.de>
In-Reply-To: <48260CF7.5050700@kuehlbox.de>
References:  <20080507162713.73A3A5B47@mail.bitblocks.com> <20080508195843.G17500@delplex.bde.org> <20080509220922.GA13480@saturn.kn-bremen.de> <48260CF7.5050700@kuehlbox.de>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080511110122.GA31223>