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 <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] sparc32 fix carry flag handling (Solaris bootblk fix)
Date: Wed, 16 Dec 2009 17:41:56 +0100	[thread overview]
Message-ID: <fb8d4f70912160841m399d35b1t38040ef969b736fe@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580911041144o2eff70f8ydc0c14cda7c7ecdc@mail.gmail.com>

2009/11/4 Blue Swirl <blauwirbel@gmail.com>:
> On Wed, Nov 4, 2009 at 1:58 AM, Artyom Tarasenko
> <atar4qemu@googlemail.com> wrote:
>> The page 108 of the SPARC Version 8 Architecture Manual describes
>> that addcc and addxcc shall compute carry flag the same way.
>> The page 110 claims the same about subcc and subxcc instructions.
>> This patch fixes carry computation in corner cases and removes redundant code.
>> The most visible effect of the patch is enabling Solaris boot when using OBP.
>
> Thanks, applied.
>
> Could you describe the steps how to boot Solaris with OBP? I'm sure
> there are a lot of people who'd like to test if their favorite Sparc
> Solaris programs work on QEMU.

I gathered a little how-to here:
http://tyom.blogspot.com/2009/12/solaris-under-qemu-how-to.html

If the patches will made it into 0.12, I think it's worth to mention
OBP and kadb boot support as a new feature. What do you think?

Actually the shell-boot is also pretty close. We just need to fix the
NF-bit handling in MMU. I'm experimenting with a real SS-20 to
understand how it is supposed to work. (the MCC manual doesn't
describe it clear enough, as you have pointed out before).

-- 
Regards,
Artyom Tarasenko

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

      parent reply	other threads:[~2009-12-16 16:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 23:58 [Qemu-devel] [PATCH] sparc32 fix carry flag handling (Solaris bootblk fix) Artyom Tarasenko
2009-11-04 19:44 ` [Qemu-devel] " Blue Swirl
2009-11-05 20:48   ` Artyom Tarasenko
2009-11-13 14:28     ` Artyom Tarasenko
2009-11-13 21:01       ` Blue Swirl
2009-12-10 18:27         ` Artyom Tarasenko
2009-12-12  9:07           ` Blue Swirl
2009-12-16 16:41   ` Artyom Tarasenko [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=fb8d4f70912160841m399d35b1t38040ef969b736fe@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).