On Friday, March 17, 2023 at 9:01:39 AM UTC+2 Jan Kiszka wrote:

On 15.03.23 19:29, Laurentiu Mihalcea wrote: 
> Hi, 
> 
> I'm not sure if this topic has been discussed before but would it be 
> possible to integrate the Jailhouse driver in the Linux kernel tree? 
> This would allow other kernel modules to utilise Jailhouse and would be 
> useful in cases where user space is not yet available (e.g: during a 
> device's probe()) to do all the setup. 
> 
> 
> Use case: 
>       1) Linux boots 
>       2) device_x's probe() is called 
>       3) User space becomes available. 
> 
> I would be interested in enabling the hypervisor, creating an inmate and 
> loading some image during step 2) of the above flow. 
> 

But you know that Jailhouse startup and non-root cell loading currently 
depends on userspace? How would a built-in Jailhouse driver help there? 


We want to make startup and cell root loading independent of user space. 

e.g 

Use EXPORT_SYMBOL for jailhouse_cmd_cell_load / jailhouse_cmd_cell_load & 
friends. 


What you can already do is pushing the setup into an initramfs. 

 
This won't really help in our case. Our driver (Sound Open Firmware) runs 
at boot and somehow
it already expects that the jailhouse to be enabled in a controlled way. 

e.g -> Our driver already handles loading the inmate and starting it. 

We come from a world where there was no need to use Jailhouse (there was a 
separate DSP core).

Exporting the symbols will allow our driver to call in the jailhouse API 
and create the expected
environment.

Also, where there any attempt to upstream the Jailhouse driver to the Linux 
kernel community?

thanks,
Daniel.
 

-- 
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/a22210d5-6ea5-4926-acc4-fec65ca36884n%40googlegroups.com.

Reply via email to