Am Tue, 28 May 2019 06:22:05 -0700 schrieb <[email protected]>:
> Hello everyone, > > I'm trying to run the ivshmem-demo on a lanner NCA-510A. The inmate > cell seems to be working well. However, I can't get the interruptions > between the cells to work. Is this due to a configuration problem? > (You will find attached my configuration files) I explain : when I > launch the inmate the shared memory is written but the inmate doesn't > react to the uio_send and there is nothing to read in the uio_read... The ivshmem guestcode repo is not tested as well as jailhouse. And together with kernels there are now 3 components to combine. So i would not be surprised if your problem has to do with that uio linux example. But it is not horribly broken and should work! The main issue with it is that people do not read the docs and check out the wrong branch, later use the python code ... which is not tested on jailhouse ... I would suggest two ivshmem-demo cells before you even look at linux+uio. That way you get isvhmem-guestcode out of the picture and will start with just jailhouse. Especially since you later want to run linux in another cell anyways. > here is my : > grep ivshmem /proc/interrupts > 202: 0 0 0 0 0 > 0 0 0 0 0 0 > 0 0 0 0 0 0 > 0 0 0 0 0 0 IR-PCI-MSI > 229376-edge uio_ivshmem > > Second question: the next step of my project will be to run the > uio_ivshmem driver between two linux cells. Is it possible or is the > driver only for the rootCell? The uio stuff will work in either root or non-root, no problem. That is, if it works. Henning > best regards, > > Jeanne > -- 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/20190528210147.6dd80c1d%40md1za8fc.ad001.siemens.net. For more options, visit https://groups.google.com/d/optout.
