1. 02 Nov, 2018 1 commit
  2. 18 Nov, 2015 1 commit
  3. 10 Oct, 2013 1 commit
  4. 21 Aug, 2013 10 commits
  5. 16 Aug, 2013 5 commits
  6. 14 Aug, 2013 14 commits
  7. 13 Aug, 2013 4 commits
  8. 12 Aug, 2013 2 commits
    • Ivo Anjo's avatar
      Make javartm usage safe on non-rtm cpus · 127555c6
      Ivo Anjo authored
      One of the use cases of javartm is that any app may use it, and use the Transaction.RTM_AVAILABLE
      flag to trigger execution with javartm, or to decide how to fallback onto something else.
      
      Nevertheless, if the application ignored the RTM_AVAILABLE flag and mistakenly invoked the javartm
      functions, it would result in a VM segfault.
      
      To avoid this, the native code part of javartm has been split into three libraries. The first is
      libtestrtmsupport.so, that only includes the code that checks for rtm usage.
      After checking for rtm support, the code decides if either libjavartm-dummy.so or libjavartm.so
      are loaded; libjavartm-dummy.so just includes dummy implementations of the native code functions
      that throw exceptions whenever they are used.
      
      This way, older machines can never trigger the execution of rtm instructions on older machines,
      making javartm usage safe.
      127555c6
    • Ivo Anjo's avatar
      Compile native code with -march=core-avx2 · d7edb0d6
      Ivo Anjo authored
      We're going to be running on (at least) haswell anyway.
      d7edb0d6
  9. 09 Aug, 2013 2 commits