From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] target_mmap and host vs target page sizes.
Date: Sun, 30 Sep 2007 19:20:25 +0300 [thread overview]
Message-ID: <f43fc5580709300920g19b835bdx155fc6172f4672a2@mail.gmail.com> (raw)
In-Reply-To: <20070930160528.GF19016@edgar.underground.se.axis.com>
On 9/30/07, Edgar E. Iglesias <edgar.iglesias@axis.com> wrote:
> On Sun, Sep 30, 2007 at 06:45:08PM +0300, Blue Swirl wrote:
> > On 9/30/07, Edgar E. Iglesias <edgar.iglesias@axis.com> wrote:
> > > With this updated patch, I can now reliably run statically linked sparc64 programs on my 32 bit host. Dynamically linked sparc64 programs reliably fail with an unhandled trap 0x37. qemu m68k reliably segfaults with and without the patch. Again, I tested CRIS and MIPS 8K and they both reliably manage to load and run my programs. I also ran some arm (4K pages) programs, which worked fine.
> >
> > 0x37 is TT_PRIV_ACT, taken when privileged instructions are executed
> > in unprivileged mode. Could you try running this program again with -d
> > in_asm,op and see what is the faulting instruction and the generated
> > ops? Maybe some instruction has too strict checks.
>
> Sure. I pasted info from the error and fron the last TB.
> pstate: 0x00000092 ccr: 0x00 asi: 0x00 tl: 0 fprs: 0
Zero %asi?
> 0x00000000b5c516f8: wr %g0, 0xf0, %asi
%asi set to 0xf0 here.
> 0x00000000b5c51734: ldda [ %o1 ] %asi, %f0
Faulting instruction, bad %asi?
> 0x0000: movl_T0_im 0x0
> 0x0001: movl_T1_sim 0xf0
> 0x0002: movl_env_T0 0x9364
This is the wr code, no wonder %asi was zero.
Thanks a lot! I'll fix this immediately.
prev parent reply other threads:[~2007-09-30 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 1:18 [Qemu-devel] target_mmap and host vs target page sizes Edgar E. Iglesias
2007-09-30 7:27 ` Blue Swirl
2007-09-30 9:53 ` Edgar E. Iglesias
2007-09-30 11:47 ` Edgar E. Iglesias
2007-09-30 15:45 ` Blue Swirl
2007-09-30 16:05 ` Edgar E. Iglesias
2007-09-30 16:20 ` 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=f43fc5580709300920g19b835bdx155fc6172f4672a2@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).