Hi Devshatwar, Kiszka Thanks for your reply, it's helpful for us. Also there are some additional questions we want to know.
> MM Question: > 3. Does the hypervisor have some KPI data? > > such as below info > > a. How Fast boot time when OS mount filesystem; > > b. How Fast boot time to show first image? > > c. How Fast boot time to play audio? > > d. How Fast boot time to show RVC? > > e. How Fast boot time to run second OS filesystem and touch? > Devshatwar >> This varies across different platforms. There is no benchmarking data for the TI platform Jingyan >> If there didn't have the detail data on the J7 platfrom, is OK. However, what we want to know is that does jailhouse has some fastboot solution? Because now the jailhouse start is depend on the first Linux(Of course, the Linux optimize should done by SoC Vender or Ourselfs). If we want to Show image/audio/RVC(Astern imaging system), but this function is in the non-root cell OS, how can jailhouse support it. > MM Question > 17. How many resource usage when the hypervisor running? (such as Resource > usage: CPU, RAM, ROM) > Devshatwar >> Currenly, for TI platform, 6MB RAM is reserved for hypervisor There is some CPU usage when enabling hypervisor and using VM management hypercalls. At runtime, Jailhouse is involved only while handling the interrupt injection part and IVshmem Jingyan >> In this case, we want to know some detail data about hypervisor resource usage. With upon answer, we know the RAM is 6MB, how about CPU and ROM? We know the CPU use should be very less(Like < 2% or < 1%), Is there a detail theoretical or practical tests results? BR, Jingyan -----Original Message----- From: Jan Kiszka <[email protected]> Sent: 2020年11月6日 19:47 To: Nikhil Devshatwar <[email protected]>; Liang Jingyan (M) <[email protected]> Cc: [email protected]; Xiao Jianhao (M) <[email protected]>; GAO Zhao (M) <[email protected]>; THOMAS Deuilhe (M) <[email protected]> Subject: Re: [J7] jailhouse hypervisor in TI J7 On 06.11.20 11:29, 'Nikhil Devshatwar' via Jailhouse wrote: > On 06:30-20201106, Liang Jingyan (M) wrote: >> >> 14. What the hypervisor have got Safety certification level? >> >> if no safety certification, pls share some introduce how does it make safety? >> >> > > I think the smaller code base, deterministic resource allocation and > other decisions are taken considering the usage of this hypervisor in > safety critical systems. This shoud ease in certification. > > However, there is no certification done for Jailhouse > ...and that is because of the lack of a suitable hardware platform - up to now - which provides the necessary safety properties in order to use the hypervisor as a safety element. Certifying the Jailhouse code base itself would be doable with reasonable effort (we actually discussed that with a certification authority, TÜV, already). However, that alone would not help you if you cannot map it on some real hardware. Check, e.g, if you can get a safety manual that covers the A-core MMU so that Jailhouse can rely on it (and/or check it during runtime) for establishing spatial partitioning. You can also watch [1] on that, namely the discussion at the end of my talk. It's old but - to my best knowledge - still valid in this regard, unfortunately. A good share of these issues we are currently trying to address via hardware/software co-design in a research project [2]. Jan [1] https://connect.linaro.org/resources/hkg18/hkg18-115/ [2] https://www.selene-project.eu/ -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/0fe28eddb98b46fa80ee49b866d84ed0%40MXPO1FGAW.fgremc.it.
