From owner-freebsd-arch@FreeBSD.ORG  Fri Jul  9 10:37:41 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AF36616A4CE
	for <arch@freebsd.org>; Fri,  9 Jul 2004 10:37:41 +0000 (GMT)
Received: from gw.Awfulhak.org (awfulhak.demon.co.uk [80.177.173.150])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E52A343D3F
	for <arch@freebsd.org>; Fri,  9 Jul 2004 10:37:32 +0000 (GMT)
	(envelope-from brian@Awfulhak.org)
Received: from mail.lan.Awfulhak.org (brian@dev.lan.Awfulhak.org [172.16.0.5])
	by gw.Awfulhak.org (8.12.11/8.12.11) with SMTP id i69AaC4N021506;
	Fri, 9 Jul 2004 11:36:23 +0100 (BST)
	(envelope-from brian@Awfulhak.org)
Date: Fri, 9 Jul 2004 11:36:12 +0100
From: Brian Somers <brian@Awfulhak.org>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Message-Id: <20040709113612.40e3a5c8@dev.lan.Awfulhak.org>
In-Reply-To: <6595.1089317548@critter.freebsd.dk>
References: <6595.1089317548@critter.freebsd.dk>
X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd5.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on gw.lan.Awfulhak.org
cc: arch@freebsd.org
Subject: Re: [RFC] kldunload -f argument.
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jul 2004 10:37:41 -0000

On Thu, 08 Jul 2004 22:12:28 +0200, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:
> In the new world order, a new event is introduced MOD_QUIESCE[1].
[.....]
> Comments ?

I would have thought a MOD_UNQUIESCE would be required too - maybe called
MOD_ACTIVATE (but I don't care much about the name).  It'd make things
more orthogonal.

When a module is loaded, it would be in a quiescent state allowing only a
MOD_UNLOAD or a MOD_ACTIVATE.  It's open for business between MOD_ACTIVATE
and MOD_QUIESCE.

The idea is that the user can be more active in getting rid of the active
module by QUIESCEing it, then running around murdering processes before
unloading it.

A couple of new flags could be added:

kldload -a module	don't activate it
kldunload -q module	only quiesce the module

kldstat would need to have a column to show whether a module was quiescent.

I'm not sure if kldunload should MOD_ACTIVATE if the MOD_QUIESCE succeeds
and the MOD_UNLOAD fails.... just an implementation detail I guess.

-- 
Brian <brian@Awfulhak.org>                        <brian@[uk.]FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !