[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • From: Tej <bewith.tej@xxxxxxxxx>
  • Date: Thu, 9 Apr 2009 17:58:37 +0530
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 09 Apr 2009 05:29:08 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=cnV3BKrkFP7nlRRWHfQgo5ltdZazApMeWlz2c6v2cV0QHGIaMW7tspMJjdsaJwPEYW VBp4ne/kBYQNhwhBlSGSMBrUCYQvragYYUChmzQLWtvUvbMNxtyRxr3WPsnqN6goqgJ7 c6BL7R/rF2kqOF+aaKODbxZVUcsK94106Xwac=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Thu, Apr 9, 2009 at 4:50 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> 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.

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.

>
>  -- Keir
>
>
>

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.