Re: [Xen-devel] Explicit return type for Hypercall

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 09/04/2009 13:28, "Tej" <bewith.tej@xxxxxxxxx> wrote:

>> The return code is ENOSYS, which is appropriate for an unimplemented
>> hypercall.
> 
> Still it could be misleading, because in case of kernel modules
> "module-uti"l packages overrides ENOSYS with message as "Kernel does
> not have module support"
> 
> an explicit return type could be useful here.

Separate from the kernel's return code you mean? Yes, you could certainly
define a new ioctl that returns the code in the command structure passed to
the ioctl, for example. I'd have no problem with that.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel