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

[Xen-devel] [PATCH] [HVM] Fix lmsw handling

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
  • From: "Trolle Selander" <trolle.selander@xxxxxxxxx>
  • Date: Fri, 27 Jun 2008 14:11:57 +0100
  • Cc:
  • Delivery-date: Fri, 27 Jun 2008 06:12:21 -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=IsWYfd/EKvQifGRH54UGqMNpvU6yi+kN6qC89CIbxFLU6gsaXuEGi2slhbpeVO5wPC /Cr/pjSa7J3RVEDvFHzlFdPxcWM0MfZZY8lhRVKvItA90v+RdiddA592qAXROZjOR59C AVtOTbCfdVDdb0fKeg1iJBActn/RqX+YVdgPI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

The lmsw instruction can be used to set CR0_PE, but can never clear it, once set. Currently, as far as I can see, there is no provision to keep lmsw from clearing CR0_PE, either in the vmx code or in x86_emulate code (which is used by SVM to emulate lmsw). This patch fixes this issue.

Signed-off-by: Trolle Selander <trolle.selander@xxxxxxxxxxxxx>

Attachment: lmsw_noclear_pe.patch
Description: Text Data

Xen-devel mailing list



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