New vcoremap in procinfo
authorBarret Rhoden <brho@cs.berkeley.edu>
Sat, 13 Mar 2010 02:23:01 +0000 (18:23 -0800)
committerKevin Klues <klueska@cs.berkeley.edu>
Thu, 3 Nov 2011 00:35:39 +0000 (17:35 -0700)
commit369e043facca929a58797e8b3c3c14756198ef8d
treeaa7d5788ed1e450268f59f203d6308df1e3ca3c8
parentc510604762b5b423ac9f7f24ee1b2be8f7e8cf1d
New vcoremap in procinfo

The vcoremap contains new items (not just pcoreids), and it is exposed
via procinfo (along with num_vcores).  -1 no longer means invalid
either; it's more clear to have a bool for that.  Eventually we'll
signal userspace that the vcoremap (or a pcoremap) is being changed with
the seq_ctr.

If it turns out we are exposing too much info, we can move the vcoremap
back and push updates, but I'd rather not do that.
12 files changed:
kern/arch/i686/env.c
kern/include/env.h
kern/include/process.h
kern/include/ros/notification.h
kern/include/ros/procdata.h
kern/include/ros/procinfo.h
kern/src/elf.c
kern/src/env.c
kern/src/manager.c
kern/src/process.c
kern/src/resource.c
kern/src/syscall.c