Messages in this thread | | | Date | Mon, 26 Apr 2004 16:55:55 -0700 | From | Greg KH <> | Subject | Re: [Pcihpd-discuss] [RFC] New sysfs tree for hotplug |
| |
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 - 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/
| |