[Qemu-commits] [qemu/qemu] 1aab16: cpu-exec: unify icount_decr and tcg_exit_req

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: 1aab16c28a0232d898d6f56f5a56019472296ee7
      
https://github.com/qemu/qemu/commit/1aab16c28a0232d898d6f56f5a56019472296ee7
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-02-22 (Wed, 22 Feb 2017)

  Changed paths:
    M cpu-exec.c
    M include/exec/gen-icount.h
    M include/qom/cpu.h
    M qom/cpu.c
    M tcg/tcg.h
    M translate-all.c
    M translate-common.c

  Log Message:
  -----------
  cpu-exec: unify icount_decr and tcg_exit_req

The icount interrupt flag and tcg_exit_req serve almost the same
purpose, let's make them completely the same.

The former TB_EXIT_REQUESTED and TB_EXIT_ICOUNT_EXPIRED cases are
unified, since we can distinguish them from the value of the
interrupt flag.

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: cfb2d02be9413d45b30ed6d8e38800250b6b4b48
      
https://github.com/qemu/qemu/commit/cfb2d02be9413d45b30ed6d8e38800250b6b4b48
  Author: Pavel Dovgalyuk <address@hidden>
  Date:   2017-02-24 (Fri, 24 Feb 2017)

  Changed paths:
    M cpu-exec.c

  Log Message:
  -----------
  replay: check icount in cpu exec loop

This patch adds check to break cpu loop when icount expires without
setting the TB_EXIT_ICOUNT_EXPIRED flag. It happens when there is no
available translated blocks and all instructions were executed.
In icount replay mode unnecessary tb_find will be called (which may
cause an exception) and execution will be non-deterministic.
Because cpu_loop_exec_tb cannot longjmp anymore, we can remove
the anticipated call to align_clocks in cpu_loop_exec_tb, as
well as the SyncClocks *sc argument.

Signed-off-by: Pavel Dovgalyuk <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Signed-off-by: Pavel Dovgalyuk <address@hidden>


  Commit: 55ac0a9bf4e1b1adfc7d73586a7aa085f58c9851
      
https://github.com/qemu/qemu/commit/55ac0a9bf4e1b1adfc7d73586a7aa085f58c9851
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-02-24 (Fri, 24 Feb 2017)

  Changed paths:
    M cpu-exec.c

  Log Message:
  -----------
  cpu-exec: remove unnecessary check of cpu->exit_request

The cpu->exit_request check in cpu_loop_exec_tb is unnecessary,
because cpu->tcg_exit_req is always set after cpu->exit_request.
So let the TB exit and we will pick up the exit request later
in cpu_handle_interrupt.

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: 30f3dda24b2a4cd30f8fbf984ab08ef08eaf5020
      
https://github.com/qemu/qemu/commit/30f3dda24b2a4cd30f8fbf984ab08ef08eaf5020
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M cpu-exec.c
    M include/exec/gen-icount.h
    M include/qom/cpu.h
    M qom/cpu.c
    M tcg/tcg.h
    M translate-all.c
    M translate-common.c

  Log Message:
  -----------
  Merge branch 'icount-update' into HEAD

Merge the original development branch due to breakage caused by the
MTTCG merge.

Conflicts:
        cpu-exec.c
        translate-common.c

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: d98d407234713d05b77114237f839c43a8152089
      
https://github.com/qemu/qemu/commit/d98d407234713d05b77114237f839c43a8152089
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M cpus.c
    R include/qemu/compatfd.h
    M include/qemu/osdep.h
    M util/compatfd.c
    M util/main-loop.c
    M util/oslib-posix.c

  Log Message:
  -----------
  cpus: remove ugly cast on sigbus_handler

The cast is there because sigbus_handler is invoked via sigfd_handler.
But it feels just wrong to use struct qemu_signalfd_siginfo in the
prototype of a function that is passed to sigaction.

Instead, do a simple-minded conversion of qemu_signalfd_siginfo to
siginfo_t.

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: 20e0ff59a96e72dc6785be31db23ed7030781d45
      
https://github.com/qemu/qemu/commit/20e0ff59a96e72dc6785be31db23ed7030781d45
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M target/i386/kvm.c

  Log Message:
  -----------
  KVM: x86: cleanup SIGBUS handlers

This patch should have no semantic change.

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: a16fc07ebd58da51d5e1c2928069879c40a26f59
      
https://github.com/qemu/qemu/commit/a16fc07ebd58da51d5e1c2928069879c40a26f59
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M cpus.c
    M include/qemu/osdep.h
    M target/i386/kvm.c

  Log Message:
  -----------
  cpus: reorganize signal handling code

