Hi all
A friendly reminder that the seL4 developer hangout is on again next week.
Tue 11 Jun, 22:00 UTC.
For your local date and time please see https://sel4.systems/contact/.
Zoom link: https://unsw.zoom.us/j/82640784431
Birgit Brecknell
seL4 Foundation Project Coordinator
Sydney, Australia
M
Hello David,
On 2024-06-05 15:40, David Martin wrote:
that sounds like a real plan for me to test tomorrow :)
and if I'm not mistaken, inside each kernel now, the function
"seL4_Untyped_Retype" should be called twice (one on each core)
pointing to the same "free memory" declared previously so it
Thanks Indan,
that sounds like a real plan for me to test tomorrow :)
and if I'm not mistaken, inside each kernel now, the function
"seL4_Untyped_Retype" should be called twice (one on each core) pointing to the
same "free memory" declared previously so it can be used as shared memory by
both
Hello David,
On 2024-06-05 14:56, David Martin wrote:
If I'm not mistaken, that could be done using a chunk of memory
defined as device untyped and then used by each kernel (for my
tests, I'll use 2 harts) to write/read. --> Is that a good
understanding on how shared memory is suppose to be use
Hello,
Indeed I was able to have seL4 running on multiple harts.
Now I want to add an extra layer of shared memory (I'm not going to dig into
the notification mechanism for the moment). I just want to create a shared
memory region between 2 harts and check that both can have access to it.
If I'
