From: Dirk Behme <dirk.behme@googlemail.com>
To: qemu-devel@nongnu.org, Marius Groeger <mgroeger@sysgo.com>
Subject: Re: [Qemu-devel] Wrong reset of MIPS hflags EXL after interrupt?
Date: Thu, 17 Aug 2006 08:51:40 +0200 [thread overview]
Message-ID: <44E411FC.3000503@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0608170819150.29618@mag.sysgo.com>
Marius Groeger wrote:
> I agree, though, that in your debugging, you probably examined a wrong
> context. The actual, current context's EXL should be correct, otherwise
> things wouldn't be working at all.
Argh, debugging different context sounds nice ;) It's my
feeling that while switching between these different context
anything with hflags goes wrong. But I'm only guessing here.
Let's see...
> Having said that, I'm currently playing with nested interrupts - let's see
> how that checks out... :-)
Do several consecutively, non nested, interrupts (e.g.
priodical timer) work for you?
Cheers
Dirk
next prev parent reply other threads:[~2006-08-17 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 17:04 [Qemu-devel] Wrong reset of MIPS hflags EXL after interrupt? Dirk Behme
2006-08-16 18:29 ` Thiemo Seufer
2006-08-16 20:18 ` Dirk Behme
2006-08-17 6:30 ` Marius Groeger
2006-08-17 6:51 ` Dirk Behme [this message]
2006-08-17 7:01 ` Marius Groeger
2006-08-18 8:32 ` Marius Groeger
2006-08-18 10:01 ` Thiemo Seufer
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=44E411FC.3000503@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=mgroeger@sysgo.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).