Move the KVM "eat signals" code under CONFIG_LINUX, in preparation
for moving it to kvm-all.c; reraise non-MCE SIGBUS immediately,
without passing it to KVM.

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: 4d39892cca86a9162beaa3944057d118ef42edcd
      
https://github.com/qemu/qemu/commit/4d39892cca86a9162beaa3944057d118ef42edcd
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M include/sysemu/kvm.h
    M kvm-all.c
    M target/arm/kvm.c
    M target/i386/kvm.c
    M target/mips/kvm.c
    M target/ppc/kvm.c
    M target/s390x/kvm.c

  Log Message:
  -----------
  KVM: remove kvm_arch_on_sigbus

Build it on kvm_arch_on_sigbus_vcpu instead.  They do the same
for "action optional" SIGBUSes, and the main thread should never get
"action required" SIGBUSes because it blocks the signal.

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: 2ae41db262e02743b27719fe085e749d957613c0
      
https://github.com/qemu/qemu/commit/2ae41db262e02743b27719fe085e749d957613c0
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M cpus.c
    M include/sysemu/kvm.h
    M kvm-all.c
    M target/arm/kvm.c
    M target/i386/kvm.c
    M target/mips/kvm.c
    M target/ppc/kvm.c
    M target/s390x/kvm.c

  Log Message:
  -----------
  KVM: do not use sigtimedwait to catch SIGBUS

Call kvm_on_sigbus_vcpu asynchronously from the VCPU thread.
Information for the SIGBUS can be stored in thread-local variables
and processed later in kvm_cpu_exec.

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: 18268b6016930efe76c77ae590e244d42d9671ea
      
https://github.com/qemu/qemu/commit/18268b6016930efe76c77ae590e244d42d9671ea
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M cpus.c
    M include/sysemu/kvm.h
    M kvm-all.c
    M kvm-stub.c

  Log Message:
  -----------
  KVM: move SIG_IPI handling to kvm-all.c

This lets us remove a bunch of CONFIG_LINUX defines.

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: c5c6679d37547a2a5125e257529fcd3fd095b88f
      
https://github.com/qemu/qemu/commit/c5c6679d37547a2a5125e257529fcd3fd095b88f
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M kvm-all.c

  Log Message:
  -----------
  kvm: use atomic_read/atomic_set to access cpu->exit_request

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: cf0f7cf903073f9dd9979dd33d52618b384ac2cb
      
https://github.com/qemu/qemu/commit/cf0f7cf903073f9dd9979dd33d52618b384ac2cb
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M kvm-all.c

  Log Message:
  -----------
  KVM: use KVM_CAP_IMMEDIATE_EXIT

The purpose of the KVM_SET_SIGNAL_MASK API is to let userspace "kick"
a VCPU out of KVM_RUN through a POSIX signal.  A signal is attached
to a dummy signal handler; by blocking the signal outside KVM_RUN and
unblocking it inside, this possible race is closed:
     VCPU thread                     service thread
   --------------------------------------------------------------
  check flag
                                    set flag
                                    raise signal
  (signal handler does nothing)
  KVM_RUN

However, one issue with KVM_SET_SIGNAL_MASK is that it has to take
tsk->sighand->siglock on every KVM_RUN.  This lock is often on a
remote NUMA node, because it is on the node of a thread's creator.
Taking this lock can be very expensive if there are many userspace
exits (as is the case for SMP Windows VMs without Hyper-V reference
time counter).

KVM_CAP_IMMEDIATE_EXIT provides an alternative, where the flag is
placed directly in kvm_run so that KVM can see it:
     VCPU thread                     service thread
   --------------------------------------------------------------
                                    raise signal
  signal handler
    set run->immediate_exit
  KVM_RUN
    check run->immediate_exit

The previous patches changed QEMU so that the only blocked signal is
SIG_IPI, so we can now stop using KVM_SET_SIGNAL_MASK and sigtimedwait
if KVM_CAP_IMMEDIATE_EXIT is available.

On a 14-VCPU guest, an "inl" operation goes down from 30k to 6k on
an unlocked (no BQL) MemoryRegion, or from 30k to 15k if the BQL
is involved.

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: c3e31eaa21bc038c146cb196f7762a972eb9de5b
      
https://github.com/qemu/qemu/commit/c3e31eaa21bc038c146cb196f7762a972eb9de5b
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M scripts/kvm/vmxcap

  Log Message:
  -----------
  vmxcap: port to Python 3

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: 025533f6eeb4751ee6d8330a505d47a1128322d1
      
