Le mercredi 29 mai 2019 09:42:02 UTC+2, [email protected] a écrit : > Le mardi 28 mai 2019 21:01:52 UTC+2, Henning Schild a écrit : > > Am Tue, 28 May 2019 06:22:05 -0700 > > schrieb <jeanne.***@gmail.com>: > > > > > 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 > > > > > Hello everyone, > > > First of all, thank you very much for your help! > > > > I can get two inmates ivshmem-demo to work without any problems with all the > interruptions. > > > > For the driver uio_ivhsmem I took the jailhouse branch on the git. The file > /dev/uio0 pops well and my ivshmem-demo inmate writes well on it. However, > there are still no interruptions... > > Here is my lspci -v on my virtual PCI on the rootCell side. Is this good ? > > lspci -v > 00:0e.0 Unassigned class [ff00]: Red Hat, Inc Inter-VM shared memory > I/O behind bridge: 0000e000-0000efff > > Best regards, > > Jeanne
Hello everyone, Now I can get the demo-ivshmem to work with my root cell too (it seems that removing the.shmem_protocol in the pci_device unlocked the situation I don't know why). Now I'm trying to get this driver to work on my inmate linux but when I insert the module I don't have a /dev/uio0 that pop and I don't know why... any ideas? here is my inmate : # insmod /bin/test/uio_ivshmem.ko uio_ivshmem: loading out-of-tree module taints kernel. uio_ivshmem 0000:00:0e.0: enabling device (0000 -> 0002) # lsmod Module Size Used by Tainted: G uio_ivshmem 16384 0 So the module is well loaded and I don't need to modprobe uio because it's already done in my kernel. 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/a132b6de-0483-4e2f-a5e8-56d8ed4eaae5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
