From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <jbeulich@novell.com>
Subject: svm vmexit action sequence
Date: Thu, 10 May 2007 18:01:58 +0200
Message-ID: <46435E16.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Is there any particular reason why on 32-bits the order is VMLOAD then
HVM_SAVE_ALL_NOSEGREGS, while on 64-bits its is the other way around?
Trying to put in the saving of EAX, I could save a GET_CURRENT() on =
32-bits
if I could order things the same way as on 64-bits.

Also, both versions seem to have a redundant GET_CURRENT() right after
the clgi/sti sequence - again, is there a particular reason for this?

Thanks, Jan