https://github.com/qemu/qemu/commit/025533f6eeb4751ee6d8330a505d47a1128322d1
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M scripts/kvm/vmxcap

  Log Message:
  -----------
  vmxcap: update for September 2016 SDM

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: e8ed97a6478f55dde54f0188a54e094a1caa7965
      
https://github.com/qemu/qemu/commit/e8ed97a6478f55dde54f0188a54e094a1caa7965
  Author: Anton Nefedov <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M qapi-schema.json
    M target/i386/cpu.c
    M vl.c

  Log Message:
  -----------
  qapi: flatten GuestPanicInformation union

Signed-off-by: Anton Nefedov <address@hidden>
Signed-off-by: Denis V. Lunev <address@hidden>
CC: Paolo Bonzini <address@hidden>
CC: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: 11953be792998c43bf2cad4ad3deaeaeaf89dbb4
      
https://github.com/qemu/qemu/commit/11953be792998c43bf2cad4ad3deaeaeaf89dbb4
  Author: Anton Nefedov <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M qapi/event.json

  Log Message:
  -----------
  qmp-events: fix GUEST_PANICKED description formatting

Signed-off-by: Anton Nefedov <address@hidden>
Signed-off-by: Denis V. Lunev <address@hidden>
CC: Paolo Bonzini <address@hidden>
CC: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: c99a29e702528698c0ce2590f06ca7ff239f7c39
      
https://github.com/qemu/qemu/commit/c99a29e702528698c0ce2590f06ca7ff239f7c39
  Author: Yongji Xie <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M include/exec/cpu-common.h
    M memory.c

  Log Message:
  -----------
  memory: Introduce DEVICE_HOST_ENDIAN for ram device

At the moment ram device's memory regions are DEVICE_NATIVE_ENDIAN. It's
incorrect. This memory region is backed by a MMIO area in host, so the
uint64_t data that MemoryRegionOps read from/write to this area should be
host-endian rather than target-endian. Hence, current code does not work
when target and host endianness are different which is the most common case
on PPC64. To fix it, this introduces DEVICE_HOST_ENDIAN for the ram device.

This has been tested on PPC64 BE/LE host/guest in all possible combinations
including TCG.

Suggested-by: Paolo Bonzini <address@hidden>
Signed-off-by: Yongji Xie <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: f6f99b48087696812241d6c54f97444de6364c24
      
https://github.com/qemu/qemu/commit/f6f99b48087696812241d6c54f97444de6364c24
  Author: Hervé Poussineau <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M vl.c

  Log Message:
  -----------
  vl: disable default cdrom when using explicitely scsi-hd

In commit af6bf1328ef90fae617857c02697e0174b84d596 (May 2011),
ide-hd, ide-cd and scsi-cd have been added to disable default cdrom,
"or else you can't put one on secondary master without -nodefaults".

Make it the same for scsi-hd, so you can put one on scsi-id 2 without
using -nodefaults.
scsi-hd has probably been forgotten, as it has been added in the
preceding commit (b443ae67130d32ad06b06fc9aa6d04d05ccd93ce).

Affected users are the ones using a machine with SCSI devices and start QEMU
with -device scsi-hd but without -device scsi-cd or -cdrom
In that case, the default cdrom device will disappear instead of being empty.

Signed-off-by: Hervé Poussineau <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: f20e6f8cd42acae9a130b9e0bcd47b0d7e39f253
      
https://github.com/qemu/qemu/commit/f20e6f8cd42acae9a130b9e0bcd47b0d7e39f253
  Author: Li Qiang <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M spice-qemu-char.c

  Log Message:
  -----------
  spice-char: fix segfault in char_spice_finalize

In 'qemu_chr_open_spice_vmc' if the 'psubtype' is NULL, it will
call 'char_spice_finalize'. But as the SpiceChardev is not inserted
in the 'spice_chars' list, the 'QLIST_REMOVE' will cause a segfault.
Add a detect to avoid it.

Signed-off-by: Li Qiang <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Marc-André Lureau <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Signed-off-by: Li Qiang <address@hidden>


  Commit: fc3a1fd74fac0e3233060aaaf923fe8ec104b48f
      
https://github.com/qemu/qemu/commit/fc3a1fd74fac0e3233060aaaf923fe8ec104b48f
  Author: Dr. David Alan Gilbert <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M include/hw/i386/pc.h
    M target/i386/cpu.c
    M target/i386/cpu.h
    M target/i386/kvm.c

  Log Message:
  -----------
  x86: Work around SMI migration breakages

