From: Linas Vepstas <linas@austin.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: userland hotplug tools
Date: Tue, 24 Aug 2004 17:15:30 +0000 [thread overview]
Message-ID: <20040824171530.GC14002@austin.ibm.com> (raw)
Hi,
On Tue, Aug 24, 2004 at 01:16:17PM -0500, Linda Xie was heard to remark:
>
> GregKH wrote:
> >They exist:
> >www.kroah.com/linux/hotplug
>
> >It's just the dumb ppc64 driver that breaks this tool, the last time I
> >tried it...
>
>
> Hi Greg,
>
> This tool won't work on pSeries platforms that support DLPAR. One of the
> reasons is that rpadlpar_io module creates "control" directory in
> /sys/bus/pci/slots.
> "control" is for adding/removing DLPAR I/O slots. It is not a PHP slot
> directory, so it doesn't have atribute files "power", "adapter",... the
> tool is looking for.
Either the 'control' subdirectory is in the wrong spot, or the tool
should be changed to ignore it. Greg?
> BTW, I downloaded 0.5 version src of the tool, modified man.c to use
> /sys/bus/pci/slots instead of /sys/bus/pci/hotplug_slots, modified
Maybe the ppc64 code uses the wrong name here? All the arches should use
the same name, and if 'hotplug_slots' is the 'official' name, then the
ppc64 code should change to use that name.
> slot.c to skip "control" dirctory and made other miscelaneous additions.
(yes, e.g. it won't build with newer versions of automake, etc.)
> Now I can use it to list all php slots and identify a php slots. I like
> the GUI environment this tool creates. I wanted to say thank you for
> creating a great tool.
Greg, should your tool be upgraded and maintained, or would you rather
deflect focus onto HAL? My biggest complaint is that most of my servers
are not graphical, so a graphical tool won't help, unless it can operate
distributed. By contrast, HAL, with hald looks like it might be able to
(???) run distributed.
> I am thinking about creating a GUI (based on your tool) that can be used
> on pSeries to do PHP add/remove/replace a PCI adapter. One thing I'd
> like to do is to integrate our php tool (drslot_chrp_pci) into the GUI.
Ugh. My gut reaction is to obsolete the drslot_chrp_pci tools, and
replace them by generic tools that would work on all arches.
--linas
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-08-24 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 17:15 Linas Vepstas [this message]
2004-08-24 20:07 ` userland hotplug tools Linda Xie
2004-08-24 22:38 ` Greg KH
2004-08-26 6:24 ` Greg KH
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=20040824171530.GC14002@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).