)]}'
{
  "commit": "683dca6bd5057a87d9376475b0c7e30d56d8e532",
  "tree": "e9a0ca88dcaf7bd08c4044b1ad0ff9c21478d57f",
  "parents": [
    "c6acbe861f1ed4203f4864baf756686064ba561f"
  ],
  "author": {
    "name": "Laurent Vivier",
    "email": "lvivier@redhat.com",
    "time": "Tue Aug 25 16:16:21 2015 +0200"
  },
  "committer": {
    "name": "Laurent Vivier",
    "email": "lvivier@redhat.com",
    "time": "Fri Sep 25 14:54:04 2015 +0200"
  },
  "message": "mips: remove muldiv64()\n\nOriginally, timers were ticks based, and it made sense to\nadd ticks to current time to know when to trigger an alarm.\n\nBut since commit:\n\n7447545 change all other clock references to use nanosecond resolution accessors\n\nAll timers use nanoseconds and we need to convert ticks to nanoseconds, by\ndoing something like:\n\n    y \u003d muldiv64(x, get_ticks_per_sec(), TIMER_FREQ)\n\nwhere x is the number of device ticks and y the number of system ticks.\n\ny is used as nanoseconds in timer functions,\nit works because 1 tick is 1 nanosecond.\n(get_ticks_per_sec() is 10^9)\n\nBut as MIPS timer frequency is 100 MHz, we can also do:\n\n    y \u003d x * 10; /* 100 MHz period is 10 ns */\n\nSigned-off-by: Laurent Vivier \u003clvivier@redhat.com\u003e\nReviewed-by: Leon Alrae \u003cleon.alrae@imgtec.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ba9264b415662ca4b88c3e271938aa3b90649996",
      "old_mode": 33188,
      "old_path": "hw/mips/cputimer.c",
      "new_id": "f046588ada4749dc5934726eb23c7e34d0e1be6f",
      "new_mode": 33188,
      "new_path": "hw/mips/cputimer.c"
    }
  ]
}