06-20-2016, 03:50 PM
(06-20-2016, 02:42 PM)ssvb Wrote:Ok, thanks. They seem to have reinvented the UEFI Runtime Services wheel. But the links are mostly about enabling an easier way for the virtualization stuff. It's not the monitor in its entirety. But thank you for the info. I found I have the spec on PSCI on my computer for the long time.(06-20-2016, 01:30 PM)z4v4l Wrote: Does Allwinner let you implememt your own Monitor? And I mean not just entering secure state, after BROM, I mean the monitor mode handler, who manages SMC's?PSCI is implemented as a secure monitor and provides an SMC based interface. You can check the U-Boot code for more details, or look at the following patch sets:
http://lists.denx.de/pipermail/u-boot/20...52872.html
http://lists.denx.de/pipermail/u-boot/20...67594.html
So you say, with Allwinner SoC's, any 3rd party developer can implement its own Monitor and give their users all Secure world stack? Sounds too cool to be a reality. In fact, the standard by Arm implies this layer is owned by silicon vendor and it is not available to freely implement your own. They provide PSCI as a recommendation standard and they provide a reference implementation for it. But they say PSCI should reside in SPF (secure platform firmware), which in turn is owned by the silicon vendor and you can not provide your own. You only may somehow get certified for your TrustedOS, but I have no idea how much it costs this does work. Still, you will not be able to supply SPF. This is how I understand this mess thing on the arm architecture. If I am wrong, please correct me.
ANT - my hobby OS for x86 and ARM.