mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keiichiro Tokunaga <kei@pia3.com>
To: Greg KH <greg@kroah.com>
Cc: Keiichiro Tokunaga <tokunaga.keiich@soft.fujitsu.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] New sysfs tree for hotplug
Date: Wed, 5 May 2004 02:52:22 +0900	[thread overview]
Message-ID: <20040505025222.70df6716.kei@pia3.com> (raw)

On Mon, 26 Apr 2004 16:55:55 -0700, Greg KH wrote:
> 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 :(

Actually I'm expecting to use the first option (hook) in the
current code of the board hotplug :)
The board hotplug is supposed to support "board attachment and
detachment".  That requires hardware manipulation.  So, the
hotplug code (at least, a part of the code) needs to live in
the kernel space.  Anyway, I would finish the first rough patches
in a few days and post them.  Please take a look at them to see
what I'm trying to do.

Thank you,
Kei

             reply	other threads:[~2004-05-04 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04 17:52 Keiichiro Tokunaga [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-15  8:09 Keiichiro Tokunaga

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=20040505025222.70df6716.kei@pia3.com \
    --to=kei@pia3.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tokunaga.keiich@soft.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

all inboxes | Powered by JetHome®