)]}'
{
  "log": [
    {
      "commit": "2044892d4a005a78796c92fd1aef4633be896698",
      "tree": "949b29a43a3c2c282dd1d4d00d2f70b3265e7893",
      "parents": [
        "ddf0289db22c4ae2192a252706792837528605c6"
      ],
      "author": {
        "name": "Wu Fengguang",
        "email": "fengguang.wu@intel.com",
        "time": "Thu Dec 24 09:04:16 2009 +0800"
      },
      "committer": {
        "name": "Marcelo Tosatti",
        "email": "mtosatti@redhat.com",
        "time": "Mon Mar 01 12:35:43 2010 -0300"
      },
      "message": "KVM: trivial document fixes\n\nSigned-off-by: Wu Fengguang \u003cfengguang.wu@intel.com\u003e\nSigned-off-by: Marcelo Tosatti \u003cmtosatti@redhat.com\u003e\n"
    },
    {
      "commit": "dab4b911a5327859bb8f969249c6978c26cd4853",
      "tree": "a21d0ef04e3bf831b2f9e674b6266535267cc9ce",
      "parents": [
        "6e24a6eff4571002cd48b99a2b92dc829ce39cb9"
      ],
      "author": {
        "name": "Jan Kiszka",
        "email": "jan.kiszka@web.de",
        "time": "Sun Dec 06 18:24:15 2009 +0100"
      },
      "committer": {
        "name": "Marcelo Tosatti",
        "email": "mtosatti@redhat.com",
        "time": "Sun Dec 27 13:36:33 2009 -0200"
      },
      "message": "KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates\n\nUser space may not want to overwrite asynchronously changing VCPU event\nstates on write-back. So allow to skip nmi.pending and sipi_vector by\nsetting corresponding bits in the flags field of kvm_vcpu_events.\n\n[avi: advertise the bits in KVM_GET_VCPU_EVENTS]\n\nSigned-off-by: Jan Kiszka \u003cjan.kiszka@siemens.com\u003e\nSigned-off-by: Avi Kivity \u003cavi@redhat.com\u003e\n"
    },
    {
      "commit": "3cfc3092f40bc37c57ba556cfd8de4218f2135ab",
      "tree": "562d61febfe7d3c99ea08e376b3f3c016cff613c",
      "parents": [
        "65ac7264043740572ba804edca03c374d70427c9"
      ],
      "author": {
        "name": "Jan Kiszka",
        "email": "jan.kiszka@web.de",
        "time": "Thu Nov 12 01:04:25 2009 +0100"
      },
      "committer": {
        "name": "Avi Kivity",
        "email": "avi@redhat.com",
        "time": "Thu Dec 03 09:32:25 2009 +0200"
      },
      "message": "KVM: x86: Add KVM_GET/SET_VCPU_EVENTS\n\nThis new IOCTL exports all yet user-invisible states related to\nexceptions, interrupts, and NMIs. Together with appropriate user space\nchanges, this fixes sporadic problems of vmsave/restore, live migration\nand system reset.\n\n[avi: future-proof abi by adding a flags field]\n\nSigned-off-by: Jan Kiszka \u003cjan.kiszka@siemens.com\u003e\nSigned-off-by: Avi Kivity \u003cavi@redhat.com\u003e\n"
    },
    {
      "commit": "afbcf7ab8d1bc8c2d04792f6d9e786e0adeb328d",
      "tree": "14320a1c768562139a550fd0c576d6d52829d9ec",
      "parents": [
        "cd5a2685de4a642fd0bd763e8c19711ef08dbe27"
      ],
      "author": {
        "name": "Glauber Costa",
        "email": "glommer@redhat.com",
        "time": "Fri Oct 16 15:28:36 2009 -0400"
      },
      "committer": {
        "name": "Avi Kivity",
        "email": "avi@redhat.com",
        "time": "Thu Dec 03 09:32:19 2009 +0200"
      },
      "message": "KVM: allow userspace to adjust kvmclock offset\n\nWhen we migrate a kvm guest that uses pvclock between two hosts, we may\nsuffer a large skew. This is because there can be significant differences\nbetween the monotonic clock of the hosts involved. When a new host with\na much larger monotonic time starts running the guest, the view of time\nwill be significantly impacted.\n\nSituation is much worse when we do the opposite, and migrate to a host with\na smaller monotonic clock.\n\nThis proposed ioctl will allow userspace to inform us what is the monotonic\nclock value in the source host, so we can keep the time skew short, and\nmore importantly, never goes backwards. Userspace may also need to trigger\nthe current data, since from the first migration onwards, it won\u0027t be\nreflected by a simple call to clock_gettime() anymore.\n\n[marcelo: future-proof abi with a flags field]\n[jan: fix KVM_GET_CLOCK by clearing flags field instead of checking it]\n\nSigned-off-by: Glauber Costa \u003cglommer@redhat.com\u003e\nSigned-off-by: Marcelo Tosatti \u003cmtosatti@redhat.com\u003e\nSigned-off-by: Avi Kivity \u003cavi@redhat.com\u003e\n"
    },
    {
      "commit": "ffde22ac53b6d6b1d7206f1172176a667eead778",
      "tree": "16ab77d364ba26928136e6d18463845941b6dd2c",
      "parents": [
        "94c30d9ca6fd00a69e367b91b6e13572c41938c5"
      ],
      "author": {
        "name": "Ed Swierk",
        "email": "eswierk@aristanetworks.com",
        "time": "Thu Oct 15 15:21:43 2009 -0700"
      },
      "committer": {
        "name": "Avi Kivity",
        "email": "avi@redhat.com",
        "time": "Thu Dec 03 09:32:18 2009 +0200"
      },
      "message": "KVM: Xen PV-on-HVM guest support\n\nSupport for Xen PV-on-HVM guests can be implemented almost entirely in\nuserspace, except for handling one annoying MSR that maps a Xen\nhypercall blob into guest address space.\n\nA generic mechanism to delegate MSR writes to userspace seems overkill\nand risks encouraging similar MSR abuse in the future.  Thus this patch\nadds special support for the Xen HVM MSR.\n\nI implemented a new ioctl, KVM_XEN_HVM_CONFIG, that lets userspace tell\nKVM which MSR the guest will write to, as well as the starting address\nand size of the hypercall blobs (one each for 32-bit and 64-bit) that\nuserspace has loaded from files.  When the guest writes to the MSR, KVM\ncopies one page of the blob from userspace to the guest.\n\nI\u0027ve tested this patch with a hacked-up version of Gerd\u0027s userspace\ncode, booting a number of guests (CentOS 5.3 i386 and x86_64, and\nFreeBSD 8.0-RC1 amd64) and exercising PV network and block devices.\n\n[jan: fix i386 build warning]\n[avi: future proof abi with a flags field]\n\nSigned-off-by: Ed Swierk \u003ceswierk@aristanetworks.com\u003e\nSigned-off-by: Jan Kiszka \u003cjan.kiszka@siemens.com\u003e\nSigned-off-by: Marcelo Tosatti \u003cmtosatti@redhat.com\u003e\nSigned-off-by: Avi Kivity \u003cavi@redhat.com\u003e\n"
    },
    {
      "commit": "5dadbfd64724c41716d4fc82df6f01b023d5b15d",
      "tree": "78dc2c620f4e0bd49d81e4ca9a01c208de800d50",
      "parents": [
        "88c808fd42b53a7e01a2ac3253ef31fef74cb5af"
      ],
      "author": {
        "name": "Avi Kivity",
        "email": "avi@redhat.com",
        "time": "Sun Aug 23 17:08:04 2009 +0300"
      },
      "committer": {
        "name": "Avi Kivity",
        "email": "avi@redhat.com",
        "time": "Thu Sep 10 10:46:55 2009 +0300"
      },
      "message": "KVM: Document KVM_CAP_IRQCHIP\n\nSigned-off-by: Avi Kivity \u003cavi@redhat.com\u003e\n"
    },
    {
      "commit": "9c1b96e34717d001873b603d85434aa78e730282",
      "tree": "d0390fdb24d8a5cce9f91fdb59067ab9659bb1cd",
      "parents": [
        "07420171593908406c3a59d6f884d426a921a5ea"
      ],
      "author": {
        "name": "Avi Kivity",
        "email": "avi@redhat.com",
        "time": "Tue Jun 09 12:37:58 2009 +0300"
      },
      "committer": {
        "name": "Avi Kivity",
        "email": "avi@redhat.com",
        "time": "Thu Sep 10 08:33:09 2009 +0300"
      },
      "message": "KVM: Document basic API\n\nDocument the basic API corresponding to the 2.6.22 release.\n\nSigned-off-by: Avi Kivity \u003cavi@redhat.com\u003e\n"
    }
  ]
}