Strange behavior of kernel module (output terminated)
John Baldwin
jhb at freebsd.org
Tue Mar 23 21:27:58 UTC 2010
On Tuesday 23 March 2010 5:07:05 pm Dag-Erling Smørgrav wrote:
> John Baldwin <jhb at freebsd.org> writes:
> > Dag-Erling Smørgrav <des at 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
> > process context. We run module handlers synchronously from the kldload(2)
> > syscall.
>
> Sure, but not when the module is loaded by the boot loader (note "can",
> not "will")
For the purposes of writing a dummy test kld that you know you will load via
kldload it is ok though. :)
--
John Baldwin
More information about the freebsd-hackers
mailing list