> > 
> > I am curious that besides of the special ivshmem2 driver and patches to 
> > uio, are there any other significant changes to the kernel source? 
> > 
>
> You can check the commits: 
>   - uio ivshmem driver 
>   - ivshmem-net driver (lots of commits in queues/jailhouse, folded in 
>     stable) 
>   - virtio-over-ivshmem (experimental, only in queues/jailhouse so far) 
>   - driver for debug console (only relevant for bring-ups) 
>   - some export-symbols, not needed with kallsyms workaround (as long as 
>     that works) 
>   - some dts changes for marvell arm64 boards 
>
> > Because I am using stock 4.19 with PREEMPT_RT, i can run Nuttx and it 
> > works like a charm without any noticeable bugs. 
> > 
>
> It depends on the use case what would be missing, but things generally 
> work. At least booting. 
>
>
Thanks for the information.

Now I know how to port my old modified ivshmem driver now.

I am on x86_64 so I think I am good using the stock kernel with separately 
compiled driver.

One more question, 

As long as my user-space program don't write to the readonly region and 
trigger a fault in the hypervisor.

Without the uio readonly patch, things should work correctly, yes?

Thanks, 

Yang




 

-- 
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/7b537982-4415-44ba-a538-ffb599634633%40googlegroups.com.

Reply via email to