Skip to content

Commit 6c60446

Browse files
committed
fix(linux): update inmate-ping demo logs for jailhouse
jailhouse inmate ping logs update with respect to the ethernet interfaces changed in both root cell and inmate cell. Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
1 parent 6b148e1 commit 6c60446

1 file changed

Lines changed: 18 additions & 10 deletions

File tree

source/linux/Foundational_Components/Hypervisor/Jailhouse.rst

Lines changed: 18 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -264,7 +264,7 @@ on the EVM then power on the board, the following logs can be observed on the te
264264
265265
am62lxx-evm login:
266266
267-
.. note::
267+
.. note::
268268
Jailhouse module is not autoloaded during boot-up. To load the jailhouse module
269269
after boot, run following commands:
270270

@@ -927,7 +927,7 @@ Run ivshmem-demo on both root and inmate cell
927927
^C
928928
929929
You can see interrupts will be received in both inmate and root cell. Also, check
930-
the values using
930+
the values using
931931

932932
.. code-block:: console
933933
@@ -981,32 +981,40 @@ Running Ethernet Demo
981981
=====================
982982

983983
This application demonstrates how to use IVSHMEM Ethernet to communicate with another
984-
linux inmate cell in the Jailhouse hypervisor. Configure the eth1 in root cell and eth0 in
984+
linux inmate cell in the Jailhouse hypervisor. Configure the eth2 in root cell and eth0 in
985985
inmate cell and ping.
986986

987987
- In inmate cell
988988

989989
.. code-block:: console
990990
991-
root@<machine>: ifconfig enp0s1 192.168.0.2
991+
root@<machine>: ip addr add 192.168.0.3 dev eth0
992+
root@<machine>: ip link set eth0 up
992993
993994
- In root cell
994995

995996
.. code-block:: console
996997
997-
root@<machine>: ifconfig enP1p0s1 192.168.0.3
998+
root@<machine>: ip addr add 192.168.0.2 dev eth2
999+
root@<machine>: ip link set eth2 up
9981000
999-
Ping enp0s1 using enP1p0s1 #ping 192.168.0.2 in root cell or ping enP1p0s1 using enp0s1
1001+
Ping eth0 using eth2 #ping 192.168.0.2 in root cell or ping eth2 using eth0
10001002
ping 192.168.0.3 in inmate cell.
10011003

10021004
Ex. ping to inmate cell from root cell
10031005

10041006
.. code-block:: console
10051007
1006-
root@<machine>: ping 192.168.0.2
1007-
PING 192.168.0.2 (192.168.0.2): 56 data bytes
1008-
64 bytes from 192.168.0.2: seq=0 ttl=64 time=0.707 ms
1009-
64 bytes from 192.168.0.2: seq=1 ttl=64 time=0.373 ms
1008+
root@<machine>:~# ping -c 4 192.168.0.3
1009+
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
1010+
64 bytes from 192.168.0.3: icmp_seq=1 ttl=64 time=0.780 ms
1011+
64 bytes from 192.168.0.3: icmp_seq=2 ttl=64 time=0.413 ms
1012+
64 bytes from 192.168.0.3: icmp_seq=3 ttl=64 time=0.407 ms
1013+
64 bytes from 192.168.0.3: icmp_seq=4 ttl=64 time=0.415 ms
1014+
1015+
--- 192.168.0.3 ping statistics ---
1016+
4 packets transmitted, 4 received, 0% packet loss, time 3057ms
1017+
rtt min/avg/max/mdev = 0.407/0.503/0.780/0.159 ms
10101018
10111019
Running Baremetal Demos
10121020
=======================

0 commit comments

Comments
 (0)