DPDK patches and discussions
 help / color / mirror / Atom feed
From: Didier Pallard <didier.pallard@6wind.com>
To: thomas.monjalon@6wind.com
Subject: [dpdk-dev] [PATCH v2] timer: add lfence before TSC read
Date: Wed, 19 Feb 2014 12:39:05 +0100	[thread overview]
Message-ID: <1392809945-28025-1-git-send-email-didier.pallard@6wind.com> (raw)
In-Reply-To: <1390562134-24720-1-git-send-email-didier.pallard@6wind.com>

According to Intel Developer's Manual:

"The RDTSC instruction is not a serializing instruction. It does not necessarily wait
 until all previous instructions have been executed before reading the counter. Simi-
 larly, subsequent instructions may begin execution before the read operation is
 performed. If software requires RDTSC to be executed only after all previous instruc-
 tions have completed locally, it can either use RDTSCP (if the processor supports that
 instruction) or execute the sequence LFENCE;RDTSC."

So add a rte_rdtsc_precise function that do a lfence instruction before rdtsc to
synchronize read operations and ensure that the TSC read is done at the expected
place.

Signed-off-by: Didier Pallard <didier.pallard@6wind.com>
---

Introduce a rte_rdtsc_precise function that adds lfence before reading tsc counter.

 lib/librte_eal/common/include/rte_cycles.h |   37 ++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)

diff --git a/lib/librte_eal/common/include/rte_cycles.h b/lib/librte_eal/common/include/rte_cycles.h
index cc6fe71..662f62d 100644
--- a/lib/librte_eal/common/include/rte_cycles.h
+++ b/lib/librte_eal/common/include/rte_cycles.h
@@ -128,6 +128,43 @@ rte_rdtsc(void)
 }
 
 /**
+ * Read the TSC register precisely where function is called.
+ *
+ * @return
+ *   The TSC for this lcore.
+ */
+static inline uint64_t
+rte_rdtsc_precise(void)
+{
+	union {
+		uint64_t tsc_64;
+		struct {
+			uint32_t lo_32;
+			uint32_t hi_32;
+		};
+	} tsc;
+
+	/* serialize previous load instructions in pipe */
+	asm volatile("lfence");
+
+#ifdef RTE_LIBRTE_EAL_VMWARE_TSC_MAP_SUPPORT
+	if (unlikely(rte_cycles_vmware_tsc_map)) {
+		/* ecx = 0x10000 corresponds to the physical TSC for VMware */
+		asm volatile("rdpmc" :
+		             "=a" (tsc.lo_32),
+		             "=d" (tsc.hi_32) :
+		             "c"(0x10000));
+		return tsc.tsc_64;
+	}
+#endif
+
+	asm volatile("rdtsc" :
+		     "=a" (tsc.lo_32),
+		     "=d" (tsc.hi_32));
+	return tsc.tsc_64;
+}
+
+/**
  * Get the measured frequency of the RDTSC counter
  *
  * @return
-- 
1.7.10.4

       reply	other threads:[~2014-02-19 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1390562134-24720-1-git-send-email-didier.pallard@6wind.com>
2014-02-19 11:39 ` Didier Pallard [this message]
2014-02-19 16:46   ` [dpdk-dev] [PATCH v3] timer: add new rte_rdtsc_precise function Didier Pallard
2014-02-26  9:39     ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1392809945-28025-1-git-send-email-didier.pallard@6wind.com \
    --to=didier.pallard@6wind.com \
    --cc=thomas.monjalon@6wind.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).