On 26.06.19 20:06, 'Vitaly Andrianov' via Jailhouse wrote:
On 06/26/2019 07:38 AM, Vitaly Andrianov wrote:
On 06/25/2019 11:50 AM, Jan Kiszka wrote:
On 24.06.19 23:44, 'Vitaly Andrianov' via Jailhouse wrote:
[skip]
Check - when in doubt via instrumenting the calls - if the regions at the
faulting addresses are actually mapped -> arch_map_memory_region.
arch_map_memory_region 0x48020000/0x48020000/0x00001000 0x00000093
arch_map_memory_region 0x48424000/0x48424000/0x00001000 0x00000093
arch_map_memory_region 0x48826000/0x48826000/0x00001000 0x00000093
arch_map_memory_region 0x4a000000/0x4a000000/0x00e00000 0x00000093
arch_map_memory_region 0xee000000/0x00000000/0x00800000 0x00000047
arch_map_memory_region 0x00000000/0x80000000/0x00001000 0x00000023
Created cell "AM57XX-EVM-timer8-demo"
Page pool usage after cell creation: mem 62/4073, remap 6/131072
Each region from the am57xx-evm-ti-app.c are mapped.
Using the CCS debugger I started the inmate and paused it immediately on
inmate_main() entrance and checked memory referenced by TTBR0 register.
TTBR0 = 0x00017000
Is that TTBR0_EL1 or EL2?
0x0000017000 00019003 00000000 00000000 00000000 0001A003 00000000 00000000
00000000
Looks like only 2 last regions are mapped (application memory and communication
regions)
None of the peripherals regions are mapped, or may be I don't see them.
If we are talking about TTBR0_EL1: Since your old version, imates gained MMU
support. That means you now need to map additional memory (beyond the first 2M
or so) into the guest's page table.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate 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/828e6eff-d11c-7364-797f-623d4d41eb4f%40siemens.com.
For more options, visit https://groups.google.com/d/optout.
