This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-ia64-devel] Question about paravirtualization

To: Dan Magenheimer <dan.magenheimer@xxxxxx>
Subject: [Xen-ia64-devel] Question about paravirtualization
From: Haavard Bjerke <havard.bjerke@xxxxxxx>
Date: Sat, 4 Jun 2005 22:14:32 +0200
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 04 Jun 2005 20:13:50 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4i
I'm looking the Xenlinux paravirtualization, just for the sake of studies, and 
a few questions came to mind.

In ivt.S, the "thash" instructions are replaced with "tak" instructions. I 
understand the need for paravirtualizing thash instructions, but not in 
Xenlinux' IVT. Will Xenlinux' fault handlers ever be executed? Won't the 
hypervisor's IVT be used instead? Are these instructions paravirtualized just 
in case?

And is the choice of the "tak" instruction just so that a privop fault will be 
rised, or does it have a function?


Xen-ia64-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-ia64-devel] Question about paravirtualization, Haavard Bjerke <=