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

[Xen-devel] HVM hypercalls, hvm_hypercall_table

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "George Surka" <gsurka@xxxxxxxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 15 Mar 2007 15:31:13 -0400
  • Delivery-date: Thu, 15 Mar 2007 12:30:20 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdnOH49IAIVSTjGTcG3UeosKV7iLA==
  • Thread-topic: HVM hypercalls, hvm_hypercall_table

Hi everyone,
I am running XenEnterprise 3.1.0 (Xen v. on x86-32 hardware. I have noticed that the hvm_hypercall_table is initialized for only 6 hypercalls (memory_op, multicall, xen_version, event_channel_op, sched_op, and hvm_op). The hypercall_page for HVM domain is initialized with HVM exit (VMCALL instr.) - all stubs.
So, how do I do the other hypercalls (beyond those 6) from HVM domain? Do I just have to use INT 0x82 trap without using the hypercall-page (without using the HYPERVISOR_* hypercall macros in hypercall.h)?
Why there is just those six hypercalls implemented as HVM-hypercalls?
Xen-devel mailing list



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