On 04/12/2017 04:57 PM, Vitaly Andrianov wrote: > Hi Jan, > > Most of inmate configurations for ARM platform has RAM .virt_start = > 0x0. Is that a requirement? No, you can map it somewhere else as well, but then you also need to relocate your inmates (i.e., link them to the new address). > > A while ago I tried to make an inmate with .virt_start = 0x80000000 and > couldn't load the inmate. I wondering if that is an issue with my Because you have to change it's base address.
I wrote some off-tree patches that introduce inmate relocation, didn't send them to the list so far... Will do that in a couple of days. (BTW: Inmate relocation is pretty useful, because it allows to boot inmates without Jailhouse on bare-metal hardware, excellent for benchmarking or testing :-) ) Have a look at jailhouse/inmates/lib/arm/inmate.lds, 0x0 is hardcoded base address. Ralf > configuration or a Jailhouse limitation. I'm working on porting a AM572x > TI-RTOS based application to run as inmate and for me that is a big > limitation (if that is a real limitation but not my bug). A typical > TI-RTOS application has MMU enabled with identical one-to-one mapping of > the entire DDR (0x80000000-0xffffffff). And the binary entry is > somewhere at the beginning of that range. > > I saw couple of linux-demo configuration files with .virt_start != 0x0. > Does jailhouse care the .virt_start != 0x0 in some special way? Or I > just have some issue with my configuration? > > Thanks, > -Vitaly > -- 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]. For more options, visit https://groups.google.com/d/optout.
