From: Torbjorn Granlund <tg@gmplib.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu varying performance
Date: Thu, 29 Sep 2011 16:53:52 +0200 [thread overview]
Message-ID: <86pqij5ri7.fsf@shell.gmplib.org> (raw)
In-Reply-To: <20110928093433.GA13116@edde.se.axis.com> (Edgar E. Iglesias's message of "Wed\, 28 Sep 2011 11\:34\:33 +0200")
"Edgar E. Iglesias" <edgar.iglesias@gmail.com> writes:
> But running Debian's 64-bit kernel vmlinux-2.6.32-5-5kc-malta under
> qemu-system-mips64 consumes 100% on the host system, whether the guest
> is idle or busy. (And for qemu-system-mips64el, the same is true for the
> corresponding 64-bit el kernel.)
Hi, It could be any of them or both. You'll have to dig a bit deeper and
see if WAIT insns are beeing issued and if QEMU is successfully decoding
them etc.
Thanks for this advice!
I naively ran 'objdump -dw' on the kernel, looked for wait, and thanks
to the naming of kernel idle loop functions, was able to make educated
guesses about which processors would be fed the 'wait' instruction.
The feeble conclusion made, that passing '-cpu 5Kc' to
qemu-system-mips64{el,} would help, turned out to be correct--now my
mips64 systems uses insignificant host CPU when they idle.
--
Torbjörn
next prev parent reply other threads:[~2011-09-29 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 0:25 [Qemu-devel] Qemu varying performance Torbjorn Granlund
2011-09-28 7:15 ` Andreas Färber
2011-09-28 8:23 ` Torbjorn Granlund
2011-09-28 9:34 ` Edgar E. Iglesias
2011-09-29 14:53 ` Torbjorn Granlund [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 2:49 [Qemu-devel] qemu " Lee
2005-01-26 13:34 ` Johannes Schindelin
2005-01-26 14:49 ` Daniel Egger
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=86pqij5ri7.fsf@shell.gmplib.org \
--to=tg@gmplib.org \
--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.