Migration from a 2.3.0 qemu results in a reboot on the receiving QEMU
due to a disagreement about SM (System management) interrupts.

2.3.0 didn't have much SMI support, but it did set CPU_INTERRUPT_SMI
and this gets into the migration stream, but on 2.3.0 it
never got delivered.

~2.4.0 SMI interrupt support was added but was broken - so
that when a 2.3.0 stream was received it cleared the CPU_INTERRUPT_SMI
but never actually caused an interrupt.

The SMI delivery was recently fixed by 68c6efe07a, but the
effect now is that an incoming 2.3.0 stream takes the interrupt it
had flagged but it's bios can't actually handle it(I think
partly due to the original interrupt not being taken during boot?).
The consequence is a triple(?) fault and a reboot.

Tested from:
  2.3.1 -M 2.3.0
  2.7.0 -M 2.3.0
  2.8.0 -M 2.3.0
  2.8.0 -M 2.8.0

This corresponds to RH bugzilla entry 1420679.

Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: 377a07aa0d1617736289bfa9a9cbdc73de4e6542
      
https://github.com/qemu/qemu/commit/377a07aa0d1617736289bfa9a9cbdc73de4e6542
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M memory.c

  Log Message:
  -----------
  memory: show region offset and ROM/RAM type in "info mtree -f"

"info mtree -f" output is currently hard to use for large RAM regions, because
there is no hint as to what part of the region is being mapped.  Add the offset
if it is nonzero.

Secondly, FlatView has a readonly field, that can override the MemoryRegion
in the presence of aliases.  Take it into account.

Together, with this patch this:

address-space (flat view): KVM-SMRAM
  0000000000000000-00000000000bffff (prio 0, ram): pc.ram
  00000000000c0000-00000000000c9fff (prio 0, ram): pc.ram
  00000000000ca000-00000000000ccfff (prio 0, ram): pc.ram
  00000000000cd000-00000000000ebfff (prio 0, ram): pc.ram
  00000000000ec000-00000000000effff (prio 0, ram): pc.ram
  00000000000f0000-00000000000fffff (prio 0, ram): pc.ram
  0000000000100000-00000000bfffffff (prio 0, ram): pc.ram
  00000000fd000000-00000000fdffffff (prio 1, ram): vga.vram
  00000000febc0000-00000000febdffff (prio 1, i/o): e1000-mmio
  00000000febf0400-00000000febf041f (prio 0, i/o): vga ioports remapped
  00000000febf0500-00000000febf0515 (prio 0, i/o): bochs dispi interface
  00000000febf0600-00000000febf0607 (prio 0, i/o): qemu extended regs
  00000000fec00000-00000000fec00fff (prio 0, i/o): kvm-ioapic
  00000000fed00000-00000000fed003ff (prio 0, i/o): hpet
  00000000fee00000-00000000feefffff (prio 4096, i/o): kvm-apic-msi
  00000000fffc0000-00000000ffffffff (prio 0, rom): pc.bios
  0000000100000000-000000013fffffff (prio 0, ram): pc.ram

becomes this:

address-space (flat view): KVM-SMRAM
  0000000000000000-00000000000bffff (prio 0, ram): pc.ram
  00000000000c0000-00000000000c9fff (prio 0, rom): pc.ram @00000000000c0000
  00000000000ca000-00000000000ccfff (prio 0, ram): pc.ram @00000000000ca000
  00000000000cd000-00000000000ebfff (prio 0, rom): pc.ram @00000000000cd000
  00000000000ec000-00000000000effff (prio 0, ram): pc.ram @00000000000ec000
  00000000000f0000-00000000000fffff (prio 0, rom): pc.ram @00000000000f0000
  0000000000100000-00000000bfffffff (prio 0, ram): pc.ram @0000000000100000
  00000000fd000000-00000000fdffffff (prio 1, ram): vga.vram
  00000000febc0000-00000000febdffff (prio 1, i/o): e1000-mmio
  00000000febf0400-00000000febf041f (prio 0, i/o): vga ioports remapped
  00000000febf0500-00000000febf0515 (prio 0, i/o): bochs dispi interface
  00000000febf0600-00000000febf0607 (prio 0, i/o): qemu extended regs
  00000000fec00000-00000000fec00fff (prio 0, i/o): kvm-ioapic
  00000000fed00000-00000000fed003ff (prio 0, i/o): hpet
  00000000fee00000-00000000feefffff (prio 4096, i/o): kvm-apic-msi
  00000000fffc0000-00000000ffffffff (prio 0, rom): pc.bios
  0000000100000000-000000013fffffff (prio 0, ram): pc.ram @00000000c0000000

