WinUAE QEMU PPC

Thank you to Arnie and Tony. Now the blizzard is working. The system boots, but graphically is slower than cyberstorm, as well as the loading time.

[AMIGASYSTEM]

Originally Posted by AnnaWu

Which is visible via GUI (indicator on status bar)

Yes I know Anna, my question was only to clarify some small doubt on speed loadingof the system OS4

Thanks anyway for the info

[midimax]

Originally Posted by amilo3438

Yeah, why are not configurations restricted to proper hardware when it anyway does not work in other combinations?
...
Edit:
Ok, there in quickstart already exist some configurtions for A1200 and A4000! (what about others)

Restricting to real life hardware is not needed for m68k-aos operating systems, furthermore you may loose all nice m68k UAE extensions.

Maybe some sort of automatic switch to quickstart A1200 when Blizzard PPC rom or switch to quickstart A4000 when Cyberstorm PPC rom is selected is needed for dummies.

[amilo3438]

Yeah, but maybe it could be restricted according to "Chipset Extra" setting!

If "Generic" than you can see all available boards in Expansion tab! (as it is now possible)

If "A500" than you can see only those intended for A500 configuration!

If "A1200" than you can see only those intended for A1200 configuration!

...and so on...

I guess this would be possible to implement!

[Toni Wilen]

No. Quickstart or you need to know what are you doing.

Have you already forgot that 99% of users don't care about PPC. It and any other non-m68k-AOS OS setup is a special case. You are required to know what are you doing.

It has always been my goal to allow all kinds of weird options, only exception being something that simply can't work. (=would cause hardware level conflict)

[amilo3438]

It was just an idea in general! (I do not care anyway)

But you did not answer is it possible to implement? (I guess its because it looks like too boring task, right?)

Originally Posted by Toni Wilen

You are required to know what are you doing.

Does that also implies a good knowledge of how the emulator works!? (because it does not apply to 99% of users)

[Toni Wilen]

Originally Posted by amilo3438

It was just an idea! (I do not care anyway)

But you did not answer is it possible to implement? (I guess is because it looks like too boring task, right?)

1) It makes no sense. Chipset extra should not have anything to do which options are possible.
2) Adding restrictions just because of PPC? It also makes no sense.
3) Current restrictions are caused by software limits, not hardware, software can change. It would become moving target: not going to happen.

"No".

[amilo3438]

Originally Posted by Toni Wilen

1) It makes no sense. Chipset extra should not have anything to do which options are possible.

How it make not sense... you can not use something intended f.e. for A1200 in A500, right? (its not compatible and it would not work anyway on real machines)

Originally Posted by Toni Wilen

2) Adding restrictions just because of PPC? It also makes no sense.

"No".

I was talking generally, not restricted to PPC only!

Ok then, enjoy your well-deserved break!

[Darksun777]

The download link for the qemu-zip file does not work...is there another source?!

[prowler]

Which link are you having trouble with?

[Darksun777]

This link from post#1:

http://www.winuae.net/files/b/qemu-uae.zip

EDIT: Ok i see i Need the PPC-Core Plugin download, thanks

[prowler]

Try the one in The Zone I'm uploading for you now.

[Darksun777]

got it already via the PPC-Core-Plugin download link, thank you!

[midimax]

Latest should be:

http://www.winuae.net/files/b/ppc_plugin.7z (QEMU 2.4 update. Includes both 32-bit and 64-bit versions)

I don't know the required minimum WinUAE version for this.

[Michael]

