qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vince Weaver <vince@csl.cornell.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] mipsIV support for mips-linux-user
Date: Mon, 30 Mar 2009 13:29:29 -0400 (EDT)	[thread overview]
Message-ID: <20090330131050.L20376@stanley.csl.cornell.edu> (raw)
In-Reply-To: <20090330043539.GE12026@hall.aurel32.net>

On Mon, 30 Mar 2009, Aurelien Jarno wrote:

> Do you have the end of qemu.log when running your code with -d in_asm,op?

The first cop1x instruction happens relatively deep into the program, so 
the debugging dump is pretty larege.  How far back do you want?

It looks like no matter what cpu option I pick, the HFLAGS is set to 
0x0022 (which is only the usermode and FPU flags).

Because of this the generated assembly in the debug output unconditionally 
generates an illegal instruction exception the first time a cop1x 
instruction is executed (in my case, "msub.d")

I've been digging through the qemu mips code, and I can't seem to find 
where the hflags are set in the usermode case.

The only place that sets the MIPS_HFLAG_COP1X is in exec.h, 
"compute_hflags()" but that doesn't ever seem to be called if 
CONFIG_USER_ONLY

Vince

  reply	other threads:[~2009-03-30 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29 20:56 [Qemu-devel] mipsIV support for mips-linux-user Vince Weaver
2009-03-30  1:05 ` Aurelien Jarno
2009-03-30  2:14   ` Vince Weaver
2009-03-30  4:35     ` Aurelien Jarno
2009-03-30 17:29       ` Vince Weaver [this message]
2009-04-08 22:17         ` Aurelien Jarno
2009-04-09  1:00           ` Vince Weaver

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=20090330131050.L20376@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).