public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: akpm@osdl.org, Amit Gud <gud@eth.net>,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	Pavel Machek <pavel@ucw.cz>,
	linux-pci@atrey.karlin.mff.cuni.cz,
	". Linux-pm mailing list" <linux-pm@lists.osdl.org>,
	linux-kernel@vger.kernel.org, cramerj@intel.com
Subject: Re: [PATCH] PCI: Add pci shutdown ability
Date: Mon, 25 Apr 2005 16:11:33 -0400	[thread overview]
Message-ID: <20050425201133.GB3951@neo.rr.com> (raw)
In-Reply-To: <426D439D.6080705@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

On Mon, Apr 25, 2005 at 03:23:09PM -0400, Jeff Garzik wrote:
> Greg KH wrote:
> >Well it seems that people are starting to want to hook the reboot
> >notifier, or the device shutdown facility in order to properly shutdown
> >pci drivers to make kexec work nicer.
> >
> >So here's a patch for the PCI core that allows pci drivers to now just
> >add a "shutdown" notifier function that will be called when the system
> >is being shutdown.  It happens just after the reboot notifier happens,
> >and it should happen in the proper device tree order, so everyone should
> >be happy.
> >
> >Any objections to this patch?
> 
> Traditionally the proper place -has- been
> * the reboot notifier
> * the ->remove hook (hot unplug, and module remove)
> 
> which covers all the cases.
> 
> Add a ->shutdown hook is more of a hack.  If you want to introduce this 
> facility in a systematic way, introduce a 'kexec reboot' option which 
> walks the device tree and shuts down hardware.
> 
> ->shutdown is just a piecemeal, uncoordinated effort (uncoordinated in 
> the sense that driver shutdowns occur in an undefined order).
> 
> 	Jeff

I agree, though I think "->remove" may be more than we need.  Another
potential use of this might be to prepare devices just before removing power.

Thanks,
Adam

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2005-04-25 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44L0.0504251128070.5751-100000@iolanthe.rowland.org>
     [not found] ` <20050425182951.GA23209@kroah.com>
     [not found]   ` <SVLXCHCON1syWVLEFN00000099e@SVLXCHCON1.enterprise.veritas.com>
     [not found]     ` <20050425185113.GC23209@kroah.com>
     [not found]       ` <20050425190606.GA23763@kroah.com>
2005-04-25 20:08         ` [PATCH] PCI: Add pci shutdown ability Adam Belay
2005-04-25 20:19           ` Greg KH
2005-04-25 20:24             ` Adam Belay
     [not found]         ` <426D439D.6080705@pobox.com>
2005-04-25 20:11           ` Adam Belay [this message]
     [not found] <1114458325.983.17.camel@localhost.localdomain>
     [not found] ` <Pine.LNX.4.44L0.0504251609420.7408-100000@iolanthe.rowland.org>
     [not found]   ` <20050425145831.48f27edb.akpm@osdl.org>
     [not found]     ` <20050425221326.GC15366@redhat.com>
     [not found]       ` <20050425232330.GG27771@neo.rr.com>
     [not found]         ` <1114489949.7111.43.camel@gaston>
2005-04-26  6:23           ` Adam Belay
2005-04-26  9:16             ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050425201133.GB3951@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=akpm@osdl.org \
    --cc=cramerj@intel.com \
    --cc=gud@eth.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linux-pm@lists.osdl.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox