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

[Xen-devel] how page faults are handled in paravirtualized xen guests?


  • To: "Xen Developers" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: weiming <zephyr.zhao@xxxxxxxxx>
  • Date: Sat, 8 Mar 2008 20:50:55 -0500
  • Delivery-date: Sat, 08 Mar 2008 17:51:17 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=g6cBtE148A+vCIz9H+FIRimcO5+bIadiZGi85ihC7BgQdJTgerinGxsBFfKjUwqq2vzB1gb5tULz5QoDjSj62ABVTahAFGsUNmRYrW5ITXzpimv9I85EQIt8hn89PQ88Q3q40ZTRZcsGEX5gJigZQoBq8+zZFW0iWWOJ/sBYvbU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

I got contradicted information about the path of page fault handling under para-virtualized linux:

1) From some web resources: page fault interruption is trapped by xen hypervisor and it then dispatches to corresponding guest OS
2) From the book "a definitive guide to xen hypervisor": when a guest is scheduled to run by hypervisor, hypervisor installes the guest's IDT (except for special interrupts like timer) to CPU. So almost all interrupts are handled by guest OS directly, bypassing the xen hypervisor.

Which one is correct? (My guess is second one because it's more efficient)

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