Re: [PATCH] PPC64 iSeries viodasd proc file

[Jeff Garzik]

Jeremy Katz wrote:
> And to be more constructive (after a discussion with Jeff this
> afternoon which is when I realized the reply didn't go out), what
> would be _very_ useful to have from a "probing disks" perspective
> would be a way to enumerate easily and simply from within sysfs the
> disks that are associated with a specific controller.  Not entirely
> sure where under sysfs this would go, but to be able to easily see
> that for block device type foo, I have disks disk0, disk1 and disk2. 
> The vio sysfs stuff actually works kind of nicely like this, but it
> would be more useful as a generic thing rather than not being able to
> depend on it.

And here's what I said to Jeremy over IRC as well...

I think it's perfectly reasonable to want a "driver -> registered 
devices" mapping.  That's what the installer appears to want, if I 
understand Jeremy correctly.

That will probably take some thought by the sysfs wizards, though, since 
drivers are registered on a per-bus basis...

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/