 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] [patch] double incrementing l2tab
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] [patch] double incrementing l2tab |
| From: | Scott Parish <srparish@xxxxxxxxxx> |
| Date: | Thu, 12 May 2005 21:06:03 +0000 |
| Delivery-date: | Thu, 12 May 2005 21:21:09 +0000 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| 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 |
| User-agent: | Mutt/1.4.2.1i |
For PAE, l2e_get_phys() will look something like this:
#define l2e_get_phys(_x) ((((u64)(_x).l2_hi & 0x0f) << 32) |\
((u64)(_x).l2_lo & PAGE_MASK))
Thus l2e_get_phys(++foo) is not safe, as the increment will be evaluated
multiple times and at undefined times.
sRp
--
Scott Parish
Signed-off-by: srparish@xxxxxxxxxx
_______________________________________________ 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] [PATCH] x86-64-phys-ma.patch, Arun Sharma |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH] x86-64-phys-ma.patch, Christian Limpach |
| Previous by Thread: | [Xen-devel] [PATCH] x86-64-phys-ma.patch, Arun Sharma |
| Next by Thread: | Re: [Xen-devel] [patch] double incrementing l2tab, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
