Thank you for the corrections, I appreciate it.
Regarding the integer vs float for zero-ing a table, if we were to ignore alignment, cache hits/misses, etc, integer stores and double-float stores have the same cycle latency (2:1). I remember a long time ago I was doing some quick tests on seeing how to zero a small block of memory quickly. IIIRC, dcbz came out on top even with it being an Execution Serialization instruction. Then again, I have an awful memory (lol)
I've found a few optimized memcpy PowerPC 32-bit implementations on the web and all of them implemented double-float stores to some degree to speed up the memcpy.
Regarding eieio, that shouldn't be needed if SGE is low in HID0. A sync shouldn't be required if this is being set in Real Mode (translation off) and if so, the sync would simply need to be done sometime after all the PTEs are written and before translation is enabled. I'll add them regardless for the case that SGE is high in HID0 and/or PTEs are being rewritten while translation is on.
Regarding the integer vs float for zero-ing a table, if we were to ignore alignment, cache hits/misses, etc, integer stores and double-float stores have the same cycle latency (2:1). I remember a long time ago I was doing some quick tests on seeing how to zero a small block of memory quickly. IIIRC, dcbz came out on top even with it being an Execution Serialization instruction. Then again, I have an awful memory (lol)
I've found a few optimized memcpy PowerPC 32-bit implementations on the web and all of them implemented double-float stores to some degree to speed up the memcpy.
Regarding eieio, that shouldn't be needed if SGE is low in HID0. A sync shouldn't be required if this is being set in Real Mode (translation off) and if so, the sync would simply need to be done sometime after all the PTEs are written and before translation is enabled. I'll add them regardless for the case that SGE is high in HID0 and/or PTEs are being rewritten while translation is on.