seq counters to protect vcoremap changes
authorBarret Rhoden <brho@cs.berkeley.edu>
Thu, 18 Mar 2010 00:33:15 +0000 (17:33 -0700)
committerKevin Klues <klueska@cs.berkeley.edu>
Thu, 3 Nov 2011 00:35:39 +0000 (17:35 -0700)
commit6d0b636803fdde2dc13d3948934c265b4936faeb
treedc5a868a7c1242a4b67f6fe961d80088265cf5ab
parentd3ffafeb0e3822839e2a5e4ec4974b5a31abd2fa
seq counters to protect vcoremap changes

The kernel uses the seq counter when updating vcore-pcore mappings and
the number of vcores.  Userspace may need to check the counter when
trying to perform certain operations.

Also, this introduces a reference seq lock, that is an example of how to
use it.  It relies on a spinlock, which isn't that flexible.
kern/include/atomic.h
kern/include/ros/atomic.h [new file with mode: 0644]
kern/include/ros/notification.h
kern/include/ros/procinfo.h
kern/src/process.c
kern/src/resource.c