Re: kldunload DIAGNOSTIC idea...
From: Brian Fundakowski Feldman (green_at_freebsd.org)
Date: 07/20/04
- Previous message: Poul-Henning Kamp: "kldunload DIAGNOSTIC idea..."
- In reply to: Poul-Henning Kamp: "kldunload DIAGNOSTIC idea..."
- Next in thread: Poul-Henning Kamp: "Re: kldunload DIAGNOSTIC idea..."
- Reply: Poul-Henning Kamp: "Re: kldunload DIAGNOSTIC idea..."
- Reply: Scott Long: "Re: kldunload DIAGNOSTIC idea..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 20 Jul 2004 14:32:13 -0400 To: Poul-Henning Kamp <phk@phk.freebsd.dk>
On Tue, Jul 20, 2004 at 08:20:23PM +0200, Poul-Henning Kamp wrote:
>
> I'm pulling hair out trying to make it guaranteed safe to unload device
> driver modules, and the major pain here is to make sure there is no
> thread stuck somewhere inside the code.
>
> That gave me the idea for a simple little DIAGNOSTIC check for kldunload:
> run through the proc/thread table and look for any thread with an
> instruction counter inside the range of pages we are going to unload.
>
> Any takers ?
You mean any thread with a stack trace that includes an instruction
counter inside those pages, don't you?
-- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ _______________________________________________ freebsd-arch@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Poul-Henning Kamp: "kldunload DIAGNOSTIC idea..."
- In reply to: Poul-Henning Kamp: "kldunload DIAGNOSTIC idea..."
- Next in thread: Poul-Henning Kamp: "Re: kldunload DIAGNOSTIC idea..."
- Reply: Poul-Henning Kamp: "Re: kldunload DIAGNOSTIC idea..."
- Reply: Scott Long: "Re: kldunload DIAGNOSTIC idea..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|