All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mateusz Loskot <mateusz@loskot.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu-system-sparc uses all host cpu (continued)
Date: Sat, 15 Jan 2011 01:44:30 +0000	[thread overview]
Message-ID: <4D30FBFE.1030407@loskot.net> (raw)

Hi,

I'm running QEMU built from Git current repo to emulate SPARC with
NetBSD 5.0 installed. My host runs x86_64 GNU/Linux with kernel 2.6.35
on Intel P8600 CPU.

I've noticed qemu-system-sparc constantly uses 100% of CPU
I found similar report in the ml archives [1] and tried to apply the
patches mentioned there, but it looks they have been partially added to
Git repo. Only the part in slavio_misc.c seems missing.

Is this known issue?

[1] http://lists.nongnu.org/archive/html/qemu-devel/2006-09/msg00210.html


Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org

             reply	other threads:[~2011-01-15  1:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15  1:44 Mateusz Loskot [this message]
2011-01-15  7:39 ` [Qemu-devel] qemu-system-sparc uses all host cpu (continued) Blue Swirl
2011-01-15 16:01   ` Mateusz Loskot
2011-01-15 16:13     ` Blue Swirl

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=4D30FBFE.1030407@loskot.net \
    --to=mateusz@loskot.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.