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

[Xen-devel] Paravirtualization of the "HLT" instruction (for example) on x386

  • To: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Ian Brown <ianbrn@xxxxxxxxx>
  • Date: Thu, 12 Jan 2006 11:27:31 +0200
  • Delivery-date: Thu, 12 Jan 2006 09:34:02 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=sXgv5N+E7i3sJZF7DvpqH3L/p7mwmVN+S3KOAfB2BX+dC46TMwgwIq5V7RPVah9Np8+scy1UZtuwbpgGkKDxOPTWdu2j6071BIBT4M1sr+XlfH4CSrQaS7MZA2i+QHGh6IIIvY65VvsheSKp5czWdpvyW3cdMRzwekmuLPVSOpA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


I am trying to understand a little more the paravirtualization
implementation in Xen.
As I understand, when using paravirtualization, we want to
change the behavior of certain instructions.
So for example, we don't want to enable guest domains to
perform "HLT" instruction (which will stop the machine).
And there are other instructions which their
default behavior in ring 1 should  be modified.

So I tried to find where in the Xen-3.0 code it is done.
I saw in vmx.c the vmx_vmexit_do_hlt() method ,which is called
when "HLT" is performed,  but this is relevant when running a
platform with VT-x.
I am looking for tracing where this handling or modifying of
the HLT instruction is done in a usual x386 (non-VTX) processor.

Can anybody please point where in the code of Xen 3.0 this is done
(for x86 processors)?

Xen-devel mailing list



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