Some benchmarks (now we have some clue what's going slow)

REAL CPU BlizzardPPC
UltimatePPC.WOS
-----------------------------------------------
Your PPC processor is: PPC 603E
CPU Core running on : 180 MHz
PPC Bus Clock is : 60 MHz
Instruction Cache is : ON & UNLOCKED
Data Cache is now : ON & UNLOCKED
PageTable location : $45000000
PageTableSize is : 2048 KBytes
Current CPU load is : 2219 Percent
Current system load : 11850 Percent

Now comming some PPCMath Tests.......

50M Add : 167 ticks
50M Multiply : 206 ticks
20M Sqrt() : 905 ticks
20M Rnd() : 1040 ticks
20M Sin() : 773 ticks
20M Log() : 834 ticks
50M Bounds : 236 ticks
10M Pow() : 585 ticks


WINUAE BlizzardPPC
UltimatePPC.WOS
-----------------------------------------------
Your PPC processor is: PPC 603E
CPU Core running on : 100 MHz
PPC Bus Clock is : 66 MHz
Instruction Cache is : ON & UNLOCKED
Data Cache is now : ON & UNLOCKED
PageTable location : $72400000
PageTableSize is : 4096 KBytes
Current CPU load is : 0 Percent
Current system load : 0 Percent

Now comming some PPCMath Tests.......

50M Add : 24 ticks
50M Multiply : 24 ticks
20M Sqrt() : 2168 ticks
20M Rnd() : 308 ticks
20M Sin() : 1546 ticks
20M Log() : 2023 ticks
50M Bounds : 47 ticks
10M Pow() : 1331 ticks


WINUAE CyberstormPPC
UltimatePPC.WOS
-----------------------------------------------
Your PPC processor is: PPC 603E
CPU Core running on : 100 MHz
PPC Bus Clock is : 66 MHz
Instruction Cache is : ON & UNLOCKED
Data Cache is now : ON & UNLOCKED
PageTable location : $8400000
PageTableSize is : 4096 KBytes
Current CPU load is : 40 Percent
Current system load : 40 Percent


Now comming some PPCMath Tests.......

50M Add : 165 ticks
50M Multiply : 166 ticks
20M Sqrt() : 2239 ticks
20M Rnd() : 371 ticks
20M Sin() : 1608 ticks
20M Log() : 2074 ticks
50M Bounds : 221 ticks
10M Pow() : 1355 ticks

[Toni Wilen]

Your tests also confirms odd speed difference between difference CPU models which makes no sense in emulation, most instructions are exact same.. Note that used QEMU version is quite old (~1years) because newer ones (at least when it was last tested few months ago) are slower and some programs started crashing.

What happens if you use different PPC models using ppc_model config entry (replace ppc_model=automatic with ppc_model=<type name>):

For example BPPC config but CSPPC CPU: (ppc_model=604e_v2.4)
Or some newer common PPC model, for example ppc_model=750_v3.1

(QEMU PPC models here: http://git.qemu.org/?p=qemu.git;a=bl...dels.c;hb=HEAD)

FPU probably won't get any faster until there is option to use host FPU instead of softfloat library. (But use of host FPU can be difficult if PPC FPU has some special features)

[Michael]

cpu model on the BlizzardPPC configuration does change the cpu model for the test tools and they report a new cpu model, that's cool and funny. (AOS3/WarpOS) Does not seem to effect the speed of simple tests

CyberstormPPC seems to igrnore this, and the tools I tried always reported 604 (under AOS4)

But here is an interesting result from SysMon/RageMem test! Emulation can't be that good

[Toni Wilen]

Originally Posted by Michael

Does not seem to effect the speed of simple tests

Thats odd. So it may not be 100% QEMU problem after all..

CyberstormPPC seems to igrnore this, and the tools I tried always reported 604 (under AOS4)

CPU model detection probably does not know any other CPU types and just selects "best known" one.

But here is an interesting result from SysMon/RageMem test! Emulation can't be that good

Whole test loop probably was converted to host CPU code and was executed in single pass. Most "microbenchmarks" are quite useless when testing JIT emulators, sometimes results are far too good (but technically correct..), sometimes they are totally random.

[AMIGASYSTEM]

Ciao Toni, Today I wanted to do a little experiment, with a software "CD/DVD-RW Burner Virtual" i created a ISO which I then formatted UDF Filesystem. Formatting finished i copied a file in this volume UDF and then mounted as a DVD on OS4.1. Started OS4.1 the new volume was seen without problems by the system, only that it is not possible to see the content or copy data because this book as we know it is set to read-only; do you have a system for access read-write on this volume UDF.

[Toni Wilen]

Originally Posted by AMIGASYSTEM

do you have a system for access read-write on this volume UDF.

No. Emulated optical media writing is not supported.