Hi Jan, On Tue, May 3, 2022 at 11:47 AM Lad, Prabhakar <[email protected]> wrote: > > Hi Jan, > > On Mon, May 2, 2022 at 9:30 PM Jan Kiszka <[email protected]> wrote: > > > > 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 > > > Thanks for the hint. > > > 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. > > > Great, I'll start with the latest enabling branch which you pointed to > and use it with the v0.12 release (I'll have to port my platform to > this though). And then later I consider either 5.10/4.19 kernel. > > > > > > >>> > > >>> 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 followed the jailhouse-images repo with the master branch and started with Linux first. For Linux it uses the jailhouse-enabling/5.10 branch [1] (commit id: eb6927f7eea77f823b96c0c22ad9d4a2d7ffdfce). In this kernel version the cpu_up/down api are static [2] due to which the build of jailhouse 0.12 is failing ( I tried to build for zynq platform just wanted to make sure build passes before porting my platform)
I looked at the kernel recipe and there aren't any patches which exports cpu_up/down api and nor do I see any patch in jailhouse_0.12.bb [3] which drops cpu_up/down api. Is there anything I'm missing here? [0] https://github.com/siemens/jailhouse-images/blob/master/recipes-kernel/linux/linux-jailhouse_5.10.inc#L17 [1] https://github.com/siemens/linux/tree/jailhouse-enabling/5.10 [2] https://github.com/siemens/linux/blob/jailhouse-enabling/5.10/kernel/cpu.c#L1253 [3] https://github.com/siemens/jailhouse-images/blob/master/recipes-jailhouse/jailhouse/jailhouse_0.12.bb Cheers, Prabhakar -- 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/CA%2BV-a8u0bPPZBk49twr9xuLNCPKV8isdSGTt%2BPj6mYV%3DDkh2OA%40mail.gmail.com.
