November 21, 2010 // 9:48 pm
has now released the PL3 LV1 Hypercall Tracer Payload
which can be used by developers to trace PS3 syscalls and hypercalls.
at PSX-Scene (linked above) reports that KaKaroToKS
has dumped the PS3 LV1 syscalls, and plans to update his payload soon to allow other developers to dump the calls.
To quote: For Those Of You Who Are Asking What This Is:
level-1 syscalls are used to call hypervisor functions. On a PS3 the hypervisor is known as as "lv1? (level1) since it is the lowest level that runs directly on top of the hardware. The operating system is executed on top of this and is known as "lv2? (level2).
The two common operating systems are GameOS which PS3 games run on, and OtherOS which is usually used to run linux. Since both OSes run on top of the same lv1 hypervisor, they use the same set of hypercalls which has been partially documented here.
KaKaRoToKS Recent Tweets:
FINALLY able to dump (over eth) all lv1 calls!! Will push it soon!
To everyone misunderstanding: no lv1 access, all I did was be able to dump the "call trace" of lv1 hypercalls. same as payload_dump_syscalls
Released the hypercall tracer payload! Also merged syscall tracer, and a payload that traces hypercalls+syscalls.
Adding a payload to trace all sc calls (syscalls and hypercalls). Use carefully, this generates race conditions easily!!
Add a payload to trace all read/writes to the vuart by showing the hypercall and the data buffers sent/received
And Finally What Does These All Mean To Us Right Now!
This is work-in-progress, once KaKaRoToKS has finished his poking around the dumps, and detailing the info on his GIT, I will update this thread, even after he is done, it will take some time for various PS3 developers to study all this new information, before it will help out the "end-user" but it is another big step forward in the daily forever-changing and growing-fast PS3 Scene World!