Hi,

It's been long enough that my memory could be wrong here, but I think that issue with the seL4SharedDataWithCaps issue was fixed. I once made an example of using this connector to do one way communication between a sender and receiver where both could be VM guests. https://github.com/kent-mcleod/camkes/blob/kent/aadl/apps/aadl-eventdata-dir.... The shared memory connectors and notification connection in that example should be a stable way for setting up shared memory and asynch signalling communication channels between two guests where you can control the access rights for each end of the connection in the Camkes connection configuration.

Kent.

On Mon, 27 Sep 2021, 18:36 , everton@ssrc.tii.ae wrote:

Hello seL4-devs,

I am working with seL4 running as a hypervisor with multiple VMs. I am aware of vchan (inactive) and VirtIO Net as mechanisms for inter-VM communication on top of seL4. However, I am looking to have a shared memory inter-VM communication between my VMs. Is there a well-maintained mechanism with shared memory and notifications for inter VM communication?

I have been trying to create a CAmkES example with dataport and I found out this "seL4SharedDataWithCaps" CAmkES connector for connecting dataport interfaces (https://github.com/seL4/global-components/issues/8): connection seL4SharedDataWithCaps sharedMem(from vm0.dummy_port, to vm0.buff, to vm1.buff);

The "to" side of the connection is supposed to give capabilities to both vmm0 and vmm1 (workaround proposed in the link above). How to use those capabilities to map "buff" into Linux guest address space?

Ideally, I would like to access that "buff" from Linux kernel without VMM intervention.

Thank you in advance. Best, Everton _______________________________________________ Devel mailing list -- devel@sel4.systems To unsubscribe send an email to devel-leave@sel4.systems