On Tue, 16 Sep 2014, Darren Hart wrote:
> - When reading and writing sysfs device attribute files, avoid dependency
> on specific error codes wherever possible. This minimizes coupling to
> the error handling implemementation within the kernel.
>
> In general, failures to read or write sysfs device attributes shall
> propogate errors wherever possible. Common errors include, but are not
> limited to:
>
> -EIO: The read or store operation is not supported, typically returned by
> the sysfs system itself if the read or store pointer is NULL.
>
> -ENXIO: The read or store operation failed
from errno(3):
EIO Input/output error (POSIX.1)
ENXIO No such device or address (POSIX.1)
It makes sense to retry EIO. ENXIO means there's nobody listening at the
time, and isn't usually retried.
The device-based interfaces get it right. A typical example is the
cpu-based devices, where ENXIO means "no such processor", while EIO means
"whatever you're trying to do failed", so a MSR read would return ENXIO if
the processor core is offline/doesn't exist, and EIO if the processor core
is there, but raised a #GP when the MSR read was attempted.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
