Re: Why need a lock in memory/capability map
Yuxin Ren <[email protected]>
| Newsgroups | gmane.comp.micro-kernel.l4.devel |
|---|---|
| Message-ID | <CAAKbDreY3w+RFPrgX5h2YkF-h-XYxncpmGpeVmN48Uzs+EvM6g@mail.gmail.com> |
This makes more sense. But could you explain in a litter more detail? What data structures are protected? Task struture or something else? Thank you very much. Yuxin On Mon, Jul 21, 2014 at 5:34 AM, Adam Lackorzynski < [email protected]> wrote: > On Fri Jul 18, 2014 at 18:34:31 -0400, Yuxin Ren wrote: > > I note that when a thread does memory or capability mapping, both over > > system call and IPC, it needs take a lock, which is the existence_lock of > > target task. I cannot understand it needs take a per task, as cap/page > > table are per thread. > > What data does this lock to protect? > > Memory as well as caps are per task, so the lock makes sure that the > task does not disappear while an operation is in progress. > > > Adam > -- > Adam [email protected] > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > _______________________________________________ > l4-hackers mailing list > [email protected] > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > _______________________________________________ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers