)]}'
{
  "log": [
    {
      "commit": "ba4e7d973dd09b66912ac4c0856add8b0703a997",
      "tree": "32a87edb83a427ffd22645c5f77e6cec8be4e719",
      "parents": [
        "e6c03c5b40314d787f7053f631594d6b1bd609e8"
      ],
      "author": {
        "name": "Thomas Hellstrom",
        "email": "thellstrom@vmware.com",
        "time": "Wed Jun 10 15:20:19 2009 +0200"
      },
      "committer": {
        "name": "Dave Airlie",
        "email": "airlied@redhat.com",
        "time": "Mon Jun 15 09:37:57 2009 +1000"
      },
      "message": "drm: Add the TTM GPU memory manager subsystem.\n\nTTM is a GPU memory manager subsystem designed for use with GPU\ndevices with various memory types (On-card VRAM, AGP,\nPCI apertures etc.). It\u0027s essentially a helper library that assists\nthe DRM driver in creating and managing persistent buffer objects.\n\nTTM manages placement of data and CPU map setup and teardown on\ndata movement. It can also optionally manage synchronization of\ndata on a per-buffer-object level.\n\nTTM takes care to provide an always valid virtual user-space address\nto a buffer object which makes user-space sub-allocation of\nbig buffer objects feasible.\n\nTTM uses a fine-grained per buffer-object locking scheme, taking\ncare to release all relevant locks when waiting for the GPU.\nAlthough this implies some locking overhead, it\u0027s probably a big\nwin for devices with multiple command submission mechanisms, since\nthe lock contention will be minimal.\n\nTTM can be used with whatever user-space interface the driver\nchooses, including GEM. It\u0027s used by the upcoming Radeon KMS DRM driver\nand is also the GPU memory management core of various new experimental\nDRM drivers.\n\nSigned-off-by: Thomas Hellstrom \u003cthellstrom@vmware.com\u003e\nSigned-off-by: Jerome Glisse \u003cjglisse@redhat.com\u003e\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\n"
    }
  ]
}