Where should be that implementations placed if we want other platform to
reuse them?
Maxim.
On 03/06/15 19:22, Mike Holmes wrote:
Linux-generic should be a reference implementation and does not need
archetecture specific acceleration.
Signed-off-by: Mike Holmes <[email protected]>
---
platform/linux-generic/odp_time.c | 47 +++------------------------------------
1 file changed, 3 insertions(+), 44 deletions(-)
diff --git a/platform/linux-generic/odp_time.c
b/platform/linux-generic/odp_time.c
index 31d6656..6f40361 100644
--- a/platform/linux-generic/odp_time.c
+++ b/platform/linux-generic/odp_time.c
@@ -6,52 +6,13 @@
#define _POSIX_C_SOURCE 200809L
+#include <time.h>
#include <odp/time.h>
-#include <odp/hints.h>
#include <odp/system_info.h>
-
-#define GIGA 1000000000
-
-#if defined __x86_64__ || defined __i386__
-
-uint64_t odp_time_cycles(void)
-{
- union {
- uint64_t tsc_64;
- struct {
- uint32_t lo_32;
- uint32_t hi_32;
- };
- } tsc;
-
- __asm__ __volatile__ ("rdtsc" :
- "=a" (tsc.lo_32),
- "=d" (tsc.hi_32) : : "memory");
-
- return tsc.tsc_64;
-}
-
-
-#elif defined __OCTEON__
-
-uint64_t odp_time_cycles(void)
-{
- #define CVMX_TMP_STR(x) CVMX_TMP_STR2(x)
- #define CVMX_TMP_STR2(x) #x
- uint64_t cycle;
-
- __asm__ __volatile__ ("rdhwr %[rt],$" CVMX_TMP_STR(31) :
- [rt] "=d" (cycle) : : "memory");
-
- return cycle;
-}
-
-#else
-
-#include <time.h>
-#include <stdlib.h>
#include <odp_debug_internal.h>
+#define GIGA 1000000000
+
uint64_t odp_time_cycles(void)
{
struct timespec time;
@@ -74,8 +35,6 @@ uint64_t odp_time_cycles(void)
return cycles;
}
-#endif
-
uint64_t odp_time_diff_cycles(uint64_t t1, uint64_t t2)
{
if (odp_likely(t2 > t1))
_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp
