{"push_id":615725924,"size":62,"distinct_size":0,"ref":"refs/heads/transactionless-incremental","head":"7053a44041a77179482dbacd45f6f854973cac16","before":"b589fc49ca60be6c20478c7771332e39ede3ee7d","commits":[{"sha":"054903a832b865eb5432d79b5c9d1e1ff31b58d7","author":{"email":"313afa09ce093b19ae1dd74f57c1ebd94508584c@linaro.org","name":"Peter Maydell"},"message":"Update version for v2.3.0-rc1 release\n\nSigned-off-by: Peter Maydell <peter.maydell@linaro.org>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/054903a832b865eb5432d79b5c9d1e1ff31b58d7"},{"sha":"8e27fc200457e3f2473d0069263774d4ba17bd85","author":{"email":"a4c2eeb85a7888d5bb7312ddbacc53a360bf0620@profitbricks.com","name":"Eduardo Otubo"},"message":"seccomp: update libseccomp version and remove arch restriction\n\nLibseccomp version updated to 2.2.0 and arch restriction to x86/x86_64\nis now removed. It's supposed to work on armv7l as well.\n\nRelated bug: https://bugs.launchpad.net/qemu/+bug/1363641\n\nSigned-off-by: Eduardo Otubo <eduardo.otubo@profitbricks.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/8e27fc200457e3f2473d0069263774d4ba17bd85"},{"sha":"8a5956ad6392f115521dad774055c737c49fb0dd","author":{"email":"69d3ebcf5ee4e7f05a50dc23cd96655b730804b4@redhat.com","name":"Paolo Bonzini"},"message":"rcu tests: fix compilation on 32-bit ppc\n\n32-bit PPC cannot do atomic operations on long long.  Inside the loops,\nwe are already using local counters that are summed at the end of\nthe run---with some exceptions (rcu_stress_count for rcutorture,\nn_nodes for test-rcu-list): fix them to use the same technique.\nFor test-rcu-list, remove the mostly unused member \"val\" from the\nlist.  Then, use a mutex to protect the global counts.\n\nPerformance does not matter there because every thread will only enter\nthe critical section once.\n\nRemaining uses of atomic instructions are for ints or pointers.\n\nReported-by: Andreas Faerber <afaerber@suse.de>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/8a5956ad6392f115521dad774055c737c49fb0dd"},{"sha":"3a5c76baf312d83cb77c8faa72c5f7a477effed0","author":{"email":"0bda901f34b59fdc0593dc5ef2b1790278d1dfd8@cmu.edu","name":"Gabriel L. Somlo"},"message":"fw_cfg: factor out initialization of FW_CFG_ID (rev. number)\n\nThe fw_cfg documentation says this of the revision key (0x0001, FW_CFG_ID):\n\n> A 32-bit little-endian unsigned int, this item is used as an interface\n> revision number, and is currently set to 1 by all QEMU architectures\n> which expose a fw_cfg device.\n\narm/virt doesn't.  It could be argued that that's an error in\n\"hw/arm/virt.c\"; on the other hand, all of the other fw_cfg providing\nboards set the interface version to 1 manually, despite the device\ncoming from the same, shared implementation. Therefore, instead of\nadding\n\n    fw_cfg_add_i32(fw_cfg, FW_CFG_ID, 1);\n\nto arm/virt, consolidate all such existing calls in the fw_cfg\ninitialization code.\n\nSigned-off-by: Gabriel Somlo <somlo@cmu.edu>\nMessage-Id: <1426789244-26318-1-git-send-email-somlo@cmu.edu>\nReviewed-by: Laszlo Ersek <lersek@redhat.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/3a5c76baf312d83cb77c8faa72c5f7a477effed0"},{"sha":"06b82e2d8ead4d1f9441dbf2b03c31369a8f27bd","author":{"email":"aa743a0aaec8f7d7a1f01442503957f4d7a2d634@gibson.dropbear.id.au","name":"David Gibson"},"message":"i6300esb: Correct endiannness\n\nThe IO operations for the i6300esb watchdog timer are marked as\nDEVICE_NATIVE_ENDIAN.  This is not correct, and - as a PCI device - should\nbe DEVICE_LITTLE_ENDIAN.\n\nThis allows i6300esb to work on ppc targets (yes, using an Intel ICH\nderived device on ppc is a bit odd, but the driver exists on the guest\nand there's no more obviously suitable watchdog device).\n\nSigned-off-by: David Gibson <david@gibson.dropbear.id.au>\nMessage-Id: <1427075508-12099-2-git-send-email-david@gibson.dropbear.id.au>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/06b82e2d8ead4d1f9441dbf2b03c31369a8f27bd"},{"sha":"4bc7b4d56657ebf75b986ad46e959cf7232ff26a","author":{"email":"aa743a0aaec8f7d7a1f01442503957f4d7a2d634@gibson.dropbear.id.au","name":"David Gibson"},"message":"i6300esb: Fix signed integer overflow\n\nIf the guest programs a sufficiently large timeout value an integer\noverflow can occur in i6300esb_restart_timer().  e.g. if the maximum\npossible timer preload value of 0xfffff is programmed then we end up with\nthe calculation:\n\ntimeout = get_ticks_per_sec() * (0xfffff << 15) / 33000000;\n\nget_ticks_per_sec() returns 1000000000 (10^9) giving:\n\n     10^9 * (0xfffff * 2^15) == 0x1dcd632329b000000 (65 bits)\n\nObviously the division by 33MHz brings it back under 64-bits, but the\noverflow has already occurred.\n\nSince signed integer overflow has undefined behaviour in C, in theory this\ncould be arbitrarily bad.  In practice, the overflowed value wraps around\nto something negative, causing the watchdog to immediately expire, killing\nthe guest, which is still fairly bad.\n\nThe bug can be triggered by running a Linux guest, loading the i6300esb\ndriver with parameter \"heartbeat=2046\" and opening /dev/watchdog.  The\nwatchdog will trigger as soon as the device is opened.\n\nThis patch corrects the problem by using muldiv64(), which effectively\nallows a 128-bit intermediate value between the multiplication and\ndivision.\n\nSigned-off-by: David Gibson <david@gibson.dropbear.id.au>\nMessage-Id: <1427075508-12099-3-git-send-email-david@gibson.dropbear.id.au>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/4bc7b4d56657ebf75b986ad46e959cf7232ff26a"},{"sha":"bdd459a00a206772185970efbc38c455dc43167e","author":{"email":"7f4ef24acb5fadd2d444c175ca9e12e09a0858ae@xilinx.com","name":"Peter Crosthwaite"},"message":"cpus: Don't kick un-realized cpus.\n\nfollowing a464982499b2f637f6699e3d03e0a9d2e0b5288b, it's now possible for\nthere to be attempts to take the BQL before CPUs have been realized in\ncases where a machine model inits peripherals before the first CPU.\n\nBQL lock aquisition kicks the first_cpu, leading to a segfault if this\nhappens pre-realize. Guard the CPU kick routine to perform no action for\na CPU that doesn't exist or doesn't have a thread yet.\n\nThere was a fix to this with commit\n6b49809c597331803ea941eadda813e5bb4e8fe2, but the check there misses\nthe case where the CPU has been inited and not realized. Strengthen the\ncheck to make sure that the first_cpu has a thread (i.e. it is\nrealized) before allowing the kick.\n\nSigned-off-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>\nMessage-Id: <1427107689-6946-1-git-send-email-peter.crosthwaite@xilinx.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/bdd459a00a206772185970efbc38c455dc43167e"},{"sha":"16578c6ffe8c4ee5207ccb9b0c994c1b18bb322d","author":{"email":"69d3ebcf5ee4e7f05a50dc23cd96655b730804b4@redhat.com","name":"Paolo Bonzini"},"message":"megasas: use PCI DMA APIs\n\nIt is wrong to use address_space_memory directly, because there could be an\nIOMMU in the middle.\n\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/16578c6ffe8c4ee5207ccb9b0c994c1b18bb322d"},{"sha":"0dc40f28518dee8aa95abd330a53f06179e71995","author":{"email":"69d3ebcf5ee4e7f05a50dc23cd96655b730804b4@redhat.com","name":"Paolo Bonzini"},"message":"vmw_pvscsi: use PCI DMA APIs\n\nIt is wrong to use address_space_memory directly, because there could be an\nIOMMU in the middle.  Passing the entire PVSCSIRingInfo to RS_GET_FIELD\nand RS_SET_FIELD makes it easy to go back to the PVSCSIState.\n\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/0dc40f28518dee8aa95abd330a53f06179e71995"},{"sha":"78fa62ff1bc0d66f0115b7147c4eb260ad22022a","author":{"email":"5d00b6b660f20fb41305186c34c40973ec5cb35b@redhat.com","name":"Markus Armbruster"},"message":"nbd: Fix up comment after commit e140177\n\nSigned-off-by: Markus Armbruster <armbru@redhat.com>\nMessage-Id: <1427271528-11624-1-git-send-email-armbru@redhat.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/78fa62ff1bc0d66f0115b7147c4eb260ad22022a"},{"sha":"c167e2e7eda609bbbb58650c1b82e8168106e40e","author":{"email":"8d4c780fcfdc41841e5070f4c43da8958ba6aec0@weilnetz.de","name":"Stefan Weil"},"message":"acpi: Add missing GCC_FMT_ATTR to local function\n\nThis fixes these gcc warnings (not enabled in default build):\n\nhw/acpi/aml-build.c:83:5: warning:\n function might be possible candidate for ‘gnu_printf’ format attribute [-Wsuggest-attribute=format]\nhw/acpi/aml-build.c:88:5: warning:\n function might be possible candidate for ‘gnu_printf’ format attribute [-Wsuggest-attribute=format]\n\nCc: Michael S. Tsirkin <mst@redhat.com>\nSigned-off-by: Stefan Weil <sw@weilnetz.de>\nReviewed-by: Michael S. Tsirkin <mst@redhat.com>\nSigned-off-by: Michael S. Tsirkin <mst@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/c167e2e7eda609bbbb58650c1b82e8168106e40e"},{"sha":"7976a6d23151c780474bdac106f3cf1343a2d6ca","author":{"email":"255103e50249e3d658441816e0597170ebfc16ef@redhat.com","name":"Michael S. Tsirkin"},"message":"virtio-serial: fix virtio config size\n\ncommit 9b70c1790acacae54d559d38ca69186a85040bb8\n    virtio-serial: switch to standard-headers\n\nchanges virtio_console_config size from 8 to 12 bytes:\nit adds an optional 4 byte emerg_wr field.\n\nAs this crosses a power of two boundary, this changes the PCI BAR size,\nwhich breaks migration compatibility with old qemu machine types.\nIt's probably a problem for other transports as well.\n\nAs a temporary fix, as we don't yet support this new field anyway,\nsimply make the config size smaller at init time.\n\nLong terms we probably want something along the lines\nof virtio_net_set_config_size.\n\nReported-by: Cole Robinson <crobinso@redhat.com>\nSigned-off-by: Michael S. Tsirkin <mst@redhat.com>\nTested-by: Cole Robinson <crobinso@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/7976a6d23151c780474bdac106f3cf1343a2d6ca"},{"sha":"7e0e736ecdfeac6d3517513d3a702304e4f6cf59","author":{"email":"808efd45667dbd241e4e026b5673172419ecb43e@redhat.com","name":"Jason Wang"},"message":"virtio-net: validate backend queue numbers against bus limitation\n\nWe don't validate the backend queue numbers against bus limitation,\nthis will easily crash qemu if it exceeds the limitation which will\nhit the abort() in virtio_del_queue(). An example is trying to\nstarting a virtio-net device with 256 queues. E.g:\n\n./qemu-system-x86_64 -netdev tap,id=hn0,queues=256 -device\nvirtio-net-pci,netdev=hn0\n\nFixing this by doing the validation and fail early.\n\nCc: Michael S. Tsirkin <mst@redhat.com>\nCc: qemu-stable <qemu-stable@nongnu.org>\nSigned-off-by: Jason Wang <jasowang@redhat.com>\nReviewed-by: Michael S. Tsirkin <mst@redhat.com>\nSigned-off-by: Michael S. Tsirkin <mst@redhat.com>\nReviewed-by: Stefan Hajnoczi <stefanha@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/7e0e736ecdfeac6d3517513d3a702304e4f6cf59"},{"sha":"1d5bfde1b978b57156d851d140b99eac8b2adbe4","author":{"email":"a00b27378a09822d5638cdfb8c2e7ccc36d74c56@dmllr.de","name":"Dirk Müller"},"message":"m68k: memory: Replace memory_region_init_ram with memory_region_allocate_system_memory\n\nCommit 0b183fc871:\"memory: move mem_path handling to\nmemory_region_allocate_system_memory\" split memory_region_init_ram and\nmemory_region_init_ram_from_file. Also it moved mem-path handling a step\nup from memory_region_init_ram to memory_region_allocate_system_memory.\n\nTherefore for any board that uses memory_region_init_ram directly,\n-mem-path is not supported.\n\nFix this by replacing memory_region_init_ram with\nmemory_region_allocate_system_memory.\n\nSigned-off-by: Dirk Mueller <dmueller@suse.com>\nMessage-Id: <CAL5wTH6X-GsT1AA8kEtP_e7oZWGZgi=fCcDfSs3wLgJN30DbUw@mail.gmail.com>\nReviewed-by: Andreas Färber <afaerber@suse.de>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/1d5bfde1b978b57156d851d140b99eac8b2adbe4"},{"sha":"6a926fbc6fff58598cce9404019204090a8e8361","author":{"email":"a00b27378a09822d5638cdfb8c2e7ccc36d74c56@dmllr.de","name":"Dirk Müller"},"message":"mips: memory: Replace memory_region_init_ram with memory_region_allocate_system_memory\n\nCommit 0b183fc871:\"memory: move mem_path handling to\nmemory_region_allocate_system_memory\" split memory_region_init_ram and\nmemory_region_init_ram_from_file. Also it moved mem-path handling a step\nup from memory_region_init_ram to memory_region_allocate_system_memory.\n\nTherefore for any board that uses memory_region_init_ram directly,\n-mem-path is not supported.\n\nFix this by replacing memory_region_init_ram with\nmemory_region_allocate_system_memory.\n\nSigned-off-by: Dirk Mueller <dmueller@suse.com>\nMessage-Id: <CAL5wTH4-=HJUvwBu+2o6jGanJesJOyNf3sL8-5+d_-6C3cWBfA@mail.gmail.com>\nReviewed-by: Andreas Färber <afaerber@suse.de>\nAcked-by: Leon Alrae <leon.alrae@imgtec.com>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/6a926fbc6fff58598cce9404019204090a8e8361"},{"sha":"8e7ba4ed3a0b68ab35736c7859fd950f6705e0cf","author":{"email":"a00b27378a09822d5638cdfb8c2e7ccc36d74c56@dmllr.de","name":"Dirk Müller"},"message":"sparc: memory: Replace memory_region_init_ram with memory_region_allocate_system_memory\n\nCommit 0b183fc871:\"memory: move mem_path handling to\nmemory_region_allocate_system_memory\" split memory_region_init_ram and\nmemory_region_init_ram_from_file. Also it moved mem-path handling a step\nup from memory_region_init_ram to memory_region_allocate_system_memory.\n\nTherefore for any board that uses memory_region_init_ram directly,\n-mem-path is not supported.\n\nFix this by replacing memory_region_init_ram with\nmemory_region_allocate_system_memory.\n\nSigned-off-by: Dirk Mueller <dmueller@suse.com>\nMessage-Id: <CAL5wTH7o8uA59Ep0n41i0M19VFWa73n9m172j2W3fjz6=PSVBA@mail.gmail.com>\nReviewed-by: Andreas Färber <afaerber@suse.de>\nSigned-off-by: Paolo Bonzini <pbonzini@redhat.com>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/8e7ba4ed3a0b68ab35736c7859fd950f6705e0cf"},{"sha":"0d2f830255c758240dccbeb732a2c21f4eea995c","author":{"email":"ac1fc56530d7d037e1ea666f130daca22d72f964@ozlabs.ru","name":"Alexey Kardashevskiy"},"message":"pseries: Update SLOF firmware image to qemu-slof-20150313\n\nThe changelog is:\n  > virtio: Fix vring allocation\n  > helpers: Fix SLOF_alloc_mem_aligned to meet callers expectation\n  > Set default palette according to \"16-color Text Extension\" document\n  > Fix rectangle drawing functions to work also with higher bit depths\n  > Fix the x86emu patch file\n  > Silence compiler warning when building the biosemu\n  > Use device-type Forth word to set up the corresponding property\n  > Improve /openprom node\n  > pci-properties: Remove redundant call to device-type\n  > cas: reconfigure memory nodes\n  > pci: use 64bit bar ranges\n\nSigned-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>\nSigned-off-by: Alexander Graf <agraf@suse.de>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/0d2f830255c758240dccbeb732a2c21f4eea995c"},{"sha":"4c56440d6754b45c2d82969e029a3c2a72864b30","author":{"email":"8d4c780fcfdc41841e5070f4c43da8958ba6aec0@weilnetz.de","name":"Stefan Weil"},"message":"spapr: Add missing checks for NULL pointers and report failures\n\nThis fixes potential runtime crashes and two warnings from Coverity.\n\nThe new error message does not add  a prefix \"qemu:\" because that is\nalready done in function hw_error. It also starts with an uppercase\nletter because that seems to be the mostly used form.\n\nSigned-off-by: Stefan Weil <sw@weilnetz.de>\n[agraf: fix typo]\nSigned-off-by: Alexander Graf <agraf@suse.de>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/4c56440d6754b45c2d82969e029a3c2a72864b30"},{"sha":"fda276c7aafe2bfc9df808e61abd25cb834a0254","author":{"email":"ac1fc56530d7d037e1ea666f130daca22d72f964@ozlabs.ru","name":"Alexey Kardashevskiy"},"message":"target-ppc: Remove POWER5+ v0.0 that never existed\n\nIBM uses low 16bits to specify the chip version of a POWER CPU.\nSo there has never been an actual silicon with PVR = 0x003B0000.\nThe first silicon would have PVR 0x003B0100 but it is very unlikely\nto find it in any machine shipped to any customer as it was too raw.\n\nThis removes CPU_POWERPC_POWER5P_v00 definition and changes\nPOWER5+ and POWERgs aliases (which are synonyms) to point to\nPOWER5+_v2.1 which can still be found in real machines.\n\nSigned-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>\nReviewed-by: Andreas Färber <afaerber@suse.de>\n[agraf: fix commit message]\nSigned-off-by: Alexander Graf <agraf@suse.de>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/fda276c7aafe2bfc9df808e61abd25cb834a0254"},{"sha":"5b2128d27051fe036ac36e8e860e72490b27a369","author":{"email":"3ad82b0c937b9aa51276120cedd545efc822be04@suse.de","name":"Alexander Graf"},"message":"PPC: pseries: Implement boot once=foo\n\nOn sPAPR we haven't supported boot once ever since it emerged, but\nrecently grew need for it. This patch implements boot once logic\nto it.\n\nWhile at it, we also move to the new bootdevice handling that got\nintroduced to the tree recently.\n\nReported-by: Dinar Valeev <dvaleev@suse.de>\nSigned-off-by: Alexander Graf <agraf@suse.de>","distinct":false,"url":"https://api.github.com/repos/jnsnow/qemu/commits/5b2128d27051fe036ac36e8e860e72490b27a369"}]}