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

To:	Tej <bewith.tej@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] Explicit return type for Hypercall
From:	Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date:	Thu, 09 Apr 2009 12:20:35 +0100
Cc:
Delivery-date:	Thu, 09 Apr 2009 04:21:06 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<f1c9d250904090338j28b44cffh42ade9161eb2ddf0@xxxxxxxxxxxxxx>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	Acm4/3xc+mQh2KDfTki637gZ6NingwABbdWi
Thread-topic:	[Xen-devel] Explicit return type for Hypercall
User-agent:	Microsoft-Entourage/12.15.0.081119

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

> eg in GCOV case, I issued hypercall, when there is no corresponding
> entry in Hypervisor, it gives -38<3> as return type. and Kernel Send a
> message to userspace (in case of kernel module) as Kernel does not
> have module support, which is total misleading.

The return code is ENOSYS, which is appropriate for an unimplemented
hypercall.

 -- Keir



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

WARNING - OLD ARCHIVES

xen-devel

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