qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: sparc32 do_unassigned_access overhaul
Date: Fri, 15 Jan 2010 22:11:04 +0100	[thread overview]
Message-ID: <fb8d4f71001151311u4e5a0ec6vab0656494ebc957f@mail.gmail.com> (raw)
In-Reply-To: <f43fc5581001151145v77ea594dk7288373974413e8f@mail.gmail.com>

2010/1/15 Blue Swirl <blauwirbel@gmail.com>:
> On Fri, Jan 15, 2010 at 6:46 PM, Artyom Tarasenko
> <atar4qemu@googlemail.com> wrote:
>> According to pages 9-31 - 9-34 of "SuperSPARC & MultiCache Controller
>> User's Manual":
>>
>> 1. "A lower priority fault may not overwrite the
>>    MFSR status of a higher priority fault."
>> 2. The MFAR is overwritten according to the policy defined for the MFSR
>> 3. The overwrite bit is asserted if the fault status register (MFSR)
>>   has been written more than once by faults of the same class
>> 4. SuperSPARC will never place instruction fault addresses in the MFAR.
>>
>> Implementation of points 1-3 allows booting Solaris 2.6 and 2.5.1.
>
> Nice work! This also passes my tests.

I'm afraid we still are not there yet though: Solaris 7 fails potentially due to
another bug in the MMU emulation, and the initial [missing-] RAM
detection in OBP fails
very probably due to a bug in in the MMU emulation.

> However, there are some CODING_STYLE issues.

Is it something you do by hand (or, actually, by eyes), or is there a
way I can automatically test my patches before sending?

-- 
Regards,
Artyom Tarasenko

solaris/sparc under qemu blog: http://tyom.blogspot.com/

  reply	other threads:[~2010-01-15 21:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15 18:46 [Qemu-devel] sparc32 do_unassigned_access overhaul Artyom Tarasenko
2010-01-15 19:45 ` [Qemu-devel] " Blue Swirl
2010-01-15 21:11   ` Artyom Tarasenko [this message]
2010-01-15 21:26     ` Blue Swirl
2010-01-15 21:48       ` Artyom Tarasenko
2010-01-19 17:30         ` Artyom Tarasenko
2010-01-19 19:32           ` Blue Swirl
2010-01-19 21:44             ` Artyom Tarasenko
2010-01-20 18:29               ` Blue Swirl
2010-01-22 18:00               ` Blue Swirl
2010-01-22 20:51                 ` Artyom Tarasenko
2010-01-23  7:55                   ` Blue Swirl
2010-01-23 16:46                     ` Artyom Tarasenko
2010-01-23 18:39                       ` 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=fb8d4f71001151311u4e5a0ec6vab0656494ebc957f@mail.gmail.com \
    --to=atar4qemu@googlemail.com \
    --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).