From: Artyom Tarasenko <atar4qemu@gmail.com>
To: Pasha Tatashin <pasha.tatashin@oracle.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Subject: Re: [Qemu-devel] SPARC64 supported processors
Date: Thu, 29 Jun 2017 11:45:58 +0200 [thread overview]
Message-ID: <CACXAS8AqFRC+6nXBm86Ed9ReLFxHxNm8FSvmSt3c+13mA2f7VQ@mail.gmail.com> (raw)
In-Reply-To: <4e41c60b-53b8-b917-108a-7cea8cb9e591@oracle.com>
Hi Pasha,
On Tue, Jun 27, 2017 at 7:59 PM, Pasha Tatashin
<pasha.tatashin@oracle.com> wrote:
> Hi,
>
> I am trying to evaluate the current qemu support for sparc64 processors.
> First, it seems -smp is not supported for any processor, is this correct?
> When I set -smp greater than 1, I am getting:
>
> qemu-system-sparc64: Number of SMP CPUs requested (2) exceeds max CPUs
> supported by machine 'sun4u' (1)
>
> I've done some testing for all available sparc64 cpus + latest linux kernel:
>
> Fujitsu Sparc64 Working
> Fujitsu Sparc64 III Exception 0x30 (DAE_side_effect_page) in OpenBios
> Fujitsu Sparc64 IV Working
> Fujitsu Sparc64 V Working
> TI UltraSparc I Working
> TI UltraSparc II Working
> TI UltraSparc IIi Working
> TI UltraSparc IIe Exception 0x28 (division_by_zero) in init_tick_ops
> Can make it to work if is_hummingbird() is changed
> to return 0. The IO stick, and OpenBios stick properties
> are absent, so we have to default to %tick for now.
>
> Sun UltraSparc III Illegal instruction in cheetah_boot():
> wr %g0, %g1, %dcr
> It appears dispatch control register is not implemented.
>
> Sun UltraSparc IIIi
> Sun UltraSparc IV
> Sun UltraSparc IV+
> Sun UltraSparc IIIi+
> In these four CPUs, I am getting exception 0x32 in
> cheetah_generic_boot: stxa %g0, [ %g3 ] #ASI_DMMU
The UltraSPARC III {,i,i+} and IV(+) MMUs are not implemented. IIi is
the best for the sun4u target, I think.
> Sun UltraSparc T1
> Sun UltraSparc T2
Same here. T2 is pretty much a stub currently. The emulation uses the
same MMU as for T1.
> Both of the above boot pretty far but fail in this function when tmpfs is
> mounted:
> direct_pcr_write(unsigned long reg_num, u64 val)
> __asm__ __volatile__("wr %0, 0x0, %%pcr" : : "r" (val));
>
> Seems like performance counter registers are not supported.
Correct. As discussed off-list they are not.
Btw, you can try to get through even without modifying qemu.
Start qemu-system-sparc64 with -s -S options, connect to it with gdb,
set a breakpoint before the instruction and skip it by modifying the
%pc and %npc registers.
> needed to add these to kernel parameters:
> keep_bootcon -> to see where we are panicking
> lpj=1000 -> jiffers could not calculate for some reason.
>
> NEC UltraSparc I Working
>
> Does this look right or may be I have missed something, and we can get some
> of the Sun UltraSparc to work for example?
>
> Thank you,
> Pasha
>
--
Regards,
Artyom Tarasenko
SPARC and PPC PReP under qemu blog: http://tyom.blogspot.com/search/label/qemu
prev parent reply other threads:[~2017-06-29 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 17:59 [Qemu-devel] SPARC64 supported processors Pasha Tatashin
2017-06-29 6:57 ` Mark Cave-Ayland
2017-06-29 9:56 ` Artyom Tarasenko
2017-06-29 9:45 ` 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=CACXAS8AqFRC+6nXBm86Ed9ReLFxHxNm8FSvmSt3c+13mA2f7VQ@mail.gmail.com \
--to=atar4qemu@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pasha.tatashin@oracle.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).