Skip to content

fix(linux): update inmate-ping demo logs for jailhouse #675

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sadik-smd merged 2 commits into from
Apr 16, 2026
+20 −12
Merged

fix(linux): update inmate-ping demo logs for jailhouse #675

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6c60446
fix(linux): update inmate-ping demo logs for jailhouse
sadik-smd Apr 16, 2026
704e6c5
fix(linux): update jailhouse linux and yocto sources
sadik-smd Apr 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 20 additions & 12 deletions source/linux/Foundational_Components/Hypervisor/Jailhouse.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,9 @@

The open source Jailhouse project from https://github.com/siemens/jailhouse is integrated in Yocto build environment.

- Yocto recipe (Scarthgap) for Jailhouse can be found here: `meta-ti <https://git.ti.com/cgit/arago-project/meta-ti/tree/meta-ti-extras/recipes-ti/jailhouse?h=scarthgap>`__.
- Yocto recipe (master) for Jailhouse can be found here: `meta-ti <https://git.ti.com/cgit/arago-project/meta-ti/tree/meta-ti-extras/recipes-ti/jailhouse?h=master>`__.

Check warning on line 53 in source/linux/Foundational_Components/Hypervisor/Jailhouse.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.PassiveVoice] 'be found' is passive voice. In general, use active voice. Consult the style guide for acceptable use of passive voice.

Raw Output:
{"message": "[RedHat.PassiveVoice] 'be found' is passive voice. In general, use active voice. Consult the style guide for acceptable use of passive voice.", "location": {"path": "source/linux/Foundational_Components/Hypervisor/Jailhouse.rst", "range": {"start": {"line": 53, "column": 43}}}, "severity": "INFO"}

Check warning on line 53 in source/linux/Foundational_Components/Hypervisor/Jailhouse.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.ConsciousLanguage] Use 'primary', 'source', 'initiator', 'requester', 'controller', 'host', 'director', or 'supplier' rather than 'master'.

Raw Output:
{"message": "[RedHat.ConsciousLanguage] Use 'primary', 'source', 'initiator', 'requester', 'controller', 'host', 'director', or 'supplier' rather than 'master'.", "location": {"path": "source/linux/Foundational_Components/Hypervisor/Jailhouse.rst", "range": {"start": {"line": 53, "column": 17}}}, "severity": "WARNING"}

- Jailhouse kernel patches are integrated with TI Linux Kernel (v6.12) and hosted here `Linux git.ti <https://git.ti.com/cgit/processor-sdk/linux/>`__. This repository includes Jailhouse module,
- Jailhouse kernel patches are integrated with TI Linux Kernel (v6.18) and hosted here `Linux git.ti <https://git.ti.com/cgit/processor-sdk/linux/>`__. This repository includes Jailhouse module,

Check warning on line 55 in source/linux/Foundational_Components/Hypervisor/Jailhouse.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.CaseSensitiveTerms] Use 'kernel' rather than 'Kernel'.

Raw Output:
{"message": "[RedHat.CaseSensitiveTerms] Use 'kernel' rather than 'Kernel'.", "location": {"path": "source/linux/Foundational_Components/Hypervisor/Jailhouse.rst", "range": {"start": {"line": 55, "column": 57}}}, "severity": "WARNING"}

Check warning on line 55 in source/linux/Foundational_Components/Hypervisor/Jailhouse.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.PassiveVoice] 'are integrated' is passive voice. In general, use active voice. Consult the style guide for acceptable use of passive voice.

Raw Output:
{"message": "[RedHat.PassiveVoice] 'are integrated' is passive voice. In general, use active voice. Consult the style guide for acceptable use of passive voice.", "location": {"path": "source/linux/Foundational_Components/Hypervisor/Jailhouse.rst", "range": {"start": {"line": 55, "column": 28}}}, "severity": "INFO"}
uio_ivshmem module for shared-memory and device tree changes for Jailhouse.

