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

[Xen-devel] Why using hypercall_page ?


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Wu Bingzheng <wubingzheng@xxxxxxxxx>
  • Date: Thu, 23 Oct 2008 09:17:57 +0800
  • Delivery-date: Wed, 22 Oct 2008 18:18:39 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=AhvDtbQaq/t4aSgof+Q9Aim4asV6wGl2yloi55bCiYOZcu+hqw2REizXP1FHU8AJVn SxrjUQ4yKHFnppPoMj2Yx4QpC4T/VQWklckMl4vkJGJvEXrhyMe4acaiSH9tuToEgYsH 5DImoJ2BxTjdybaDMlswS0xdgpIASI/4hvpfA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello,

I am studing Xen hypercall now. I found that hypercall is invoked via
hypercall_page, which is only filled with (in
no-hypervisor-kernel-mode ):

mov $i, %eax
int $0x82
ret

Why not invoked the hypercall directly by "int $0x82" ? What's the
advantage of using hypercall_page?

Thanks,
Wu


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