 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] svm vmexit action sequence
| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] svm vmexit action sequence |
| From: | "Jan Beulich" <jbeulich@xxxxxxxxxx> |
| Date: | Thu, 10 May 2007 18:01:58 +0200 |
| Delivery-date: | Thu, 10 May 2007 08:59:45 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: [Xen-devel] Xrenstore and many save/restore cycles..., Petersson, Mats |
|---|---|
| Next by Date: | RE: [Xen-devel] svm vmexit action sequence, Petersson, Mats |
| Previous by Thread: | [Xen-devel] Send an event using event channels, Daniele Sgandurra |
| Next by Thread: | RE: [Xen-devel] svm vmexit action sequence, Petersson, Mats |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
