Use our interrupt infrastructure to handle the clock interrupt, but
commit1130c186b568d5ce3a450c9906880f782e8e055d
authorMatthew Dillon <dillon@dragonflybsd.org>
Tue, 9 Jan 2007 00:49:03 +0000 (9 00:49 +0000)
committerMatthew Dillon <dillon@dragonflybsd.org>
Tue, 9 Jan 2007 00:49:03 +0000 (9 00:49 +0000)
treee28a7967f49732545e77295986550a59ee760422
parentcb118784aa8487783d1254b746e0587e5b861bba
Use our interrupt infrastructure to handle the clock interrupt, but
for the moment we have no common 'hard interrupt' (i.e. signal) core
so do the critical section check manually.
sys/platform/vkernel/platform/machintr.c
sys/platform/vkernel/platform/systimer.c