On Wednesday, February 6, 2019 at 7:00:35 AM UTC-7, J. Kiszka wrote: > On 06.02.19 13:59, Henning Schild wrote: > > Am Tue, 5 Feb 2019 19:25:28 -0800 > > schrieb <[email protected]>: > > > >> On Friday, February 1, 2019 at 12:32:40 AM UTC-7, J. Kiszka wrote: > >>> You likely want > >>> https://github.com/siemens/linux/commits/jailhouse-enabling/4.14 or > >>> the 4.19-variant that is jailhouse-prepared. That's what > >>> jailhouse-images is building for you. If you just rebuild the > >>> kernel that the original image was using, only adding UIO, you > >>> should be fine with keeping the jailhouse kernel package untouched. > >>> But the cleanest way is reproducing the image via jailhouse-images > >>> after adjusting the parameter you want to change (CONFIG_UIO, > >>> ROOTFS_EXTRA etc.). > >>> > >>> Jan > >>> > >>> -- > >>> Siemens AG, Corporate Technology, CT RDA IOT SES-DE > >>> Corporate Competence Center Embedded Linux > >> > >> That worked! I was able to figure out the correct kernel to build by > >> looking at jailhouse-images/recipes-kernel/linux/linux-jailhouse.bb > >> from when I last generated my image at 4.14.73 > >> (https://github.com/siemens/linux/archive/1dd68658b3a8308a160b0786fc4e1e04d8ff5216.tar.gz). > >> With that, I supplied QEMU with the new UIO-enabled kernel image and > >> built jailhouse and uio_ivshmem.ko and ran the ivshmem jailhouse demo. > >> > >> However, I'm still not sure how to read in the data from the > >> ivshmem-demo. Once I insmod uio_ivshmem.ko, shouldn't there be a > >> device called /dev/uio0 that I can read "Hello From IVSHMEM" from and > >> write back to? And shouldn't there be an entry in /sys/class/uio/? I > >> don't see either of these, and I'm not quite sure how to debug this > >> yet. > > > > Yes you should get that. If you do not, my first guess would be that > > you are not building the jailhouse branch of the guest-code repo. The > > jailhouse version of the PCI interface is slightly different, so the > > probing between the two is not compatible. > > FWIW, I've started a rewrite of the UIO driver against a renovated ivshmem > device (or rather "jhshmem", formerly known as "ivshmem 2.0") that will be > available soon. That UIO driver will become part of the Jailhouse kernel > queue > (targeting upstream eventually). We need to make progress with this topic, > even > if there will be another step needed afterwards. That's good to hear. Do you know when it will be available?
-Michael > > But for now Henning described the way to go. > > Jan > > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > 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]. For more options, visit https://groups.google.com/d/optout.
