Lines Matching +full:app +full:- +full:path
1 .. zephyr:code-sample:: ipm-ivshmem
3 :relevant-api: ipm_interface
5 Implement inter-processor mailbox (IPM) over IVSHMEM (Inter-VM shared memory)
12 ivshmem-server needs to be available and running. The server is available in
13 Zephyr SDK or pre-built in some distributions. Otherwise, it is available in
16 ivshmem-client needs to be available as it is employed in this sample as an
17 external application. The same conditions of ivshmem-server apply to the
18 ivshmem-server, as it is also available via QEMU.
22 #. The ivshmem-server utility for QEMU can be found into the Zephyr SDK
24 ``/path/to/your/zephyr-sdk/zephyr-<version>/sysroots/x86_64-pokysdk-linux/usr/xilinx/bin/``
26 #. You may also find ivshmem-client utility, it can be useful to check if everything works
29 #. Run ivshmem-server. For the ivshmem-server, both number of vectors and
30 shared memory size are decided at run-time (when the server is executed).
32 decided at compile-time and run-time, respectively. For Arm64 we use
35 .. code-block:: console
38 $ sudo ivshmem-server -n 2
44 .. code-block:: console
57 .. code-block:: console
59 $ mkdir -p path/to/instance_1
63 .. code-block:: console
65 $ mkdir -p path/to/instance_2
68 to test this sample, so append the option ``-d path/to/instance_1`` and
69 on the other terminal window do the same, that is it ``-d path/to/instance_2``
71 .. zephyr-app-commands::
72 :zephyr-app: samples/drivers/ipm/ipm_ivshmem
78 by ``-d path/to/instance_x`` where x is 1 or 2 depending on the
81 .. zephyr-app-commands::
82 :zephyr-app: samples/drivers/ipm/ipm_ivshmem
91 followed by the destination peer-id, to get the peer-id destination
94 .. code-block:: console
96 *** Booting Zephyr OS build zephyr-v3.4.0-974-g7fba7d395750 ***
106 For example one of the instances has the peer-id 12, so go the other
108 by this peer-id:
110 .. code-block:: console
112 *** Booting Zephyr OS build zephyr-v3.4.0-974-g7fba7d395750 ***
125 .. code-block:: console