Rename EVENT_FALLBACK -> EVENT_SPAM_INDIR (XCC)
authorBarret Rhoden <brho@cs.berkeley.edu>
Mon, 3 Aug 2015 22:41:09 +0000 (18:41 -0400)
committerBarret Rhoden <brho@cs.berkeley.edu>
Mon, 28 Sep 2015 19:14:00 +0000 (15:14 -0400)
commit7c2005438f525542c456e9e8bd8115f7bb3ca0d4
treeb58efd810d487bbcb56761ba52be48a0dfccaf71
parent5f0db5e2ee17d15886e107cf38a8529de95380a2
Rename EVENT_FALLBACK -> EVENT_SPAM_INDIR (XCC)

"Fallback" was the original name for it, since it was the back-up plan
when a vcore was offline.  Once SPAM_PUBLIC came out, it was more clear
that it's really spamming an INDIR.  This came out of trying to explain
it: http://www.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-223.pdf.

Other than comments and the rename, the only functional change is the
removal of a printk.  For now, it's possible to have an INDIR without
spamming the INDIR.  I have a couple half-baked use cases for it.

Reinstall your kernel headers (make xcc-install-headers)
Documentation/async_events.txt
kern/include/ros/event.h
kern/src/event.c
user/benchutil/alarm.c
user/parlib/signal.c
user/parlib/uthread.c
user/parlib/vcore.c
user/pthread/pthread.c