From: Stefan Weil <weil@mail.berlios.de>
To: Tristan Gingold <gingold@adacore.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug] qemu-system-ppc: "Bad clock read" when started with -icount auto
Date: Mon, 04 Jan 2010 15:00:20 +0100 [thread overview]
Message-ID: <4B41F474.5050104@mail.berlios.de> (raw)
In-Reply-To: <2A6F0D68-A7D2-4D53-A4CE-E249418EE7B2@adacore.com>
Tristan Gingold schrieb:
> On Dec 29, 2009, at 4:30 PM, Stefan Weil wrote:
>
>
>> Hi,
>>
>> When qemu-system-ppc is started with argument "-icount auto"
>> (needed for running qemu in the emulated system),
>> it will print lots of "Bad clock read" on stderr.
>>
>> env->can_do_io toggles between 0 and 1.
>>
>
> I have a patch to enable -icount on powerpc. I plan to submit it shortly. Are you in the hurry ?
>
No. When you run qemu in qemu, you never are in a hurry :-)
Stefan
prev parent reply other threads:[~2010-01-04 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B3A2083.2080008@mail.berlios.de>
2010-01-04 10:07 ` [Qemu-devel] [Bug] qemu-system-ppc: "Bad clock read" when started with -icount auto Tristan Gingold
2010-01-04 14:00 ` Stefan Weil [this message]
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=4B41F474.5050104@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=gingold@adacore.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).