Date: Tue, 23 Mar 2010 17:27:45 -0400 From: John Baldwin <jhb@freebsd.org> To: "Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?=" <des@des.no> Cc: freebsd-hackers@freebsd.org, Dmitry Krivenok <krivenok.dmitry@gmail.com> Subject: Re: Strange behavior of kernel module (output terminated) Message-ID: <201003231727.45357.jhb@freebsd.org> In-Reply-To: <86zl1y4uiu.fsf@ds4.des.no> References: <da48cf211003230218n56794f0bs27eef860efc0da3e@mail.gmail.com> <201003231000.58961.jhb@freebsd.org> <86zl1y4uiu.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 23 March 2010 5:07:05 pm Dag-Erling Sm=C3=B8rgrav wrote: > John Baldwin <jhb@freebsd.org> writes: > > Dag-Erling Sm=C3=B8rgrav <des@des.no> writes: > > > I'm not sure it's such a good idea to use uprintf() here. The event > > > handler can be called in non-process context. > > If you are doing a kldload post-boot it is actually done from some sort= of=20 > > process context. We run module handlers synchronously from the kldload= (2)=20 > > syscall. >=20 > Sure, but not when the module is loaded by the boot loader (note "can", > not "will") =46or the purposes of writing a dummy test kld that you know you will load = via kldload it is ok though. :) =2D-=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201003231727.45357.jhb>