From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ppc emulation and interrupts
Date: Wed, 21 Jan 2009 19:01:42 +0200 [thread overview]
Message-ID: <f43fc5580901210901u5259848ua289ee1d3927e272@mail.gmail.com> (raw)
In-Reply-To: <49770BB6.9050707@eu.citrix.com>
On 1/21/09, Stefano Stabellini <stefano.stabellini@eu.citrix.com> 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,
It's not only PPC problem, Sparc64 with -nographic never exits cpu
loop because no timers are running. Serial input does not work,
because IO does not cause exit from cpu loop.
We could add a dummy timer just to exit the cpu loop, but that's a bit ugly.
I think SIGIO was discussed at some point, but rejected.
Would it be very hard to move to the IO thread model?
prev parent reply other threads:[~2009-01-21 17:01 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
2009-01-21 19:42 ` Blue Swirl
2009-01-21 19:44 ` Lennart Sorensen
2009-01-21 17:01 ` Blue Swirl [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=f43fc5580901210901u5259848ua289ee1d3927e272@mail.gmail.com \
--to=blauwirbel@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).