This should make it easier to understand what's going on.

Cc: Peter Xu <address@hidden>
Cc: "William Tambe" <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: f6eb0b319e4bad3d01d74d71e3a6cf40f0ede720
      
https://github.com/qemu/qemu/commit/f6eb0b319e4bad3d01d74d71e3a6cf40f0ede720
  Author: Paolo Bonzini <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M block/iscsi.c

  Log Message:
  -----------
  iscsi: fix missing unlock

Reported by Coverity.

Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: 5febe7671f5ec0a6842d64edfb920feb7bbb5f1e
      
https://github.com/qemu/qemu/commit/5febe7671f5ec0a6842d64edfb920feb7bbb5f1e
  Author: Peter Maydell <address@hidden>
  Date:   2017-03-03 (Fri, 03 Mar 2017)

  Changed paths:
    M block/iscsi.c
    M cpu-exec.c
    M cpus.c
    M include/exec/cpu-common.h
    M include/exec/gen-icount.h
    M include/hw/i386/pc.h
    R include/qemu/compatfd.h
    M include/qemu/osdep.h
    M include/qom/cpu.h
    M include/sysemu/kvm.h
    M kvm-all.c
    M kvm-stub.c
    M memory.c
    M qapi-schema.json
    M qapi/event.json
    M qom/cpu.c
    M scripts/kvm/vmxcap
    M spice-qemu-char.c
    M target/arm/kvm.c
    M target/i386/cpu.c
    M target/i386/cpu.h
    M target/i386/kvm.c
    M target/mips/kvm.c
    M target/ppc/kvm.c
    M target/s390x/kvm.c
    M tcg/tcg.h
    M translate-all.c
    M translate-common.c
    M util/compatfd.c
    M util/main-loop.c
    M util/oslib-posix.c
    M vl.c

  Log Message:
  -----------
  Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging

* kernel header update (requested by David and Vijay)
* GuestPanicInformation fixups (Anton)
* record/replay icount fixes (Pavel)
* cpu-exec cleanup, unification of icount_decr with tcg_exit_req (me)
* KVM_CAP_IMMEDIATE_EXIT support (me)
* vmxcap update (me)
* iscsi locking fix (me)
* VFIO ram device fix (Yongji)
* scsi-hd vs. default CD-ROM (Hervé)
* SMI migration fix (Dave)
* spice-char segfault (Li Qiang)
* improved "info mtree -f" (me)

# gpg: Signature made Fri 03 Mar 2017 15:43:04 GMT
# gpg:                using RSA key 0xBFFBD25F78C7AE83
# gpg: Good signature from "Paolo Bonzini <address@hidden>"
# gpg:                 aka "Paolo Bonzini <address@hidden>"
# Primary key fingerprint: 46F5 9FBD 57D6 12E7 BFD4  E2F7 7E15 100C CD36 69B1
#      Subkey fingerprint: F133 3857 4B66 2389 866C  7682 BFFB D25F 78C7 AE83

* remotes/bonzini/tags/for-upstream: (21 commits)
  iscsi: fix missing unlock
  memory: show region offset and ROM/RAM type in "info mtree -f"
  x86: Work around SMI migration breakages
  spice-char: fix segfault in char_spice_finalize
  vl: disable default cdrom when using explicitely scsi-hd
  memory: Introduce DEVICE_HOST_ENDIAN for ram device
  qmp-events: fix GUEST_PANICKED description formatting
  qapi: flatten GuestPanicInformation union
  vmxcap: update for September 2016 SDM
  vmxcap: port to Python 3
  KVM: use KVM_CAP_IMMEDIATE_EXIT
  kvm: use atomic_read/atomic_set to access cpu->exit_request
  KVM: move SIG_IPI handling to kvm-all.c
  KVM: do not use sigtimedwait to catch SIGBUS
  KVM: remove kvm_arch_on_sigbus
  cpus: reorganize signal handling code
  KVM: x86: cleanup SIGBUS handlers
  cpus: remove ugly cast on sigbus_handler
  cpu-exec: remove unnecessary check of cpu->exit_request
  replay: check icount in cpu exec loop
  ...

Signed-off-by: Peter Maydell <address@hidden>


Compare: https://github.com/qemu/qemu/compare/5b10b94bd532...5febe7671f5e