)]}'
{
  "commit": "026c66393d71a4ebe122974712b8180b1157e59e",
  "tree": "19bccc496043c07835a38b1a2b4772aecc8e0efd",
  "parents": [
    "3c83843e111ece30d3dfb5143d5e6aed6164d587"
  ],
  "author": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Sat Feb 11 22:46:01 2023 +0000"
  },
  "committer": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Sun Feb 12 17:18:10 2023 +0000"
  },
  "message": "[rng] Work around broken RTC periodic interrupts in Hyper-V\n\nSome versions of Hyper-V (observed in some Microsoft Azure virtual\nmachines as noted in commit 74222cd (\"[rng] Check for functioning RTC\ninterrupt\"), and now in Windows Server 2022) fail to properly emulate\nthe RTC periodic interrupt.  The typical symptom is that only a single\ninterrupt will be generated: subsequent interrupts will appear to be\nasserted by the virtual RTC but will be ignored by the virtual PIC.\n\nExperiments show that this apparent hypervisor bug can be worked\naround by disabling and re-enabling the periodic interrupt within the\ninterrupt handler.\n\nApply this workaround only if required, since doing so will\nsubstantially increase the overhead of each RTC interrupt.\n\nSigned-off-by: Michael Brown \u003cmcb30@ipxe.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c400d8a78b5c4d02191caaf69845e0214a9c7379",
      "old_mode": 33188,
      "old_path": "src/arch/x86/interface/pcbios/rtc_entropy.c",
      "new_id": "c9e5e461721eac5390265b331d0545a13f12a5dc",
      "new_mode": 33188,
      "new_path": "src/arch/x86/interface/pcbios/rtc_entropy.c"
    }
  ]
}