From: Blue Swirl <blauwirbel@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Dustin Kirkland <kirkland@canonical.com>
Subject: Re: [Qemu-devel] State of sparc64-softmmu
Date: Tue, 23 Jun 2009 17:58:02 +0300 [thread overview]
Message-ID: <f43fc5580906230758r3f646e36i87455e1a718ae8a6@mail.gmail.com> (raw)
In-Reply-To: <200906222322.45361.paul@codesourcery.com>
On 6/23/09, Paul Brook <paul@codesourcery.com> wrote:
> On Monday 22 June 2009, Anthony Liguori wrote:
> > Paul Brook wrote:
> > >> But this leads me to wonder, is this just an oversite or is there
> > >> something wrong with sparc64-softmmu that we don't recommend building it
> > >> by default?
> > >
> > > My understanding it that there are still several large chunks remaining
> > > to be implemented, and it can not boot any real guest operating systems.
> >
> > If it's not building by default, it's going to bitrot (it already has).
>
>
> Yes, although without any runtime tests it's still likely to suffer quite
> badly from bitrot.
We provide openbios-sparc64 ROM image which can be used standalone for
quick tests. Then CD boot from various distro images (Linux, HelenOS,
OpenSolaris) can be tested, loading works (except for OpenSolaris) but
the kernels does not get very far. Also, Sparc32 Linux user software
can be tested with sparc32plus emulator, this tests the compatibility
mode of the CPU but not 64 bit features. I'm using the above in my
test setup.
In addition, OpenBSD/Sparc64 userland is fully 64 bits and V9, so
bsd-user can test the 64 bit CPU features. This part is not finished
yet. Booting from BSD CD images does not work.
next prev parent reply other threads:[~2009-06-23 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 21:23 [Qemu-devel] State of sparc64-softmmu Anthony Liguori
2009-06-22 22:03 ` Paul Brook
2009-06-22 22:17 ` Anthony Liguori
2009-06-22 22:22 ` Paul Brook
2009-06-23 14:58 ` Blue Swirl [this message]
2009-06-23 14:47 ` 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=f43fc5580906230758r3f646e36i87455e1a718ae8a6@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=kirkland@canonical.com \
--cc=paul@codesourcery.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).