Adam, Thanks once again for indulging me!
On Thursday, 21 April 2022 22:57:40 CEST Adam Lackorzynski wrote: > > On Tue Apr 19, 2022 at 01:20:30 +0200, Paul Boddie wrote: > > > > I still can't explain this. Doing some more invasive debugging in > > Task::sys_map (in src/kern/task.cpp) indicates that an explicit > > l4_task_map call will cause fpage_map (in src/kern/map_util.cpp) and > > subsequently mem_map (in src/kern/map_util-mem.cpp) and then map (in > > src/kern/map_util.cpp) to be called, attempting to map 0x400000 (with > > size 0x400000) in the original task at 0x1000000 in the recipient. This > > is reportedly successful. > > > > With page fault handling, the fpage_map, mem_map and map functions are > > called similarly, with the same supposedly successful outcome. But the > > page fault continues to occur with the same details, as if the mapping > > did not actually happen. I did wonder if it might be due to the original > > task not really having the pages it is trying to "export" actually mapped > > in itself (this being a potential pitfall when implementing dataspaces, > > in my experience), but this is not the case. > > > > I suppose I must be overlooking something else... > > Maybe it helps to share some code here? I suppose it might be best to condense this into an example that uses the basic L4Re APIs instead of my own libraries (that wrap those APIs), so as not to confuse things. I'll try and put that together tomorrow. Paul _______________________________________________ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de https://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
