Date: Mon, 12 Sep 2011 11:34:50 +0200 From: Filippo Sironi <filippo.sironi@gmail.com> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-hackers@freebsd.org, Riccardo Cattaneo <cattaneo.riccardo@gmail.com> Subject: Re: Kernel timers infrastructure Message-ID: <4C14E323-F283-4EB1-82D9-E782A3340995@gmail.com> In-Reply-To: <CAJ-VmommBXcmn21z%2B=MrZcLLqOvmYU=x3E%2BiEm_wbTqoyQJbVA@mail.gmail.com> References: <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> <C0EB65E5-323A-4BB9-BCAA-4EF9E071E751@gmail.com> <CAJ-VmommBXcmn21z%2B=MrZcLLqOvmYU=x3E%2BiEm_wbTqoyQJbVA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I already did that to ensure timer_event_handler would be called = correctly. The result follows: freebsd# kldload ./timer.ko=20 timer_event_handler() with MOD_LOAD freebsd# kldunload ./timer.ko=20 timer_event_handler() with MOD_UNLOAD and I maintained the module load for about 1 minute so the timer = printing "Hello, World!" should have been run. Filippo On 12/set/2011, at 11:24, Adrian Chadd wrote: > How about adding some printfs() to the functions to ensure they're = being called? >=20 > Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C14E323-F283-4EB1-82D9-E782A3340995>