From: Vince Weaver <vince@csl.cornell.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] linux-user exception handling
Date: Wed, 27 Aug 2008 15:02:32 -0400 (EDT) [thread overview]
Message-ID: <20080827143804.D54290@stanley.csl.cornell.edu> (raw)
In-Reply-To: <f43fc5580808271119u6868ac39vb548fbff9e2085f2@mail.gmail.com>
On Wed, 27 Aug 2008, Blue Swirl wrote:
>
> With this patch I get the sequence AA to MM and then back to AA.
> Strangely Sparc32 prints AA to MM and then back to BB, never reaches
> AA.
Your patch is much better than mine, with it all of the gcc spec2k inputs
work. So I'm all for committing it.
One semi-related thing, according to the documentation V9 increments CWP
on save and decrements it on restore, while V8 does the opposite. I'm not
sure if it is worth making the Qemu save/restore code behave that way too.
Vince
next prev parent reply other threads:[~2008-08-27 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 20:26 [Qemu-devel] linux-user exception handling Vince Weaver
2008-08-25 20:34 ` Blue Swirl
2008-08-27 16:58 ` Vince Weaver
2008-08-27 17:14 ` Blue Swirl
2008-08-27 17:30 ` Vince Weaver
2008-08-27 18:19 ` Blue Swirl
2008-08-27 19:02 ` Vince Weaver [this message]
2008-08-27 19:26 ` 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=20080827143804.D54290@stanley.csl.cornell.edu \
--to=vince@csl.cornell.edu \
--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).