ping.
On 19 November 2013 10:26, Simon Marchi simon.mar...@polymtl.ca wrote:
Hello there,
liburcu does not build on the Intel Xeon Phi, because the chip is
recognized as x86_64, but lacks the {s,l,m}fence instructions found on
usual x86_64 processors. The following is taken from the Xeon Phi
- Original Message -
From: Simon Marchi simon.mar...@polymtl.ca
To: lttng-dev@lists.lttng.org
Sent: Tuesday, November 19, 2013 4:26:06 PM
Subject: [lttng-dev] Xeon Phi memory barriers
Hello there,
Hi Simon,
While reading this reply, please keep in mind that I'm in a
mindset where
On Fri, Dec 06, 2013 at 08:15:38PM +, Mathieu Desnoyers wrote:
- Original Message -
From: Simon Marchi simon.mar...@polymtl.ca
To: lttng-dev@lists.lttng.org
Sent: Tuesday, November 19, 2013 4:26:06 PM
Subject: [lttng-dev] Xeon Phi memory barriers
Hello there,
Hi Simon,
- Original Message -
From: Paul E. McKenney paul...@linux.vnet.ibm.com
To: Mathieu Desnoyers mathieu.desnoy...@efficios.com
Cc: Simon Marchi simon.mar...@polymtl.ca, lttng-dev@lists.lttng.org
Sent: Friday, December 6, 2013 10:40:45 PM
Subject: Re: [lttng-dev] Xeon Phi memory barriers
