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

Re: [Xen-devel] [PATCH 1/5] vmx/hvm: move mov-cr handling functions to generic HVM code


  • To: Andre Przywara <andre.przywara@xxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Mon, 18 Apr 2011 09:48:17 +0100
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 18 Apr 2011 01:49:13 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=nXdcASlehWmKZftwPc15L9U0s1tUi4RyK6+zaFmAuloZXfb5/wjWWch04c5TJXLFxS dFZk2OGI4l963Bm7Z2CMH2aixLhsSYtWPRDbubLqRGiRwMLnLbGUDy6wF5pbGQ6gquTZ DEOQyI9v5dfRbiR7U4NfhHuieUnWj2mk8/5bM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acv9pVxKZvCAWJKrNUGp5bjEqjawkg==
  • Thread-topic: [Xen-devel] [PATCH 1/5] vmx/hvm: move mov-cr handling functions to generic HVM code

On 15/04/2011 13:21, "Andre Przywara" <andre.przywara@xxxxxxx> wrote:

> Currently the handling of CR accesses intercepts is done much
> differently in SVM and VMX. For future usage move the VMX part
> into the generic HVM path and use the exported functions.

Cleaned up and applied as c/s 23233. In particular it broke VMX, by not
preoperly decoding the GPR component of the exit qualification before
passing to the new generic handler.

 -- Keir

> Signed-off-by: Andre Przywara <andre.przywara@xxxxxxx>
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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