[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1448031764-23669-1-git-send-email-stefano.stabellini@eu.citrix.com>
Date: Fri, 20 Nov 2015 15:02:44 +0000
From: Stefano Stabellini <stefano.stabellini@...citrix.com>
To: <xen-devel@...ts.xensource.com>
CC: <linux-kernel@...r.kernel.org>, <Stefano.Stabellini@...citrix.com>,
Stefano Stabellini <stefano.stabellini@...citrix.com>,
Mark Rutland <mark.rutland@....com>, <konrad.wilk@...cle.com>,
<david.vrabel@...rix.com>, <boris.ostrovsky@...cle.com>
Subject: [PATCH] xen/time: use READ_ONCE
Use READ_ONCE through the code, rather than explicit barriers.
Suggested-by: Mark Rutland <mark.rutland@....com>
Signed-off-by: Stefano Stabellini <stefano.stabellini@...citrix.com>
CC: Mark Rutland <mark.rutland@....com>
CC: konrad.wilk@...cle.com
CC: david.vrabel@...rix.com
CC: boris.ostrovsky@...cle.com
---
drivers/xen/time.c | 17 +++++++----------
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/drivers/xen/time.c b/drivers/xen/time.c
index 433fe24..7107842 100644
--- a/drivers/xen/time.c
+++ b/drivers/xen/time.c
@@ -25,7 +25,7 @@ static u64 get64(const u64 *p)
if (BITS_PER_LONG < 64) {
u32 *p32 = (u32 *)p;
- u32 h, l;
+ u32 h, l, h2;
/*
* Read high then low, and then make sure high is
@@ -34,15 +34,14 @@ static u64 get64(const u64 *p)
* XXX some clean way to make this endian-proof?
*/
do {
- h = p32[1];
- barrier();
- l = p32[0];
- barrier();
- } while (p32[1] != h);
+ h = READ_ONCE(p32[1]);
+ l = READ_ONCE(p32[0]);
+ h2 = READ_ONCE(p32[1]);
+ } while(h2 != h);
ret = (((u64)h) << 32) | l;
} else
- ret = *p;
+ ret = READ_ONCE(*p);
return ret;
}
@@ -66,9 +65,7 @@ void xen_get_runstate_snapshot(struct vcpu_runstate_info *res)
*/
do {
state_time = get64(&state->state_entry_time);
- barrier();
- *res = *state;
- barrier();
+ *res = READ_ONCE(*state);
} while (get64(&state->state_entry_time) != state_time);
}
--
1.7.10.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists