1. 29 Sep, 2014 1 commit
  2. 28 Sep, 2014 5 commits
    • Philippe Gerum's avatar
      doc/asciidoc: remove left over · 9633e2dd
      Philippe Gerum authored
    • Philippe Gerum's avatar
      doc: prebuild · 32baabc2
      Philippe Gerum authored
    • Philippe Gerum's avatar
      alchemy/timer: drop TSC reading and conversion ops from the API · 331d6947
      Philippe Gerum authored
      Due to the accumulation of rounding errors, using raw TSC counts for
      measuring long timespans may yield (increasingly) wrong results.
      In short, either we guarantee stable computations with counts of
      nanoseconds, or with TSC instead, regardless of the clock source
      frequency, but we can't provide such guarantee for both. From an API
      standpoint, the nanosecond unit is definitely the best option as the
      meaning won't vary between clock sources.
      Avoiding the overhead of the tsc->ns conversion as a justification to
      use raw TSC counts does not fly anymore, as all architectures
      implement fast arithmetics for this operation over Cobalt, and
      Mercury's (virtual) TSC is actually mapped over CLOCK_MONOTONIC.
      Therefore, all TSC reading and ns<->tsc conversion services are
      removed from the Alchemy API to prevent misleading results. Users
      should measure timespans (or get timestamps) as counts of nanoseconds
      as returned by rt_timer_read() instead.
      The following calls are dropped from the API:
      - rt_timer_tsc()
      - rt_timer_ns2tsc()
      - rt_timer_tsc2ns()
      In addition, rt_timer_inquire() does not return the TSC count anymore.
    • Philippe Gerum's avatar
      build: add version name · f3d3c7db
      Philippe Gerum authored
    • Philippe Gerum's avatar
      doc/autotune: clarify some points · f4384791
      Philippe Gerum authored
  3. 26 Sep, 2014 2 commits
  4. 25 Sep, 2014 12 commits
  5. 24 Sep, 2014 13 commits
  6. 23 Sep, 2014 7 commits