On 27/05/20 7:18 pm, Jan Kiszka wrote:
On 27.05.20 15:28, Nikhil Devshatwar wrote:


On 27/05/20 6:41 pm, Jan Kiszka wrote:
On 27.05.20 14:32, nikhil...@ti.com wrote:
From: Nikhil Devshatwar <nikhil...@ti.com>

Number of peers available on a platform is different.
Do not hard code the target peer_id used for interrupt.
Parse this from the command line argument.

This de-couples the dependency between number of peers.
ivshmem-demo can be run to communicate with desired target

No command line, please. We can do (<ID> + 1) % <Maximum Peers> as
target. All that is accessible via the register interface. But then all


I believe, as of now, only root cell can communicate with peer1, peer2,
etc. Non root cells cannot communicate with each other.
Please correct me if I am wrong.


Not all targets have been enabled for the "triangle" setup, but if you
look at qemu-arm64, e.g., you can see that pattern.

(id + 1)% max_num_peers     logic won't work for a 3peer scenario where
root cell app(id=0) wants to communicate with baremetal(id=2)
e.g. qemu-arm64 has these ids.


Then we need to adjust that. It doesn't matter who sends whom, just
everyone should send something and everyone should receive something in
the end.


In QEMU, root (id = 0) linux-demo(id = 1) and baremetal(id = 2)

0 should be able to to 1 and 2
Here you should choose if you want to communicate with baremetal or linux-demo. There is no way this can be automatically figured out.
That's why I added an argument.

Regards,
Nikhil D



demos should be updated, ie. also the bare-metal version.

Sure, can I hard code the baremetal to always communicate with root cell
(ivshmem id = 0)


No, all demos should then use the same pattern from above, consistently.
Luckily, only two implementations exits (bare metal + linux app), and
that for all archs.

Jan


--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/c32c3837-b0d6-c48e-221a-4202923d945f%40ti.com.

Reply via email to