Re: newbus integration of MOD_QUIESCE (was Re: cvs commit: src/sbin/kldunload kldunload.8 kldunload.c )

From: Robert Watson (rwatson_at_freebsd.org)
Date: 07/14/04

  • Next message: M. Warner Losh: "Re: newbus integration of MOD_QUIESCE" 
    Date: Tue, 13 Jul 2004 20:00:37 -0400 (EDT)
To: "M. Warner Losh" <imp@bsdimp.com>

    On Tue, 13 Jul 2004, M. Warner Losh wrote:

    > The nasty case I've come up with is what happens when the module is idle
    > (not busy), but becomes busy (not idle) after the MOD_QUIESCE call?
    > Right now newbus modules that receive a MOD_UNLOAD call attempt to
    > detach all instances of devices contained in that module. If I have a
    > way to poll the driver to see if it is busy (which is relatively easy to
    > implement), then if it becomes busy after the MOD_QUIESCE call, I get a
    > MOD_UNLOAD which would force instances to detach.

    So, it sounds like a couple of concepts are floating around:

    MOD_WEAKUNLOAD - Unload if you're not in use. I.e., unattached driver,
      unmounted file system, netgraph nodes that aren't instantiated, network
      protocol without any sockets, etc. Be harmlessly gone, but vetoed
      at a low cost.

    MOD_STRONGUNLOAD - Unload even though you're in use. Detach the driver,
      deadfs the file system, wither the geom, sever the sockets, etc. May
      cause disruption, but may also veto, depending on the subsystem,
      especially if the subsytem has no way to notify its consumers of
      impending doom. Can be vetoed, but try harder before vetoing. Some
      subsystems might always return EBUSY for this if there's really no way
      to express "undesirable departure" upwards.

    MOD_QUIESCE - Attempt MOD_WEAKUNLOAD, and if that fails, ask the module to
      start draining in some form. I'm a bit unclear on quite what's
      intended, but this seems to be less atomic notion than "unload, or
      don't" at various points on the spectrum. I.e., it kicks off a state
      transition in what is likely a slightly poorly defined state machine.
      Right now, the state machine is "Not loaded", "Loaded", and we use a
      lock to prevent intermediate states from colliding.

    MOD_SHUTDOWN - The system is shutting down, the module better do it too.
      Since there's no way to say "Um, no", most modules that don't know how
      to unload just ignore the event and in most cases it's harmless because
      the system state is toast shortly anyway.

    MOD_PANIC - Unload the module, regardless of the consequences.

    Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
    robert@fledge.watson.org Principal Research Scientist, McAfee Research

    _______________________________________________
    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"

  • Next message: M. Warner Losh: "Re: newbus integration of MOD_QUIESCE"

    Relevant Pages

    • Re: newbus integration of MOD_QUIESCE
      ... an unload request is treated as a blocking quiesce request. ... such as "State transition driver into 'shutting ... load overlap? ... it" may mean one thing for a driver, but something else for a file system. ...
      (freebsd-arch)
    • Re: kldunload DIAGNOSTIC idea...
      ... > instruction counter inside the range of pages we are going to unload. ... the main reason for wanting to unload the driver is to be able ... stuck somewhere, but apart from that, we're reasonably sure we can detach. ... detach the driver leaving it in memory. ...
      (freebsd-arch)
    • Re: Lots of easy questions about drivers/linking
      ... You can't replace a driver that is currently in use without invalidating the ... handles and then unload the driver. ... can create MULTIPLE XIP regions and using the BINFS file system unload the ...
      (microsoft.public.windowsce.platbuilder)
    • [PATCH 13/22] trivial: fix typo "on on" in multiple files
      ... -Before going on on how to attach, detach and unload the framebuffer console, an ... * The type of reading going on on this chip ...
      (Linux-Kernel)
    • Re: newbus integration of MOD_QUIESCE
      ... I.e., unattached driver, ... MOD_STRONGUNLOAD - Unload even though you're in use. ... deadfs the file system, wither the geom, sever the sockets, etc. ... transition in what is likely a slightly poorly defined state machine. ...
      (freebsd-arch)