On 15.01.23 15:01, Lad, Prabhakar wrote: > Hi Jan, > > On Wed, Jan 4, 2023 at 9:26 AM Jan Kiszka <[email protected]> wrote: >> >> On 02.01.23 21:55, Lad, Prabhakar wrote: >>> Hi Jan, >>> >>> On Mon, Jan 2, 2023 at 6:50 AM Jan Kiszka <[email protected]> wrote: >>>> >>>> Hi Prabhakar, >>>> >>>> On 29.11.22 15:29, Lad, Prabhakar wrote: >>>>> Hi Jan, >>>>> >>>>> On Sun, Nov 6, 2022 at 11:05 PM Lad Prabhakar >>>>> <[email protected]> wrote: >>>>>> >>>>>> Hi All, >>>>>> >>>>>> This patch series adds support for Renesas RZ/G2M SoC [0] (root cell >>>>>> config) and adds demo cell config for HopeRun HiHope RZ/G2M platform [1]. >>>>>> >>>>>> Changes apply on top of next branch [2] and the kernel used for testing >>>>>> is >>>>>> 5.10 (-cip) based on BSP-3.0.0 [3] release from Renesas. >>>>>> >>>>>> No changes from previous version sent to ML, just rebased on the next >>>>>> branch. >>>>>> >>>>>> [0] >>>>>> https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-ultra-high-performance-microprocessors-arm-cortex-a57-and-arm-cortex-a53-cpus-3d-graphics-and-4k >>>>>> [1] >>>>>> https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board#overview >>>>>> [2] https://github.com/siemens/jailhouse/tree/next (9391d30a) >>>>>> [3] https://github.com/renesas-rz/meta-renesas/tree/BSP-3.0.0 >>>>>> >>>>>> Cheers, >>>>>> Prabhakar >>>>>> >>>>>> Lad Prabhakar (3): >>>>>> renesas: Add SCIF support >>>>>> configs: arm64: Add root cell config for Renesas RZ/G2M SoC >>>>>> configs: arm64: Add demo cell config for Renesas RZ/G2M >>>>>> >>>>>> Documentation/debug-output.md | 1 + >>>>>> configs/arm64/dts/inmate-r8a774a1-hihope.dts | 228 ++++ >>>>>> configs/arm64/renesas-r8a774a1-linux-demo.c | 114 ++ >>>>>> configs/arm64/renesas-r8a774a1.c | 1134 +++++++++++++++++ >>>>>> hypervisor/arch/arm-common/Kbuild | 2 +- >>>>>> hypervisor/arch/arm-common/dbg-write.c | 2 + >>>>>> hypervisor/arch/arm-common/include/asm/uart.h | 2 +- >>>>>> hypervisor/arch/arm-common/uart-scif.c | 44 + >>>>>> include/jailhouse/console.h | 1 + >>>>>> inmates/lib/arm-common/Makefile.lib | 2 +- >>>>>> inmates/lib/arm-common/uart-scif.c | 65 + >>>>>> inmates/lib/arm-common/uart.c | 2 + >>>>>> 12 files changed, 1594 insertions(+), 3 deletions(-) >>>>>> create mode 100644 configs/arm64/dts/inmate-r8a774a1-hihope.dts >>>>>> create mode 100644 configs/arm64/renesas-r8a774a1-linux-demo.c >>>>>> create mode 100644 configs/arm64/renesas-r8a774a1.c >>>>>> create mode 100644 hypervisor/arch/arm-common/uart-scif.c >>>>>> create mode 100644 inmates/lib/arm-common/uart-scif.c >>>>>> >>>>> Gentle ping. >>>>> >>>> >>>> Sorry for letting you wait /that/ long: >>>> >>>> Patches look good except that they are missing ivshmem support and an >>>> inmate-demo cell. You should have a demo and a networking ivshmem device >>>> in the root and the linux cell, the inmate demo needs just the demo >>>> device. Check out other boards for the required pattern, e.g. the rpi4. >>>> >>> OK, I will get this in. Can you please point me to any docs on testing >>> networking ivshmem device if any. >>> >> >> Once both cells are configured, you can assigned IPs to both network >> devices, ping them or do ssh from the root cell to the non-root one. See >> jailhouse-images for a pre-integration of such a setup, e.g. that of >> qemu-arm64. I've just pushed a new version that builds here into the >> 'next' branch (still needs more work). >> > I had couple of question, > 1: For the pci_mmconfig_base should this PA? (If PA what range should > be ideally selected and should this be reserved in the root cell?)
If you have a emulated PCI host controller (which is the common case on non-x86), this address should be free in the physical range of the target. > 2: How do we calculate vpci_irq_base? There have to be up to 4 unused (but GIC-wise supported) interrupts at that base. > 3: When do we need to configure the stream_ids? Only if you configure an SMMU. Do you have one and plan to use is? > 4: For the IVSHMEM 00:00.0 (demo) the PA range should this be reserved > in the root cell? The PA should be physical RAM that is otherwise not used by any cell or the hypervisor itself. > 5: And similarly for IVSHMEM (networking) the PA range should this be > reserved in the root cell? Same story. Jan -- Siemens AG, Technology Competence Center Embedded Linux -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/e26f0792-ec58-9edd-1bce-dcc8a6df0382%40siemens.com.
