 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] cut-and-paste error in x86-64's entry-xen.S ?
| To: | <jun.nakajima@xxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] cut-and-paste error in x86-64's entry-xen.S ? |
| From: | "Jan Beulich" <jbeulich@xxxxxxxxxx> |
| Date: | Tue, 08 Aug 2006 08:26:11 +0100 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Tue, 08 Aug 2006 00:25:49 -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 |
Jun, native code following sysret_careful uses 'sti before calling schedule(), but the Xen equivalent uses XEN_BLOCK_EVENTS() - I'm fairly certain XEN_UNBLOCK_EVENTS() is meant here, otherwise a comment should explain why this needs to deviate from native. Thanks for your opinion, 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: | [Xen-devel] VMX Status Report 10960:ec8dd0528fc6, Zheng, Jeff |
|---|---|
| Next by Date: | [Xen-devel] omission in x86-64's entry-xen.S ?, Jan Beulich |
| Previous by Thread: | [Xen-devel] VMX Status Report 10960:ec8dd0528fc6, Zheng, Jeff |
| Next by Thread: | [Xen-devel] omission in x86-64's entry-xen.S ?, Jan Beulich |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
