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

[Xen-devel] Explicit return type for Hypercall


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Tej <bewith.tej@xxxxxxxxx>
  • Date: Thu, 9 Apr 2009 16:08:44 +0530
  • Delivery-date: Thu, 09 Apr 2009 03:39:40 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=lRsW8UBFPNHiNh0w47orxFOWbZeqNsuB3B4uYLBiFnaW6hpuF0GiffrjvfpCJrgOD2 yasseZGnjLcMRzia3F80AdGQ0GwpYtf0drBQa1kH3r4w0bKtlJD5KnHvTCMaVQjl+zfU ZJUQqwUqmwMXXFBqD5ZzqINdq2kweE6HUT7Q0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi All

Some basic doubts about Hypercall return type.
If kernel issue a hypercall, and there is no corresponding entry in
entry.S in Hypervisor, it gives weired return type and Kernel
interpret it in completely different manner.

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.

1. Is this return type is intended?
2. Why there is no interpretation of hypercall return type in kernel?


Hope i am not missing any obvious thing

thanks
-tej

_______________________________________________
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®.