> I believe the culprit is that the added device goes in the next > free minor nunmber. An easy way to make the process deterministic > could be to specify both parameters when adding a device (like we > add CP-own volumes) and complain when the entry is not free.
Yes! This is just as important on LPAR as on VM. Both have different ways of using dynamic I/O reconfig, but both modes need it supported by the "guest" op sys. > And while we're at it, it would be helpful to have a userspace > program to do it and return a completion code (and maybe even do > the CP LINK as well). I would disagree about the CP LINK part. More significantly, this may be an ioctl() type of call. Punching strings to /proc pseudo files is fine, but not always best.
