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

[Xen-devel] supervisor_mode_kernel and hypercall

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Yanjun Wu" <yanjun.wu@xxxxxxxxx>
  • Date: Mon, 20 Oct 2008 18:14:36 +0800
  • Delivery-date: Mon, 20 Oct 2008 03:14:58 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=v02O3NXKLo2Sc0RWBYs2CzRIBq6WbWgzFnbALrKOtnmvdb0vf+IZJ3dw5ODImLZpY6 GACO5xT2eWzavCMW7u5nEne6K1buyUQyU1WCkCa+tG/hQqnO+b/5S/cttt3CjUOTAl/+ MuFZUqd1V/BTxmoaV/Fmd6OEwyvQ44qyTiE2Y=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

In xen/arch/x86/x86_32/traps.c, if supervisor_mode_kernel is true, the hypercall_page will be initialized by hypercall_page_initialise_ring0_kernel.
my question is, does supervisor_mode_kernel mean that the guest kernel is also running in ring0, the same privilege level as Xen hypervisor?

The book "the definitive guide to the xen hypervisor" (in page 30) says hypercall through int82 is now deprecated, and replaced by hypercall_page.
but int82 can still be found in hypercall_page_initialise_ring1_kernel. In what situation it will be used?


Xen-devel mailing list



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