qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sparc32 machine specific maximums
Date: Thu, 6 Dec 2007 19:37:55 +0200	[thread overview]
Message-ID: <f43fc5580712060937x299838b9q4049c03f5ea4bd99@mail.gmail.com> (raw)
In-Reply-To: <4755E31C.40203@earthlink.net>

On 12/5/07, Robert Reif <reif@earthlink.net> wrote:
> Blue Swirl wrote:
>
> >On 12/4/07, Robert Reif <reif@earthlink.net> wrote:
> >
> >
> >>I would be surprised if an SMP kernel actually worked on a multi CPU SS5.
> >>
> >>
> >
> >Prepare for a surprise:
> >
> >
> >
> That's interesting because the fact that it works shows how inaccurate
> the emulation is.

This wonder is not possible because of the any inaccuracies, it's
possible because there is an Open Firmware abstraction layer between
the OS and hardware. If more CPUs are available, Linux just starts
them using the OF interface. Linux can't check whether the system is
physically capable of containing more CPUs, it can merely check that
the platform is Sun4m, which is fully SMP capable.

> Now could you please really surprise me by booting Solaris 2.5 using a
> real sun openprom image ;-)

The interface between OF and hardware is not completely documented
(SMP) and Qemu is by design not completely suitable to emulate
everything that the real prom wants, like caches, performance counters
or test/debug modes. Therefore I'm more interested in booting Solaris
using OpenBIOS image.  While the interface between OF and Solaris is
documented, the assumptions used by Solaris aren't.

But I'd be happy to fix bugs or implement the missing details to
either Qemu or OpenBIOS that help Solaris boot.

  reply	other threads:[~2007-12-06 17:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-02 23:12 [Qemu-devel] [PATCH] sparc32 machine specific maximums Robert Reif
2007-12-03 17:25 ` Blue Swirl
2007-12-03 23:41   ` Robert Reif
2007-12-04 16:12     ` Blue Swirl
2007-12-04 23:30       ` Robert Reif
2007-12-06 17:37         ` Blue Swirl [this message]
2007-12-04 17:26     ` Paul Brook
2007-12-04 18:40       ` Blue Swirl
2007-12-03 23:53   ` Thiemo Seufer
2007-12-04 16:26     ` Blue Swirl
2007-12-04 16:30     ` Andreas Färber

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=f43fc5580712060937x299838b9q4049c03f5ea4bd99@mail.gmail.com \
    --to=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).