On 2016-11-09 14:37, Koehrer Mathias (ETAS/ESW5) wrote: > Hi all! > > Sorry for asking many questions... >> >> Did you check out the jailhouse branch? > No - I used the master branch. > > Now I switched to the jailhouse branch. > This looks better! > > The kernel module is loading properly, the device /dev/uio0 will be > generated. > # jailhouse cell create configs/ivshmem-demo.cell > # jailhouse cell load 1 inmates/demos/x86/ivshmem-demo.bin -a 0xf0000 > # lspci -s 0:f -v > 00:0f.0 RAM memory: Red Hat, Inc Inter-VM shared memory > Subsystem: Red Hat, Inc Inter-VM shared memory > Flags: bus master, fast devsel, latency 0 > Memory at de600000 (64-bit, non-prefetchable) [size=256] > Memory at de600100 (64-bit, non-prefetchable) [size=32] > Capabilities: [50] MSI-X: Enable+ Count=1 Masked- > Kernel driver in use: uio_ivshmem > > On the serial line I can see now lots of lines with > IVSHMEM: 00:0f.0 sending IRQ > > # grep ivshmem /proc/interrupts > 61: 0 0 0 0 0 0 > 0 IR-PCI-MSI 245760-edge ivshmem-config > > No interrupt can be seen! Is this expected? > > I tried a "uio_read /dev/uio0 2" (from tests/Interrupts/VM). > This blocks for ever. > Is this expected? > > Of course I wanted test the shared memory. For this I wrote a tiny program > that > is doing a 32byte mmap on /dev/uio0. > And this is working perfectly! > I can see the expected string > "Hello From IVSHMEM " >
Maybe not everything of the repo works, maybe we regressed - did you follow the README.jailhouse here? Jan -- Siemens AG, Corporate Technology, CT RDA ITP 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 jailhouse-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
