All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Joel Stanley <joel.stanley@au1.ibm.com>,
	Jeremy Kerr <jeremy.kerr@au1.ibm.com>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: kexec: device shutdown vs. remove
Date: Sun, 24 Jul 2016 23:13:08 +1000	[thread overview]
Message-ID: <1469365988.8568.255.camel@kernel.crashing.org> (raw)
In-Reply-To: <20160724051810.GA7663@roeck-us.net>

On Sat, 2016-07-23 at 22:18 -0700, Guenter Roeck wrote:
> I suspect that using (or depending on) the remove function may not be feasible
> anymore after the recent effort by Paul Gortmaker to make drivers explicitly
> non-modular if they are only configurable as boolean. In many cases, this
> involved dropping remove functions.

A lot of drivers we care about are modular. But maybe the right
approach is to do something like remove() if it exist and shutdown() if
it doesn't ? Or a new callback for kexec ? quiesce() ?

Cheers,
Ben.

  reply	other threads:[~2016-07-24 13:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23 20:51 kexec: device shutdown vs. remove Benjamin Herrenschmidt
2016-07-24  5:18 ` Guenter Roeck
2016-07-24 13:13   ` Benjamin Herrenschmidt [this message]
2016-07-24 21:36     ` Eric W. Biederman
2016-07-25  0:28       ` Benjamin Herrenschmidt
2016-07-24  5:24 ` Eric W. Biederman
2016-07-24 13:15   ` Benjamin Herrenschmidt
2016-07-24 21:35     ` Eric W. Biederman

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=1469365988.8568.255.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeremy.kerr@au1.ibm.com \
    --cc=joel.stanley@au1.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.