>
> Loadable does not imply that the root cell will get access to that region
> automatically. You also need a memory region in the root cell that covers
> this
> area. Access to the overlap will be controlled by the hypervisor safely,
> i.e. it
> will be taken from the root cell once the non-root cell starts to run.
>
It makes sense. I no longer have those unhandled traps related to RAM.
Now I'm having the follwing:
Unhandled data read at 0x1c2006c(4)
(...)
The debug console for bananapi is set like:
.debug_console = {
.address = 0x01c28000,
.size = 0x1000,
//.clock_reg = 0x01c2006c,
//.gate_nr = 16
//.divider = 0x0d,
.type = JAILHOUSE_CON_TYPE_8250,
.flags = JAILHOUSE_CON_ACCESS_MMIO |
JAILHOUSE_CON_REGDIST_4,
},
And for bananapi-gic-demo:
.console = {
.address = 0x01c29c00,
.clock_reg = 0x01c2006c,
.gate_nr = 23,
.divider = 0x0d,
.type = JAILHOUSE_CON_TYPE_8250,
.flags = JAILHOUSE_CON_ACCESS_MMIO |
JAILHOUSE_CON_REGDIST_4,
},
By the output and both configuration files, I suppose that that clock_reg
from bananapi-gic-demo is triggering the trap. Can you please explain how
this works and how I can manage to fix the situation?
--
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/23d3e368-b653-41e9-bafc-65fe0d6a2eb4%40googlegroups.com.
