qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Zach Metzinger" <zmetzing@gmail.com>
To: Qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU FreeBSD 6.1 "npxdna: fpcurthread == curthread" spewage
Date: Wed, 21 Jun 2006 14:47:07 -0500	[thread overview]
Message-ID: <22d160bb0606211247k72f98f68pc54a409342092441@mail.gmail.com> (raw)

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

             reply	other threads:[~2006-06-21 19:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 19:47 Zach Metzinger [this message]
2006-06-21 20:54 ` [Qemu-devel] QEMU FreeBSD 6.1 "npxdna: fpcurthread == curthread" spewage Fabrice Bellard
2006-06-22  2:32   ` Zach Metzinger
2006-06-23 20:55     ` Fabrice Bellard
2006-06-23 21:14       ` WaxDragon
2006-06-23 23:11       ` Hetz Ben Hamo
2006-06-24 12:33         ` Fabrice Bellard
2006-06-24  3:54       ` Zach Metzinger
2006-06-24  8:22       ` RE : [Qemu-devel] QEMU FreeBSD 6.1 "npxdna: fpcurthread == curthread"spewage Denis SCHEIDT
2006-06-25 11:55       ` [Qemu-devel] QEMU FreeBSD 6.1 "npxdna: fpcurthread == curthread" spewage Jan Marten Simons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22d160bb0606211247k72f98f68pc54a409342092441@mail.gmail.com \
    --to=zmetzing@gmail.com \
    --cc=Qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).