)]}'
{
  "log": [
    {
      "commit": "c45a6816c19dee67b8f725e6646d428901a6dc24",
      "tree": "096e3263fd14e140685bcc3082394ff15f5aeddb",
      "parents": [
        "72e61eb40b55dd57031ec5971e810649f82b0259"
      ],
      "author": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Fri May 02 21:50:50 2008 -0500"
      },
      "committer": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Fri May 02 21:50:50 2008 +1000"
      },
      "message": "virtio: explicit advertisement of driver features\n\nA recent proposed feature addition to the virtio block driver revealed\nsome flaws in the API: in particular, we assume that feature\nnegotiation is complete once a driver\u0027s probe function returns.\n\nThere is nothing in the API to require this, however, and even I\ndidn\u0027t notice when it was violated.\n\nSo instead, we require the driver to specify what features it supports\nin a table, we can then move the feature negotiation into the virtio\ncore.  The intersection of device and driver features are presented in\na new \u0027features\u0027 bitmap in the struct virtio_device.\n\nNote that this highlights the difference between Linux unsigned-long\nbitmaps where each unsigned long is in native endian, and a\nstraight-forward little-endian array of bytes.\n\nDrivers can still remove feature bits in their probe routine if they\nreally have to.\n\nAPI changes:\n- dev-\u003econfig-\u003efeature() no longer gets and acks a feature.\n- drivers should advertise their features in the \u0027feature_table\u0027 field\n- use virtio_has_feature() for extra sanity when checking feature bits\n\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\n"
    },
    {
      "commit": "c6fd47011b4bdebad3f1513bac75fe4895e332ee",
      "tree": "12224cdb2594be26e02291b142ba6e1e2c1c8122",
      "parents": [
        "15f9c8903cbdb02aee0f1bcf86a97c2e238b9a3d"
      ],
      "author": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Mon Feb 04 23:50:05 2008 -0500"
      },
      "committer": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Mon Feb 04 23:50:06 2008 +1100"
      },
      "message": "virtio: Allow virtio to be modular and used by modules\n\nThis is needed for the virtio PCI device to be compiled as a module.\n\nSigned-off-by: Anthony Liguori \u003caliguori@us.ibm.com\u003e\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\n"
    },
    {
      "commit": "6e5aa7efb27aec7e55b6463fa2c8db594c4226fa",
      "tree": "060a955e711ac224136157a5410e88dcdab965af",
      "parents": [
        "b3369c1fb410fddeb38a404316c861395f6d6ae8"
      ],
      "author": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Mon Feb 04 23:50:03 2008 -0500"
      },
      "committer": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Mon Feb 04 23:50:03 2008 +1100"
      },
      "message": "virtio: reset function\n\nA reset function solves three problems:\n\n1) It allows us to renegotiate features, eg. if we want to upgrade a\n   guest driver without rebooting the guest.\n\n2) It gives us a clean way of shutting down virtqueues: after a reset,\n   we know that the buffers won\u0027t be used by the host, and\n\n3) It helps the guest recover from messed-up drivers.\n\nSo we remove the -\u003eshutdown hook, and the only way we now remove\nfeature bits is via reset.\n\nWe leave it to the driver to do the reset before it deletes queues:\nthe balloon driver, for example, needs to chat to the host in its\nremove function.\n\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\n"
    },
    {
      "commit": "a586d4f6016f7139d8c26df0e6927131168d3b5b",
      "tree": "1c47e1a6b6b8fb18baa42f32980f29c4ae9cbbdc",
      "parents": [
        "f35d9d8aae08940b7fdd1bb8110619da2ece6b28"
      ],
      "author": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Mon Feb 04 23:49:56 2008 -0500"
      },
      "committer": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Mon Feb 04 23:49:57 2008 +1100"
      },
      "message": "virtio: simplify config mechanism.\n\nPreviously we used a type/len pair within the config space, but this\nseems overkill.  We now simply define a structure which represents the\nlayout in the config space: the config space can now only be extended\nat the end.\n\nThe main driver-visible changes:\n1) We indicate what fields are present with an explicit feature bit.\n2) Virtqueues are explicitly numbered, and not in the config space.\n\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\n"
    },
    {
      "commit": "74b2553f1d13e60fb27063204bd5b6908a6f8494",
      "tree": "cd35e82d16cf190ccd95362478a598314de639ce",
      "parents": [
        "d1c856e0f1a4c946c6329cff126548ef4288735f"
      ],
      "author": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Mon Nov 19 11:20:42 2007 -0500"
      },
      "committer": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Mon Nov 19 11:20:42 2007 +1100"
      },
      "message": "virtio: fix module/device unloading\n\nThe virtio code never hooked through the -\u003eremove callback.  Although\nnoone supports device removal at the moment, this code is already\nneeded for module unloading.\n\nThis of course also revealed bugs in virtio_blk, virtio_net and lguest\nunloading paths.\n\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\n"
    },
    {
      "commit": "b01d9f2863349b0e041b90c3c86a998ee0fed2b0",
      "tree": "8789a06631a0ee502c58388d12c230eb4a2059b2",
      "parents": [
        "31610434bc3523c0b01a10917a1185096a03c4c8"
      ],
      "author": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Mon Oct 22 11:03:39 2007 +1000"
      },
      "committer": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Tue Oct 23 15:49:55 2007 +1000"
      },
      "message": "Module autoprobing support for virtio drivers.\n\nThis adds the logic to convert the virtio ids into module aliases, and\nincludes a modalias entry in sysfs and the env var to make probing work.\n\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\n"
    },
    {
      "commit": "ec3d41c4db4c21164332826ea8d812f94f2f6886",
      "tree": "9b947e900745cfcc4df7409c6ba5583428964215",
      "parents": [
        "47436aa4ad054c1c7c8231618e86ebd9305308dc"
      ],
      "author": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Mon Oct 22 11:03:36 2007 +1000"
      },
      "committer": {
        "name": "Rusty Russell",
        "email": "rusty@rustcorp.com.au",
        "time": "Tue Oct 23 15:49:54 2007 +1000"
      },
      "message": "Virtio interface\n\nThis attempts to implement a \"virtual I/O\" layer which should allow\ncommon drivers to be efficiently used across most virtual I/O\nmechanisms.  It will no-doubt need further enhancement.\n\nThe virtio drivers add buffers to virtio queues; as the buffers are consumed\nthe driver \"interrupt\" callbacks are invoked.\n\nThere is also a generic implementation of config space which drivers can query\nto get setup information from the host.\n\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\nCc: Dor Laor \u003cdor.laor@qumranet.com\u003e\nCc: Arnd Bergmann \u003carnd@arndb.de\u003e\n"
    }
  ]
}