Use our interrupt infrastructure to handle the clock interrupt, but
commit2dbe04632e9d7a5f84d6bb1da3eb7ef61f493010
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)
treecb47fe353f1951f7f4f9a1ec46dee2a841870b15
parent71c149a8f6d79f257d31abe920dccdf9d37ec37f
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