In a way, SCSI IDs and LUNs can change... When you do hot swapping of SCSI
devices (may well be more likely than interface cards).
The config manager defines suspend/resume operations on drivers (I actually
call them lock/unlock), which it calls when rebinding resources, but can also
be called by outside functions on particular devices. The idea is that when
locked, the driver doesn't communicate with it's device, so that I can safely
reconfigure it.
> Anyway, it might be a nice idea to have suspend/resume for LL SCSI drivers
> because then you could tell it to suspend everything for a few seconds,
> which means that hotplugging SCSI finally becomes possible; you need a 100%
> quiet bus for that to be safe.
This would certainly be possible... currently you could do something like the
following to suspend all your SCSI devices from user space (where scsidev*
stands for the real device ID):
cat <<EOF >/proc/cm/conf
a scsidev0 0
a scsidev1 0
a scsidev3 0
a scsidev7 0
EOF
And the following to resume them all:
cat <<EOF >/proc/cm/conf
a scsidev0 1
a scsidev1 1
a scsidev3 1
a scsidev7 1
EOF
David Howells
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html