From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] linux-user exception handling
Date: Wed, 27 Aug 2008 21:19:12 +0300 [thread overview]
Message-ID: <f43fc5580808271119u6868ac39vb548fbff9e2085f2@mail.gmail.com> (raw)
In-Reply-To: <20080827132255.U54074@stanley.csl.cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
On 8/27/08, Vince Weaver <vince@csl.cornell.edu> wrote:
> On Wed, 27 Aug 2008, Blue Swirl wrote:
>
> >
> > How is that possible, because V9 class CPUs do not have "wim"?
> >
>
> I am running v8plus binaries, which are a horrible mix of v8 and v9 code.
>
> But you are right, "wim" was deleted for v9. The reason I did the code the
> way I did was because the restore_window() function was updating the
> register (even on sparc64).
>
> So I guess the real fix is to implement proper save_window() and
> restore_window(), and also flush_window(). Then make sure that "ta 3" on v9
> calls the proper flush_window() code.
>
> As a temporary workaround though the patch I posted seems to work.
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.
[-- Attachment #2: fix_s32p_wim.diff --]
[-- Type: plain/text, Size: 1772 bytes --]
next prev parent reply other threads:[~2008-08-27 18:19 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 [this message]
2008-08-27 19:02 ` Vince Weaver
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=f43fc5580808271119u6868ac39vb548fbff9e2085f2@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).