From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ppc emulation and interrupts
Date: Wed, 21 Jan 2009 19:24:40 +0000 [thread overview]
Message-ID: <49777678.1090406@eu.citrix.com> (raw)
In-Reply-To: <20090121143942.GF29175@csclub.uwaterloo.ca>
Lennart Sorensen wrote:
> On Wed, Jan 21, 2009 at 11:49:10AM +0000, Stefano Stabellini wrote:
>> Hi all,
>> one of the recent problems, noticed after the displaystate change,
>> affects ppc emulation only and is due to the fact that none on ppc
>> emulation is issuing any interrupt request of the CPU_INTERRUPT_EXIT
>> kind if the gui timer is disabled.
>> Hence qemu never leaves the loop in cpu-exec.c:cpu_exec.
>> If the gui timer is enabled qemu is able to leave the loop because the
>> condition (interrupt_request & CPU_INTERRUPT_EXIT) is true when the
>> timer is triggered.
>> I think this is a problem with the ppc emulation but if you ppc guys
>> need the gui timer to be always on, I can arrange for it to be.
>> Regards,
>
> So does this explain why vnc runs fast and sdl runs slow?
No, this bug prevents qemu from working when only vnc is enabled.
> Even with the latest patches, sdl is still slow for ppc emulation. Not
> using much cpu either of course.
>
I'll investigate more on this.
As I said before, sdl shouldn't be noticeable slower now, unless you are
using remote X.
I have just tried debian ppc and I get similar performances using vnc
(localhost) or sdl (local X server).
next prev parent reply other threads:[~2009-01-21 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 11:49 [Qemu-devel] ppc emulation and interrupts Stefano Stabellini
2009-01-21 14:39 ` Lennart Sorensen
2009-01-21 19:24 ` Stefano Stabellini [this message]
2009-01-21 19:42 ` Blue Swirl
2009-01-21 19:44 ` Lennart Sorensen
2009-01-21 17:01 ` 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=49777678.1090406@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.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).