From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 25 Mar 2005 21:19:34 +0100 From: "Devon H. O'Dell " To: 9fans@cse.psu.edu Subject: Re: [9fans] tsleep / timer questions Message-ID: <20050325201934.GC93332@smp500.sitetronics.com> References: <20050325183606.GA93332@smp500.sitetronics.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OBd5C1Lgu00Gd/Tn" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i Topicbox-Message-UUID: 2bc28a40-ead0-11e9-9d60-3106f5b1d025 --OBd5C1Lgu00Gd/Tn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 25, 2005 at 01:55:40PM -0500, jmk@plan9.bell-labs.com wrote: > >So, I thought a nifty solution would be to make use of the > >rendezvous stuff and call tsleep. But I don't understand how > >this should work. When the watchdog is enabled, I need to start > >some procedure that never returns. This would be easy in > >userland, where I could simply start another thread, but how do > >I do this in-kernel.=20 >=20 > that would be a kproc. look at some of the ether drivers, e.g. ether82557= ,c > which actually has a kproc called 'watchdog'. Aha! This does appear to be what I'm wanting to do. I saw the watchdog procedure in ether82557.c, but wasn't able to really figure it out. Searching for kproc makes more sense now :) Thanks for this tip. I'll finish this driver up tomorrow. --Devon --OBd5C1Lgu00Gd/Tn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCRHJWSkf3jVXOdl0RAmK8AKCXEJuFFSSm4JfVEN+OCD+CQX4g7wCdGufk 0DDdE2mJRh1r1FLADHHr0eo= =GsQL -----END PGP SIGNATURE----- --OBd5C1Lgu00Gd/Tn--