- U-Boot port for Jailhouse can be found here `U-Boot git.ti <https://git.ti.com/cgit/processor-sdk/u-boot/>`__. This repository contains the fix for error
Expand Down Expand Up @@ -264,7 +264,7 @@

am62lxx-evm login:

.. note::
.. note::
Jailhouse module is not autoloaded during boot-up. To load the jailhouse module
after boot, run following commands:

Expand Down Expand Up @@ -927,7 +927,7 @@
^C

You can see interrupts will be received in both inmate and root cell. Also, check
the values using
the values using

Check warning on line 930 in source/linux/Foundational_Components/Hypervisor/Jailhouse.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.Using] Use 'by using' instead of 'using' when it follows a noun for clarity and grammatical correctness.

Raw Output:
{"message": "[RedHat.Using] Use 'by using' instead of 'using' when it follows a noun for clarity and grammatical correctness.", "location": {"path": "source/linux/Foundational_Components/Hypervisor/Jailhouse.rst", "range": {"start": {"line": 930, "column": 5}}}, "severity": "WARNING"}

.. code-block:: console

Expand Down Expand Up @@ -981,32 +981,40 @@
=====================

This application demonstrates how to use IVSHMEM Ethernet to communicate with another
linux inmate cell in the Jailhouse hypervisor. Configure the eth1 in root cell and eth0 in
linux inmate cell in the Jailhouse hypervisor. Configure the eth2 in root cell and eth0 in

Check warning on line 984 in source/linux/Foundational_Components/Hypervisor/Jailhouse.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.CaseSensitiveTerms] Use 'Linux' rather than 'linux'.

Raw Output:
{"message": "[RedHat.CaseSensitiveTerms] Use 'Linux' rather than 'linux'.", "location": {"path": "source/linux/Foundational_Components/Hypervisor/Jailhouse.rst", "range": {"start": {"line": 984, "column": 1}}}, "severity": "WARNING"}
inmate cell and ping.

- In inmate cell

.. code-block:: console

root@<machine>: ifconfig enp0s1 192.168.0.2
root@<machine>: ip addr add 192.168.0.3 dev eth0
root@<machine>: ip link set eth0 up

- In root cell

.. code-block:: console

root@<machine>: ifconfig enP1p0s1 192.168.0.3
root@<machine>: ip addr add 192.168.0.2 dev eth2
root@<machine>: ip link set eth2 up

Ping enp0s1 using enP1p0s1 #ping 192.168.0.2 in root cell or ping enP1p0s1 using enp0s1
Ping eth0 using eth2 #ping 192.168.0.2 in root cell or ping eth2 using eth0

Check warning on line 1001 in source/linux/Foundational_Components/Hypervisor/Jailhouse.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.Using] Use 'by using' instead of 'using' when it follows a noun for clarity and grammatical correctness.

Raw Output:
{"message": "[RedHat.Using] Use 'by using' instead of 'using' when it follows a noun for clarity and grammatical correctness.", "location": {"path": "source/linux/Foundational_Components/Hypervisor/Jailhouse.rst", "range": {"start": {"line": 1001, "column": 6}}}, "severity": "WARNING"}
ping 192.168.0.3 in inmate cell.

Ex. ping to inmate cell from root cell

.. code-block:: console

root@<machine>: ping 192.168.0.2
PING 192.168.0.2 (192.168.0.2): 56 data bytes
64 bytes from 192.168.0.2: seq=0 ttl=64 time=0.707 ms
64 bytes from 192.168.0.2: seq=1 ttl=64 time=0.373 ms
root@<machine>:~# ping -c 4 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_seq=1 ttl=64 time=0.780 ms
64 bytes from 192.168.0.3: icmp_seq=2 ttl=64 time=0.413 ms
64 bytes from 192.168.0.3: icmp_seq=3 ttl=64 time=0.407 ms
64 bytes from 192.168.0.3: icmp_seq=4 ttl=64 time=0.415 ms

--- 192.168.0.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3057ms
rtt min/avg/max/mdev = 0.407/0.503/0.780/0.159 ms

Running Baremetal Demos
=======================
Expand Down
Loading