Dear Ralf,
2017-02-28 22:27 GMT+01:00 Ralf Ramsauer <[email protected]>:
> > > + /* RAM */ {
> > > + .phys_start = 0x17bfe0000,
> > shouldn't this rather be 0x17bff0000 in order to not introduce memory
> > holes? The HV start at 0x17c000000, and we don't have an shmem region
> > before the hypervisor's region.
> >
> >
> > Right.
> > The actual reason is that we are using such "hole" for an additional
> > region for sharing data between Linux and the RTOS,
> > and we didn't put such region into the config because we thought that it
> > was too specific.
> Ah, ok, I see, I was just wondering.
> > At the same time we thought that a memory hole could ease the debugging.
> Hmm, all other inmates are typically physically located right before the
> hypervisor, without holes (except the ones that have an IVSHMEM region).
>
> Can't we just place the inmate close to the hypervisor, and you place
> you shared memory region before the inmate? This approach should work
> for mainline as well as for your downstream branch.
>
Of course. I will send a new patchset in the next days.
Best regards,
Claudio
--
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.
