Dario Faggioli writes ("Re: [PATCH 3/3] xen: Document
XEN_SYSCTL_CPUPOOL_OP_RMCPU anomalous EBUSY result"):
> However, a different return value for the super special case of
> temporary pinning override could maybe be selected. I'm having a look,
> and although I don't find one that could be seen as a perfect fit (that
> would be EBUSY, which is taken!), what about one of these:
>
> EEXIST 17 /* File exists */
> ENOTEMPTY 39 /* Directory not empty */
> EROFS 30 /* Read-only file system */
> ENOSPC 28 /* No space left on device */
Does the hypervisor currently use EAGAIN for anything ?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
