public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Keiichiro Tokunaga <tokunaga.keiich@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Pcihpd-discuss] [RFC] New sysfs tree for hotplug
Date: Mon, 26 Apr 2004 16:55:55 -0700	[thread overview]
Message-ID: <20040426235555.GC24536@kroah.com> (raw)
In-Reply-To: <20040426145808.4ed2a7b0.tokunaga.keiich@jp.fujitsu.com>

On Mon, Apr 26, 2004 at 02:58:08PM +0900, Keiichiro Tokunaga wrote:
> 
> I think it depends on a hotplug driver that is invoked when writing to
> a "eject" file.  In the board case, a board hotplug driver (I'm making) 
> handles those CPUs, memory, and PCI slots on the board.  So my
> story for board hotplug is:
> 
>   - user checks/knows what resources are on the board (dependency)
>   - user writes to the "eject" file of the board properly (invocation)

Why not make a program that does all of this from userspace?  It would
turn off the proper CPUs, memory, and pci slots for a specific "board".
Otherwise you are going to have to either:
	- hook the current CPU, memory, and pci hotplug code to allow it
	  to be called from within the kernel
	- have your kernel code write to a the sysfs files from within
	  kernelspace.

Neither of which are acceptable things :(

thanks,

greg k-h

      reply	other threads:[~2004-04-27 15:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15  8:09 [RFC] New sysfs tree for hotplug Keiichiro Tokunaga
2004-04-16 22:34 ` [Pcihpd-discuss] " Greg KH
2004-04-16 23:39   ` Grant Grundler
2004-04-23 12:21     ` Keiichiro Tokunaga
2004-04-23 12:18   ` Keiichiro Tokunaga
2004-04-23 12:30     ` Matthew Wilcox
2004-04-23 13:52       ` Keiichiro Tokunaga
2004-04-23 12:47     ` Matthew Wilcox
2004-04-23 20:07     ` Greg KH
2004-04-26  5:58       ` Keiichiro Tokunaga
2004-04-26 23:55         ` Greg KH [this message]

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=20040426235555.GC24536@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tokunaga.keiich@jp.fujitsu.com \
    /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