Re: [PATCH] call drv->shutdown at rmmod

From: Benjamin Herrenschmidt (benh_at_kernel.crashing.org)
Date: 08/15/03

  • Next message: Felipe Alfaro Solana: "Re: Trying to run 2.6.0-test3"
    To: Patrick Mochel <mochel@osdl.org>
    Date:	15 Aug 2003 10:51:08 +0200
    
    

    > You're assuming that a driver can always bring a device out a shutdown
    > state. That's one of the things we talked about at OLS, and the other half
    > of the justification behind such a feature, not just making sure the
    > device is queisced. Your argument against my suggestion are some of the
    > same arguments for a feature like you're introducing.

    There is a problem of semantics here. Is shutdown() supposed to shutdown
    the hardware device (ie. low power) or just the driver ? If yes, then
    it's duplicate of the PM callbacks. My understanding of the shutdown()
    callback is that it was more than "stop driver activity, put device into
    idle state" to prepare for a shutdown/reboot (though we do also sleep
    IDE drives in this case, but this is because of that nasty cache flush
    issue).

    The problem with kexec is just that. What it needs isn't low power devices,
    it needs device back in "idle" state, but if possible powered up (or at
    least in whatever state the driver found them on boot). The most important
    thing is to actually stop pending bus mastering activities.

    On PPC, we have a name for that which comes from Open Firmware (since we
    need to ask the firmware to stop bus mastering & idle devices the same way
    when we take over it and before we get control of the system memory) and
    it's called "quiesce".

    Ben.

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Felipe Alfaro Solana: "Re: Trying to run 2.6.0-test3"

    Relevant Pages

    • Re: random shut-downs
      ... The manual lists lan specifications a "NVIDIA Nforce 4 built-in Gigabit MAC ... with external Marvell PHY supports". ... Should I go ahead and roll lback the driver anyway? ... shutdown followed by several months of flawless operation. ...
      (alt.comp.hardware.pc-homebuilt)
    • Re: cannot logoff/shutdown properly
      ... I can shutdown properly with shutdown -h now. ... video driver that you use for Xorg. ... are at the graphical login screen, can you switch to a terminal with ... If I have a graphical login prompt and press CTRL + ALT + Back I can ...
      (Debian-User)
    • Re: Even more problems now!
      ... Interactions are almost never easy to spot. ... The combinations that cause system instability are very hard to run ... > restore because it doiesn't close properly, yet I think it's a driver ... I can't restore because I can't shutdown ...
      (microsoft.public.windowsxp.general)
    • Re: cannot logoff/shutdown properly
      ... And in recovery mode, I can shutdown properly with shutdown -h now. ... video driver that you use for Xorg. ... switch to a terminal without shutting down gdm. ...
      (Debian-User)
    • (Work-around) Cannot normally logoff, reboot, or shutdown remotely with ATI Radeon driver
      ... cannot normally logoff, reboot, or shutdown remotely with ATI Radeon ... The attempt to unknown %SYSTEMNAME% failed ... Roll back your video driver to 6.13.10.6153, ...
      (microsoft.public.windowsxp.work_remotely)