From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ft8fP-0006Su-Sk
	for qemu-devel@nongnu.org; Wed, 21 Jun 2006 15:47:11 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Ft8fM-0006RY-ST
	for Qemu-devel@nongnu.org; Wed, 21 Jun 2006 15:47:11 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ft8fM-0006RV-Mv
	for Qemu-devel@nongnu.org; Wed, 21 Jun 2006 15:47:08 -0400
Received: from [66.249.92.170] (helo=ug-out-1314.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1Ft8qB-0005K8-2E
	for Qemu-devel@nongnu.org; Wed, 21 Jun 2006 15:58:19 -0400
Received: by ug-out-1314.google.com with SMTP id j40so83811ugd
	for <Qemu-devel@nongnu.org>; Wed, 21 Jun 2006 12:47:07 -0700 (PDT)
Message-ID: <22d160bb0606211247k72f98f68pc54a409342092441@mail.gmail.com>
Date: Wed, 21 Jun 2006 14:47:07 -0500
From: "Zach Metzinger" <zmetzing@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [Qemu-devel] QEMU FreeBSD 6.1 "npxdna: fpcurthread == curthread"
	spewage
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Qemu-devel@nongnu.org

Hi-

I'm using qemu-0.8.1 under FreeBSD 6.1-RELEASE from ports with
kqemu-1.3.0pre7 (also from ports). The guest OS is Windows XP SP2.
When I use the -kernel-kqemu flag to qemu, I get the following kernel
console messages:

Jun 21 14:04:57 jitter kernel: npxdna: fpcurthread == curthread 5173 times
Jun 21 14:04:57 jitter kernel: npxdna: fpcurthread == curthread 5174 times
<...>

This happens quite a bit (5-10 a second) when using any block device.
I assume this is because kernel I/O calls are being virtualized and
are the cause of this.

When I do not use -kernel-kqemu, I do not get these messages. In both
cases, Windows appears to work fine.

This thread:
http://tinyurl.com/mbm5l
appears to have some information on why this happens. Has a patch been
released to fix this bug?

--- Zach