WinUAE QEMU PPC - Page 19

Michael · 22 December 2015, 18:28

Some more real life test!

This time a universal LhA 2.15 compression test.
68k version, WarpUP version and OS4/PPC version
OS4:MUI directory copied to ram: and packed on ram:

Amiga1200
Real 68060/68K - 62 sec
Real 603@180/WUP - 56 sec
Real 603@180/OS4 - 36 sec

WinUAE
68020/68K - 2 sec
68060+PPC/68K - 5 sec
68060+PPC/WUP - 210 sec

PPC/OS4 - 7 sec

Am I configuring something wrong?
Or the dual cpu emulation is somewhat broken/unoptimized ?

68K is slowing down more then 2 times when ppc is emulated, that's ok.
But why the PPC cpu is so slow when 68K is emulated too,
when it runs at a very acceptable speed in PPC only mode.
And the host CPU has plenty of unused resources.

Toni Wilen · 22 December 2015, 18:42

Quote:

Originally Posted by Michael

Am I configuring something wrong?
Or the dual cpu emulation is somewhat broken/unoptimized ?

68K is slowing down more then 2 times when ppc is emulated, that's ok.
But why the PPC cpu is so slow when 68K is emulated too,
when it runs at a very acceptable speed in PPC only mode.
And the host CPU has plenty of unused resources.

M68+PPC emulation was as simple as: "Seems to work and randomly chosen programs do what they are supposed to do. Done. Waiting for feedback."

Attach your version of lha.

Michael · 22 December 2015, 18:48

http://aminet.net/util/arc/lha_68k.lha
http://aminet.net/util/arc/lha_wos.lha
http://aminet.net/util/arc/lha_os4.lha

Tomislav · 23 December 2015, 09:43

I think that PPC OS emulates 68k instructions and don't use 68k processor on card!?

Toni Wilen · 23 December 2015, 09:49

Quote:

Originally Posted by Michael

Some more real life test!

Do you also get same results without 68k JIT? It can cause (much) longer 68k<>PPC interrupt latency.

Quote:

Originally Posted by Tomislav

I think that PPC OS emulates 68k instructions and don't use 68k processor on card!?

Only OS4 does that.

Michael · 23 December 2015, 16:00

WinUAE Interpreted
68060+PPC/68K - 27 sec
68060+PPC/WUP - 120 sec

Much better results, but still somewhat slow.

Also WarpQuake has improved to 20 FPS.

Toni Wilen · 29 December 2015, 16:23

Not sure if it helps but I added extra signaling to m68k side when PPC side causes m68k interrupt, at least in theory it should help if JIT and/or if CPU Idle is enabled.

http://www.winuae.net/files/b/winuae.7z

Michael · 01 January 2016, 09:38

