PSARC/2008/146 sgen(7D) Multiple Opens

[Eric Schrock]

For the record, we discussed this issue offline and determined that the
current behavior, while leaving something to be desired, is valid given
the use of the driver (userland pass-through).  Any changes to this
behavior are beyond the scope of this particular case.

- Eric

On Mon, Feb 25, 2008 at 02:26:44PM -0800, Garrett D'Amore wrote:
> As far as Suspend/Resume goes, the "correct" behavior, IMO, is that 
> open() "blocks" if it is called while the device is suspended, at least 
> if it needs to access the device.  (If open() doesn't need to touch the 
> hardware, but only updates soft state, then there is no reason to 
> prohibit it from running normally even if the device is technically 
> suspended.)
> 
> Put another way, apart from observations involving the time it takes to 
> run, I do not believe that there should be any noticeably different 
> behavior to consumers of a device that supports suspend/resume.
> 
> A separate EIO return value seems like a poor choice to me.
> 
> Please feel free to contact me offline if you desire further feedback or 
> discussion pertaining to S/R of devices.

--
Eric Schrock, Fishworks                        http://blogs.sun.com/eschrock