Date: Mon, 12 Sep 2011 14:27:03 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Marc L?rner <loerner@gmx.de> Cc: filippo.sironi@gmail.com, freebsd-hackers@freebsd.org Subject: Re: Re: Kernel timers infrastructure Message-ID: <20110912112703.GO17489@deviant.kiev.zoral.com.ua> In-Reply-To: <20110912094842.251380@gmx.net> References: <20110912094842.251380@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--8fdAbLF0bbg2TsS/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 12, 2011 at 11:48:42AM +0200, "Marc L?rner" wrote: > Hello, > what about changing order of callout_reset and uprintf? > And your timeout isn't 1minute, it's one second! >=20 > Regards, > Marc >=20 > >I already did that to ensure timer_event_handler would be called correct= ly. > > > >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 printin= g >"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 bei= ng called? > >>=20 The callouts are executed in the context that does not have the controlling terminal. uprintf(9) tries to use the ctty for output. Use printf(9) to get something on console. --8fdAbLF0bbg2TsS/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk5t7IcACgkQC3+MBN1Mb4iyzQCfbwFFVQnPHcMCwNWVsk+QKL7X dtUAoIL3v6D9FbH1yO0c0epPUovv3W0D =aUjh -----END PGP SIGNATURE----- --8fdAbLF0bbg2TsS/--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110912112703.GO17489>