The best I could get was with idle sliders at far right position
Interpreted mode is slower then it used to be :-(

WinUAE Jit BlizzardPPC
68060+PPC/68K - 4 sec
68060+PPC/WUP - 170 sec

Toni Wilen · 01 January 2016, 16:12

Quote:

Originally Posted by Michael

[FONT=Lucida Console][SIZE=5][SIZE=3][FONT=Arial]The best I could get was with idle sliders at far right position
Interpreted mode is slower then it used to be :-(

What was the datestamp of winuae.exe? I did some changes recently that broke it and then later fixed some slowdown issues.

Does today's version have same problem?

(Some kind of test script would be nice that does everything automatically, I am too lazy to run manual tests...)

jdog320 · 02 January 2016, 07:32

When I try to run a program for WOS like quake ii or adoomppc it just generates a warpos page fault in amigaos

Michael · 05 January 2016, 07:08

Quote:

Originally Posted by jdog320

When I try to run a program for WOS like quake ii or adoomppc it just generates a warpos page fault in amigaos

That's common for misconfiguration of warpup. Need to play with env vars and correct sublibs for used hardware.

Michael · 05 January 2016, 07:35

I do it simple way.

> Copy MUI: to RAM:MUI ALL QUIET
> uptime
> LHA a -r RAM:test1.lha RAM:MUI/
> uptime

measure the difference in uptime in seconds

Michael · 05 January 2016, 07:50

Another idea...
I have no idea how it works internally, but maybe changing priorities for CPU can give a boost to ppc side.

i.e. when we run a dual cpu config, we can have a priority switch which of the cpus
is more important. So that when we select ppc, it runs full speed, and 68k is synced with it, when ppc loop is finished and has to signal 68k. Currently it looks as if 68k is running at higher priority and polling ppc for input, thus ppc cpu runs only a fraction of time, or something like that?

jdog320 · 06 January 2016, 12:52

Quote:

Originally Posted by Michael

That's common for misconfiguration of warpup. Need to play with env vars and correct sublibs for used hardware.

How? Also I like to add that when I try to run stuff it the fault reads something about memory access violation. Both Memory protection on or off. I also couldn't play any Warp3d games which depend on warp3dppc.library and even w3d demos. BTW i'm using wazp3d.

Michael · 07 January 2016, 04:59

Memory protection warning is usually the case for all ppc software that does not enforce memory alignment (a lot don't!) and was advised to be used for developers. There was some option to disable this, then all software starts to work (or you can install older (v4 ?) lib that does not enforce it) Have not tried 3D yet.

jdog320 · 07 January 2016, 12:49

Quote:

Originally Posted by Michael

Memory protection warning is usually the case for all ppc software that does not enforce memory alignment (a lot don't!) and was advised to be used for developers. There was some option to disable this, then all software starts to work (or you can install older (v4 ?) lib that does not enforce it) Have not tried 3D yet.

Do I just disable memory Protection in the WarpUP prefs?

Toni Wilen · 15 January 2016, 08:42

OS4 compatible UAE expansion device development status thread is here: http://eab.abime.net/showthread.php?t=81146

turrican3 · 01 May 2016, 05:59

I know that you choose your path to emulate amiga ppc boards.
But, perhaps you could have a look to the model 3 (sega ppc) emulator souce code ?? Perhaps there is something interesting to do with it.
The link : http://www.supermodel3.com/Files/Sup...l_0.2a_Src.zip
It support ppc 603e and R from 50mz to 166 mhz.
This emulator run really fast on my poor corei5.

Toni Wilen · 01 May 2016, 09:46

Standard answer: No MMU emulation.

16 September 2016, 03:46

PPC Mac guys haven been giving some love to the QEMU PPC core. There's a WIP fork there, no idea when will be merged upstream. They made big progress and were able to run not only MacOS X, but MacOS 9 too.

I'm not sure if they improve the PPC emulation, but there it is

https://github.com/ozbenh/qemu/tree/wip

What about WinUAE's QEMUVGA? Have you considered to merge it to upstream too? Any possible issue because the code got modified to a concrete platform or those fixes would provide a more reliable vga? I see SCSI, sound, glue code for qemu emulation in dll and network code too. Why? O_O

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
QEMU TCG as JIT replacement?	KillaByte	request.UAE Wishlist	21	30 January 2018 16:05
PPC emulation for winuae	marauder	request.UAE Wishlist	25	04 November 2014 06:13
WinUAE PPC thread	B14ck W01f	support.WinUAE	301	10 September 2014 16:34
WinUAE ppc support?	blasterreal	support.WinUAE	8	29 September 2010 00:51
PPC on WinUAE ?	glue	request.UAE Wishlist	4	28 January 2007 12:04

22 December 2015, 18:28	#361
Michael A1260T/PPC/BV/SCSI/NET Join Date: Jan 2013 Location: Moscow / Russia Posts: 839	Some more real life test! This time a universal LhA 2.15 compression test. 68k version, WarpUP version and OS4/PPC version OS4:MUI directory copied to ram: and packed on ram: Amiga1200 Real 68060/68K - 62 sec Real 603@180/WUP - 56 sec Real 603@180/OS4 - 36 sec WinUAE 68020/68K - 2 sec 68060+PPC/68K - 5 sec 68060+PPC/WUP - 210 sec PPC/OS4 - 7 sec Am I configuring something wrong? Or the dual cpu emulation is somewhat broken/unoptimized ? 68K is slowing down more then 2 times when ppc is emulated, that's ok. But why the PPC cpu is so slow when 68K is emulated too, when it runs at a very acceptable speed in PPC only mode. And the host CPU has plenty of unused resources.

22 December 2015, 18:48	#363
Michael A1260T/PPC/BV/SCSI/NET Join Date: Jan 2013 Location: Moscow / Russia Posts: 839	http://aminet.net/util/arc/lha_68k.lha http://aminet.net/util/arc/lha_wos.lha http://aminet.net/util/arc/lha_os4.lha

23 December 2015, 09:43	#364
Tomislav Registered User Join Date: Aug 2014 Location: Zagreb / Croatia Posts: 302	I think that PPC OS emulates 68k instructions and don't use 68k processor on card!?

23 December 2015, 16:00	#366
Michael A1260T/PPC/BV/SCSI/NET Join Date: Jan 2013 Location: Moscow / Russia Posts: 839	WinUAE Interpreted 68060+PPC/68K - 27 sec 68060+PPC/WUP - 120 sec Much better results, but still somewhat slow. Also WarpQuake has improved to 20 FPS.

29 December 2015, 16:23	#367
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,506	Not sure if it helps but I added extra signaling to m68k side when PPC side causes m68k interrupt, at least in theory it should help if JIT and/or if CPU Idle is enabled. http://www.winuae.net/files/b/winuae.7z

01 January 2016, 09:38	#368
Michael A1260T/PPC/BV/SCSI/NET Join Date: Jan 2013 Location: Moscow / Russia Posts: 839	The best I could get was with idle sliders at far right position Interpreted mode is slower then it used to be :-( WinUAE Jit BlizzardPPC 68060+PPC/68K - 4 sec 68060+PPC/WUP - 170 sec

02 January 2016, 07:32	#370
jdog320 Registered User Join Date: Oct 2015 Location: Anywhere City Posts: 188	When I try to run a program for WOS like quake ii or adoomppc it just generates a warpos page fault in amigaos

05 January 2016, 07:35	#372
Michael A1260T/PPC/BV/SCSI/NET Join Date: Jan 2013 Location: Moscow / Russia Posts: 839	I do it simple way. > Copy MUI: to RAM:MUI ALL QUIET > uptime > LHA a -r RAM:test1.lha RAM:MUI/ > uptime measure the difference in uptime in seconds

05 January 2016, 07:50	#373
Michael A1260T/PPC/BV/SCSI/NET Join Date: Jan 2013 Location: Moscow / Russia Posts: 839	Another idea... I have no idea how it works internally, but maybe changing priorities for CPU can give a boost to ppc side. i.e. when we run a dual cpu config, we can have a priority switch which of the cpus is more important. So that when we select ppc, it runs full speed, and 68k is synced with it, when ppc loop is finished and has to signal 68k. Currently it looks as if 68k is running at higher priority and polling ppc for input, thus ppc cpu runs only a fraction of time, or something like that?

07 January 2016, 04:59	#375
Michael A1260T/PPC/BV/SCSI/NET Join Date: Jan 2013 Location: Moscow / Russia Posts: 839	Memory protection warning is usually the case for all ppc software that does not enforce memory alignment (a lot don't!) and was advised to be used for developers. There was some option to disable this, then all software starts to work (or you can install older (v4 ?) lib that does not enforce it) Have not tried 3D yet.

15 January 2016, 08:42	#377
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,506	OS4 compatible UAE expansion device development status thread is here: http://eab.abime.net/showthread.php?t=81146

01 May 2016, 05:59	#378
turrican3 Moon 1969 = amiga 1985 Join Date: Apr 2007 Location: belgium Age: 48 Posts: 3,913	I know that you choose your path to emulate amiga ppc boards. But, perhaps you could have a look to the model 3 (sega ppc) emulator souce code ?? Perhaps there is something interesting to do with it. The link : http://www.supermodel3.com/Files/Sup...l_0.2a_Src.zip It support ppc 603e and R from 50mz to 166 mhz. This emulator run really fast on my poor corei5.

01 May 2016, 09:46	#379
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,506	Standard answer: No MMU emulation.

16 September 2016, 03:46	#380
timofonic Posts: n/a	PPC Mac guys haven been giving some love to the QEMU PPC core. There's a WIP fork there, no idea when will be merged upstream. They made big progress and were able to run not only MacOS X, but MacOS 9 too. I'm not sure if they improve the PPC emulation, but there it is https://github.com/ozbenh/qemu/tree/wip What about WinUAE's QEMUVGA? Have you considered to merge it to upstream too? Any possible issue because the code got modified to a concrete platform or those fixes would provide a more reliable vga? I see SCSI, sound, glue code for qemu emulation in dll and network code too. Why? O_O

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)