qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bob Breuer <breuerr@mc.net>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: sparc OBP psr value
Date: Sun, 12 Dec 2010 13:13:18 -0600	[thread overview]
Message-ID: <4D051ECE.509@mc.net> (raw)
In-Reply-To: <AANLkTiniG3tipRsRQinF3KF-2ZGP9n4FJbzrW1+PrMdw@mail.gmail.com>

Blue Swirl wrote:
> On Sun, Dec 12, 2010 at 12:17 AM, Bob Breuer <breuerr@mc.net> wrote:
>   
>> Under qemu-system-sparc, I found a problem with OBP's psr commands.
>>
>> On an real SS-20, I get:
>>    ok .psr
>>    CWP: 4  ET: 1  PS: 1  S: 1  PIL: f  EF: 1  EC: 0  ICC: nZvc  VER: 0
>> IMPL: 4
>>    ok %psr .
>>    40401fe4
>> But with qemu, it all shows up as 0, such as:
>>    ok .psr
>>    CWP: 0  ET: 0  PS: 0  S: 0  PIL: 0  EF: 0  EC: 0  ICC: nzvc  VER: 0
>> IMPL: 0
>>    ok %psr .
>>    0
>> while "info registers" says the psr should be 40001de0.
>>     
>
> I can't reproduce this:
> ok .psr
> CWP: 0  ET: 1  PS: 1  S: 1  PIL: f  EF: 0  EC: 0  ICC: nZvc  VER: 0  IMPL: 4
> ok %psr .
> 40400fe0
>   

Ah, I forget to verify it with the SS-20 default cpu where it does
indeed work, but in that case OBP gets an access fault which leaves it
only partially initialized.

For me, either OBP under SS-5 with it's default cpu, or SS-20 with
SuperSparc 60 both show the failure.  The most obvious is SS-20 with
Ross RT625 where it misdetects the cpu as a 605e.

This is with a 32-bit x86 host (both Debian 5.0.7 and win32).

Bob

  reply	other threads:[~2010-12-12 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12  0:17 [Qemu-devel] sparc OBP psr value Bob Breuer
2010-12-12  8:59 ` [Qemu-devel] " Blue Swirl
2010-12-12 19:13   ` Bob Breuer [this message]
2010-12-15 15:07     ` Bob Breuer

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=4D051ECE.509@mc.net \
    --to=breuerr@mc.net \
    --cc=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).