On 04/12/2017 11:11 AM, Jan Kiszka wrote:
Hi Vitaly,

On 2017-04-12 16:57, Vitaly Andrianov wrote:
Hi Jan,

Most of inmate configurations for ARM platform has RAM .virt_start =
0x0. Is that a requirement?

The reset vector is 0x0, so there should be some code at that location
when the inmate wants to start. Can be a fraction of the RAM, though,
just to carry some bootstrap page if you prefer.


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
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?

In case of Linux, you can see that there is always at least one small
region at virt_start 0 as well. That is were our linux-loader.bin is
put. It does not need identity mapping as it does not do any DMA.

Jan

Hi Jan,

Sorry, I'm confused. From Ralf's reply I understood that I can link my inmate to not zero address (in my case I use beginning of the DDR - 0x80000000) and set .virt_start to the same address. Also I placed vector table to the beginning of the image, so the entry point is the start of the binary. I understood that configuration should work.

From your reply I understood that I have to make at least a small section located at the virt_start = 0x0 address. Is that really necessary?

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.

Reply via email to