Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Sep 2011 08:19:04 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-hackers@freebsd.org
Cc:        Filippo Sironi <filippo.sironi@gmail.com>, Riccardo Cattaneo <cattaneo.riccardo@gmail.com>
Subject:   Re: Kernel timers infrastructure
Message-ID:  <201109120819.05109.jhb@freebsd.org>
In-Reply-To: <C0EB65E5-323A-4BB9-BCAA-4EF9E071E751@gmail.com>
References:  <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> <C0EB65E5-323A-4BB9-BCAA-4EF9E071E751@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, September 12, 2011 4:42:40 am Filippo Sironi wrote:
> This is what I wrote for FreeBSD 7.2 and it does not work:

callout_reset() is always going to return false here as you are never 
rescheduling an existing callout (it is either idle or has already fired each 
time you invoke callout_reset()).

However, you are calling uprintf() from the kernel softclock thread and that 
thread is not attached to your tty, so the uprintf() is going to nowhere.

Just use a regular printf and you will get your "Hello, World!" output once a 
second.

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201109120819.05109.jhb>