)]}'
{
  "commit": "64f415f9bf5bb70376859055ec2d96fbb8c998ce",
  "tree": "caa8de425655fa20f717d6a796a31da3d98704ca",
  "parents": [
    "a8d5dd1c136529e9605066368877d3b8e24dcdba"
  ],
  "author": {
    "name": "Gabe Black",
    "email": "gabeblack@google.com",
    "time": "Thu Mar 21 17:23:03 2019 -0700"
  },
  "committer": {
    "name": "Gabe Black",
    "email": "gabeblack@google.com",
    "time": "Wed Apr 10 10:37:27 2019 +0000"
  },
  "message": "mem: Add sendAtomicBackdoor/recvAtomicBackdoor port methods.\n\nThese both perform atomic accesses like their non-backdoor equivalents,\nand also request a backdoor corresponding to the access.\n\nThe default implementation for recvAtomicBackdoor prints a warning\n(once per port instance), calls recvAtomic to do the actual access,\nand leaves the backdoor pointer as nullptr. That way if an object\ndoesn\u0027t know how to handle or transfer requests for a back door, it\nautomatically replies in a safe way that ignores the back door request.\n\nChange-Id: Ia9fbbe9996eb4b71ea62214d203aa039a05f1618\nReviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/17590\nReviewed-by: Nikos Nikoleris \u003cnikos.nikoleris@arm.com\u003e\nReviewed-by: Daniel Carvalho \u003codanrc@yahoo.com.br\u003e\nMaintainer: Gabe Black \u003cgabeblack@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "001576fe3228e3561fb5c4ae77f1b3ce8deb3683",
      "old_mode": 33188,
      "old_path": "src/mem/port.cc",
      "new_id": "933e98243947d0798d12ae58516979670314d40a",
      "new_mode": 33188,
      "new_path": "src/mem/port.cc"
    },
    {
      "type": "modify",
      "old_id": "2154da007c7a0ec41d4550ade4140344fd1e3046",
      "old_mode": 33188,
      "old_path": "src/mem/port.hh",
      "new_id": "72a02711c5f2836a44815d801273f9d40e535086",
      "new_mode": 33188,
      "new_path": "src/mem/port.hh"
    }
  ]
}
