Hi Prabhakar, hi Chris, ok, now I understand your question last Thursday, Chris... ;)
On 02.05.22 21:37, Lad, Prabhakar wrote: > Hi Jan, > > On Mon, May 2, 2022 at 5:13 PM Jan Kiszka <[email protected]> wrote: >> >> On 27.04.22 15:19, Prabhakar Lad wrote: >>> Hi All, >>> >>> I recently tried to build the v0.12 tag with the upstream kernel >>> (v5.18-rc4) for emconrzg1h, but the build failed due to api changes >>> (cpu_up/cpu_down mainly). >> >> You want to use master or even next for very recent kernels. I haven't >> done a release in a too-long-while, so patches to account for kernel >> changes can only be found there. >> > I see. I came across the linux [0] tree which has > jailhouse-enabling/x.x branches. Is this a good starting point for > Linux? These branches merge Linux releases into the jailhouse kernel > which makes it a bit difficult to track the changes specifically made > to jailhouse. For example, for the 4.19 branch it's currently on > v4.19.81 whereas I plan to work on 4.19.198 which makes porting things > a bit difficult. Not at all: git log --no-merges --oneline v4.19.81..jailhouse-enabling/4.19 The 4.19 branch was retired a while ago, so rebasing over latest stable or merging that in would definitely be recommended. Actually, you likely want to check the latest enabling branch or [1] for updates since 4.19 was retired. > >>> >>> So I wanted to check what are the strict requirements for Linux and >>> u-boot as I plan to add new arm64 platform. >>> >>> Also is there any document/link that I can refer to porting on new platform? >> >> No written documents, but if you follow the commit history of >> https://github.com/siemens/jailhouse-images you can see how new targets >> were hooked up there (mostly Jailhouse-unrelated integration work). >> Jailhouse also does not depend on U-Boot, first of all only a working >> Linux / firmware integration, ideally from upstream. >> > I see the tf-a and u-boot do point to upstream with some tiny patches. > For example, for xilinx SDEI is enabled in TF-A. Is this required? > (I'm still reading through the docs so this nooby question!) SDEI is an optimization for interrupt delivery. Not needed, just faster. > >> Which SoC are you targeting? >> > My plan is to start with the Renesas RZ/V2L SoC (cortex a55 with > gic-v3), but will soon switch over to the Renesas RZ/G2M SoC (cortex > a57 with gic-400). > I see. The key steps in enabling will be - getting the patches applied to a tree that supports your board - writing a simple config (there is no "config create" on ARM, but you can more easily start with passing everything through) - jailhhouse config check - debugging remaining violations when starting Jailhouse - writing/adjusting non-root cell configs (for the pattern of recent enablings) Jan [1] https://git.kiszka.org/?p=linux.git;a=shortlog;h=refs/heads/queues/jailhouse -- 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/aebdee8e-4074-b223-2cbe-42564624e7f6%40siemens.com.
