On 28.05.19 15:22, [email protected] wrote: > 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... > > 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 >
A typical issue is when there are two DMAR units, and the system sees the ivshmem device behind a different one than it is configured. But your system only has one unit. The next thing to check is where the MMIO resource of the ivshmem device ends up (lspci -v) compared to what region you map directly into the guest. That MMIO resource must not be mapped, it needs to be interceptable by Jailhouse. And then comes printk debugging: instrument the doorbell register handling down to where the interrupt is sent out as IPI to see where the transmission bails out. > > 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? > There is no limitation to root cells. 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/5c3a0b70-c047-274b-a78d-3e0d8a4a02a6%40siemens.com. For more options, visit https://groups.google.com/d/optout.
