Date: Wed, 21 Jan 2009 17:39:08 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Andriy Gapon <avg@icyb.net.ua> Cc: freebsd-hackers@freebsd.org Subject: Re: MOD_UNLOAD and driver with cdev Message-ID: <20090121153908.GO58517@deviant.kiev.zoral.com.ua> In-Reply-To: <49773938.5010000@icyb.net.ua> References: <49773938.5010000@icyb.net.ua>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Wed, Jan 21, 2009 at 05:03:20PM +0200, Andriy Gapon wrote: > > Do I need to code for MOD_UNLOAD for driver module that also creates a cdev? > I see in the current code that one strategy is to simply call > destroy_dev(). I guess detach routines are called automatically and > destroy_dev can be done there as well.. What are the detach routines ? Do you mean newbus device detach ? Yes, the usual strategy is to call destroy_dev from unload handler. > > Is it reasonable to refuse unload if cdev is in use (in MOD_QUIESCE)? > How to check for that best? This cannot be checked race-free. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkl3QZwACgkQC3+MBN1Mb4il9QCcDgl+fvM6v2My/B5VVwzfduiR wGYAnjqq815Ce1WShNgU9gM3GzUEzUuw =Kw/R -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090121153908.GO58517>