Read about our upcoming Code of Conduct on this issue

  1. 09 Apr, 2019 1 commit
    • alex@thinkpad's avatar
      QEMU logging: updated DryOS and VxWorks task switch handling · 9049426c8cce
      alex@thinkpad authored
      It was quite hard to pass the test suite, as there were lots of edge cases:
      - context switch may happen either in a timer interrupt, or in a regular task (e.g. msleep, sempahores and so on)
      - context switch is not atomic - it happens a few instructions (or function calls!) afterh updating the current task pointer
      - until the registers are swapped for the new task, we are still on the stack of the previous task
      - there may be dummy task switches (i.e. from one task to the same task)
      - an interrupt can occur in the middle of a (non-atomic) context switch (!)
      - VxWorks models do not even use a unique task ID (!)
      Result: QEMU no longer crashes during logging tests!
      Issue: these cameras do not appear to use an unique task ID. Workaround: assign our own task IDs.
      branch : qemu
  2. 29 Dec, 2018 1 commit
  3. 28 Apr, 2018 1 commit
  4. 17 Oct, 2017 1 commit
  5. 07 Aug, 2017 1 commit
  6. 05 Aug, 2017 2 commits
  7. 29 Jul, 2017 1 commit
    • alex@thinkpad's avatar
      QEMU tests: found a way to get deterministic execution (icount option) · 2d1d5d538420
      alex@thinkpad authored
      - reworked the call/return trace tests to also run on main firmware (with -icount)
      - fixme: CF models do not have deterministic execution, even with -icount
      - fromutility tests also enabled on CF models (IDC only)
      - "first interrupt" test replaced with full call/return trace on main firmware
      - removed "sorted IDC" tests (the regular IDC + call/return trace tests are much stronger)
      branch : qemu