Hi Jan, Peng, all, We currently have a better understanding of Peng's work [1] and manage to somewhat reproduce his results on another NXP board, the IMX8QM. Since you showed interest in this, we would like to start implement something a bit more portable and user-friendly.
In this regard, I would like to share some design choices: - Jailhouse image stays more or less the same, all the code is added into a loader, expanding Peng's work to make it more portable (across Arm v8 boards for now) and generic. The loader will boot and init everything that jailhouse and the inmates need. Without the loader jailhouse can be started exactly like it was before. - The loader is platform-specific, and thus it's necessary, at compile-time, to have a parameter that specifies the target (something like `BOOT=` or `TARGET=`), using the root-cell information to fill the correct addresses and compile only the necessary drivers. Without the parameter, the loader is not compiled. - There is going to be a "sync" function at some point, probably when loading the module, that can update the status of jailhouse so that the cells created at boot time are controllable. The idea is to have the same situation as if jailhouse was started with the `enable`. Finally, we would also like to hear from Peng, to understand his current plan so that we don't step in each other's toes. [1] https://groups.google.com/forum/#!topic/jailhouse-dev/IZEFz-e2lh4 Angelo -- 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 jailhouse-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/CADiTV-1QiRhSWZnw%2BkHhJMO-BoA4sAcOmTkQE7ZWbHkGh3Jexw%40mail.gmail.com.
