[Qemu-commits] [qemu/qemu] fe39a4: migration: fix missing assignment for has_x_checkp...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: fe39a4d44004408b8c847151191f1948a4aa6570
      
https://github.com/qemu/qemu/commit/fe39a4d44004408b8c847151191f1948a4aa6570
  Author: zhanghailiang <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M hmp.c
    M migration/migration.c

  Log Message:
  -----------
  migration: fix missing assignment for has_x_checkpoint_delay

We forgot to assign true to params->has_x_checkpoint_delay parameter
in qmp_query_migrate_parameters.

Without this, qmp command 'query-migrate-parameters' doesn't show the
default value for x-checkpoint-delay option.

This also fixes the fact that HMP was relying on unspecified behavior by
reading x_checkpoint_delay without checking has_x_checkpoint_delay.

Signed-off-by: zhanghailiang <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Signed-off-by: Juan Quintela <address@hidden>


  Commit: 6d57b4c0008ef4b51b149cfd1eb3b058be623e5b
      
https://github.com/qemu/qemu/commit/6d57b4c0008ef4b51b149cfd1eb3b058be623e5b
  Author: Halil Pasic <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M tests/test-vmstate.c

  Log Message:
  -----------
  tests/test-vmstate.c: add save_buffer util func

Let us de-duplicate some code by introducing an utility function for
saving a chunk of bytes (used when testing load based on wire).

Signed-off-by: Halil Pasic <address@hidden>
Reviewed-by: Guenther Hutzl <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Signed-off-by: Juan Quintela <address@hidden>


  Commit: 8cc49f0302ff23353034b6f9cbf4e5d778239a3d
      
https://github.com/qemu/qemu/commit/8cc49f0302ff23353034b6f9cbf4e5d778239a3d
  Author: Halil Pasic <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M tests/test-vmstate.c

  Log Message:
  -----------
  tests/test-vmstate.c: add array of pointer to struct

Increase test coverage by adding tests for the macro
VMSTATE_ARRAY_OF_POINTER_TO_STRUCT.

Signed-off-by: Halil Pasic <address@hidden>
Reviewed-by: Guenther Hutzl <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Signed-off-by: Juan Quintela <address@hidden>


  Commit: ea64d5f08817b5e79e17135dce516c7583107f91
      
https://github.com/qemu/qemu/commit/ea64d5f08817b5e79e17135dce516c7583107f91
  Author: Samuel Thibault <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M slirp/socket.c

  Log Message:
  -----------
  slirp: Fix access to freed memory

if_start() goes through the slirp->if_fastq and slirp->if_batchq
list of pending messages, and accesses ifm->ifq_so->so_nqueued of its
elements if ifm->ifq_so != NULL.  When freeing a socket, we thus need
to make sure that any pending message for this socket does not refer
to the socket any more.

Signed-off-by: Samuel Thibault <address@hidden>
Tested-by: Brian Candler <address@hidden>
Reviewed-by: Stefan Hajnoczi <address@hidden>


  Commit: 5c90308f07335451a08c030dc40a9eed4698152b
      
https://github.com/qemu/qemu/commit/5c90308f07335451a08c030dc40a9eed4698152b
  Author: Thomas Huth <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M migration/ram.c

  Log Message:
  -----------
  migration: Fix return code of ram_save_iterate()

qemu_savevm_state_iterate() expects the iterators to return 1
when they are done, and 0 if there is still something left to do.
However, ram_save_iterate() does not obey this rule and returns
the number of saved pages instead. This causes a fatal hang with
ppc64 guests when you run QEMU like this (also works with TCG):

 qemu-img create -f qcow2  /tmp/test.qcow2 1M
 qemu-system-ppc64 -nographic -nodefaults -m 256 \
             -hda /tmp/test.qcow2 -serial mon:stdio

... then switch to the monitor by pressing CTRL-a c and try to
save a snapshot with "savevm test1" for example.

After the first iteration, ram_save_iterate() always returns 0 here,
so that qemu_savevm_state_iterate() hangs in an endless loop and you
can only "kill -9" the QEMU process.
Fix it by using proper return values in ram_save_iterate().

Signed-off-by: Thomas Huth <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Signed-off-by: Juan Quintela <address@hidden>


  Commit: ecce0369b864e3c505b89942cd8cc23a62a4386f
      
https://github.com/qemu/qemu/commit/ecce0369b864e3c505b89942cd8cc23a62a4386f
  Author: Nikunj A Dadhania <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M include/qemu/bitops.h

  Log Message:
  -----------
  bitops: fix rol/ror when shift is zero

All the variants for rol/ror have a bug in case where the shift == 0.
For example rol32, would generate:

    return (word << 0) | (word >> 32);

Which though works, would be flagged as a runtime error on clang's
sanitizer.

Suggested-by: Richard Henderson <address@hidden>
Signed-off-by: Nikunj A Dadhania <address@hidden>
Reviewed-by: Richard Henderson <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 3e00884f4e9f96cb25c03175d1848dd0eb2a22a8
      
https://github.com/qemu/qemu/commit/3e00884f4e9f96cb25c03175d1848dd0eb2a22a8
  Author: Gautham R. Shenoy <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M disas/ppc.c
    M target-ppc/helper.h
    M target-ppc/int_helper.c
    A target-ppc/internal.h
    M target-ppc/translate.c
    M target-ppc/translate/vmx-impl.inc.c
    M target-ppc/translate/vmx-ops.inc.c

  Log Message:
  -----------
  target-ppc: add vrldnmi and vrlwmi instructions

vrldmi: Vector Rotate Left Dword then Mask Insert
vrlwmi: Vector Rotate Left Word then Mask Insert

Signed-off-by: Gautham R. Shenoy <address@hidden>
Signed-off-by: Bharata B Rao <address@hidden>
( use extract[32,64] and rol[32,64], introduce mask helpers in
  internal.h )
Signed-off-by: Nikunj A Dadhania <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 09a245e187efa64d1a42900ec1172087d8e8afda
      
https://github.com/qemu/qemu/commit/09a245e187efa64d1a42900ec1172087d8e8afda
  Author: Bharata B Rao <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M disas/ppc.c
    M target-ppc/helper.h
    M target-ppc/int_helper.c
    M target-ppc/translate/vmx-impl.inc.c
    M target-ppc/translate/vmx-ops.inc.c

  Log Message:
  -----------
  target-ppc: add vrldnm and vrlwnm instructions

vrldnm: Vector Rotate Left Doubleword then AND with Mask
vrlwnm: Vector Rotate Left Word then AND with Mask

Signed-off-by: Bharata B Rao <address@hidden>
Signed-off-by: Nikunj A Dadhania <address@hidden>
Reviewed-by: David Gibson <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 5c69452c1456fcefaa9d7505c06b82c48b459dff
      
https://github.com/qemu/qemu/commit/5c69452c1456fcefaa9d7505c06b82c48b459dff
  Author: Ankit Kumar <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M target-ppc/helper.h
    M target-ppc/int_helper.c
    M target-ppc/translate/vmx-impl.inc.c
    M target-ppc/translate/vmx-ops.inc.c

  Log Message:
  -----------
  target-ppc: add vprtyb[w/d/q] instructions

Add following POWER ISA 3.0 instructions.
vprtybw: Vector Parity Byte Word
vprtybd: Vector Parity Byte Double Word
vprtybq: Vector Parity Byte Quad Word

Signed-off-by: Ankit Kumar <address@hidden>
Signed-off-by: Nikunj A Dadhania <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 8bd9530e1302566e9dc71abe04346ca7d16613b1
      
https://github.com/qemu/qemu/commit/8bd9530e1302566e9dc71abe04346ca7d16613b1
  Author: David Gibson <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M hw/ppc/pnv.c

  Log Message:
  -----------
  powernv: CPU compatibility modes don't make sense for powernv

powernv has some code (derived from the spapr equivalent) used in device
tree generation which depends on the CPU's compatibility mode / logical
PVR.  However, compatibility modes don't make sense on powernv - at least
not as a property controlled by the host - because the guest in powernv
has full hypervisor level access to the virtual system, and so owns the
PCR (Processor Compatibility Register) which implements compatiblity modes.

Note: the new logic doesn't take into account kvmppc_smt_threads() like the
old version did.  However, if core->nr_threads exceeds kvmppc_smt_threads()
then things will already be broken and clamping the value in the device
tree isn't going to save us.

Signed-off-by: David Gibson <address@hidden>
Reviewed-by: Greg Kurz <address@hidden>
Reviewed-by: Thomas Huth <address@hidden>


  Commit: ec575aa0ae8caf1c7af66dad753d1d19a958a8c5
      
https://github.com/qemu/qemu/commit/ec575aa0ae8caf1c7af66dad753d1d19a958a8c5
  Author: Cédric Le Goater <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M hw/ppc/pnv_core.c
    M hw/ppc/pnv_lpc.c
    M hw/ppc/pnv_xscom.c
    M include/hw/ppc/pnv.h
    M include/hw/ppc/pnv_xscom.h

  Log Message:
  -----------
  ppc/pnv: fix compile breakage on old gcc

PnvChip is defined twice and this can confuse old compilers :

  CC      ppc64-softmmu/hw/ppc/pnv_xscom.o
In file included from qemu.git/hw/ppc/pnv.c:29:
qemu.git/include/hw/ppc/pnv.h:60: error: redefinition of typedef ‘PnvChip’
qemu.git/include/hw/ppc/pnv_xscom.h:24: note: previous declaration of ‘PnvChip’ 
was here
make[1]: *** [hw/ppc/pnv.o] Error 1
make[1]: *** Waiting for unfinished jobs....

Signed-off-by: Cédric Le Goater <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: e0aa311673db3717cd726a93be0efe0115b4cd59
      
https://github.com/qemu/qemu/commit/e0aa311673db3717cd726a93be0efe0115b4cd59
  Author: David Gibson <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M target-ppc/cpu-models.c
    M target-ppc/cpu-models.h

  Log Message:
  -----------
  ppc: Remove some stub POWER6 models

The CPU model table includes stub (commented out) definitions for
CPU_POWERPC_POWER6_5 and CPU_POWERPC_POWER6A.  These are not real cpu
models, but represent the POWER6 in some compatiblity modes.  If we ever
do implement POWER6 (unlikely), we'll implement its compatibility modes in
a different way (similar to what we do for POWER7 and POWER8).  So these
stub definitions can be removed.

Signed-off-by: David Gibson <address@hidden>
Reviewed-by: Thomas Huth <address@hidden>


  Commit: b81558724f66807cfe2262707b2cd4ad457693b7
      
https://github.com/qemu/qemu/commit/b81558724f66807cfe2262707b2cd4ad457693b7
  Author: Jose Ricardo Ziviani <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M target-ppc/helper.h
    M target-ppc/int_helper.c
    M target-ppc/translate/vmx-impl.inc.c
    M target-ppc/translate/vmx-ops.inc.c

  Log Message:
  -----------
  target-ppc: Implement bcdcfn. instruction

bcdcfn. converts from National numeric format to BCD. National format
uses a byte to represent a digit where the most significant nibble is
always 0x3 and the least sign. nibbles is the digit itself.

Signed-off-by: Jose Ricardo Ziviani <address@hidden>
Reviewed-by: David Gibson <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: e2106d73d06d33c3e270535a5f69ff081760a267
      
https://github.com/qemu/qemu/commit/e2106d73d06d33c3e270535a5f69ff081760a267
  Author: Jose Ricardo Ziviani <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M target-ppc/helper.h
    M target-ppc/int_helper.c
    M target-ppc/translate/vmx-impl.inc.c

  Log Message:
  -----------
  target-ppc: Implement bcdctn. instruction

bcdctn. converts from BCD to National numeric format. National format
uses a byte to represent a digit where the most significant nibble is
always 0x3 and the least sign. nibbles is the digit itself.

Signed-off-by: Jose Ricardo Ziviani <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 38f4cb043b04e43f48317750aaa619d97e1eff37
      
https://github.com/qemu/qemu/commit/38f4cb043b04e43f48317750aaa619d97e1eff37
  Author: Jose Ricardo Ziviani <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M target-ppc/helper.h
    M target-ppc/int_helper.c
    M target-ppc/translate/vmx-impl.inc.c

  Log Message:
  -----------
  target-ppc: Implement bcdcfz. instruction

bcdcfz. converts from Zoned numeric format to BCD. Zoned format uses
a byte to represent a digit where the most significant nibble is 0x3
or 0xf, depending on the preferred signal.

Signed-off-by: Jose Ricardo Ziviani <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 0a890b31df6689aefcd5b99641ca8d305a601149
      
https://github.com/qemu/qemu/commit/0a890b31df6689aefcd5b99641ca8d305a601149
  Author: Jose Ricardo Ziviani <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M target-ppc/helper.h
    M target-ppc/int_helper.c
    M target-ppc/translate/vmx-impl.inc.c

  Log Message:
  -----------
  target-ppc: Implement bcdctz. instruction

bcdctz. converts from BCD to Zoned numeric format. Zoned format uses
a byte to represent a digit where the most significant nibble is 0x3
or 0xf, depending on the preferred signal.

Signed-off-by: Jose Ricardo Ziviani <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 9b54ca0ba781012eeea4237b7c4832ba2ea81d89
      
https://github.com/qemu/qemu/commit/9b54ca0ba781012eeea4237b7c4832ba2ea81d89
  Author: David Gibson <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M hw/ppc/spapr_pci.c

  Log Message:
  -----------
  spapr: Fix migration of PCI host bridges from qemu-2.7

daa2369 "spapr_pci: Add a 64-bit MMIO window" subtly broke migration from
qemu-2.7 to the current version.  It split the device's MMIO window into
two pieces for 32-bit and 64-bit MMIO.

The patch included backwards compatibility code to convert the old property
into the new format.  However, the property value was also transferred in
the migration stream and compared with a (probably unwise) VMSTATE_EQUAL.
So, the "raw" value from 2.7 is compared to the new style converted value
from (pre-)2.8 giving a mismatch and migration failure.

Although it would be technically possible to fix this in a way allowing
backwards migration, that would leave an ugly legacy around indefinitely.
This patch takes the simpler approach of bumping the migration version,
dropping the unwise VMSTATE_EQUAL (and some equally unwise ones around it)
and ignoring them on an incoming migration.

Signed-off-by: David Gibson <address@hidden>
Reviewed-by: Alexey Kardashevskiy <address@hidden>


  Commit: 5310799a8b687a6cf0b5dbabaa3b6ddc8a6a7a1a
      
https://github.com/qemu/qemu/commit/5310799a8b687a6cf0b5dbabaa3b6ddc8a6a7a1a
  Author: Balbir Singh <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M target-ppc/excp_helper.c

  Log Message:
  -----------
  FU exceptions should carry a cause (IC)

As per the ISA we need a cause and executing a tabort r9 in libc
for example causes a EXCP_FU exception, we don't wire up the
IC (cause) when we post the exception. The cause is required
for the kernel to do the right thing. The fix applies only to 64
bit ppc targets.

Signed-off-by: Balbir singh <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 7bacfd7f7289192c83330adceef9c38649c9acf9
      
https://github.com/qemu/qemu/commit/7bacfd7f7289192c83330adceef9c38649c9acf9
  Author: Thomas Huth <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M hw/char/spapr_vty.c

  Log Message:
  -----------
  spapr-vty: Fix bad assert() statement

When using the serial console in the GTK interface of QEMU (and
QEMU has been compiled with CONFIG_VTE), it is possible to trigger
the assert() statement in vty_receive() in spapr_vty.c by pasting
a chunk of text with length > 16 into the QEMU window.
Most of the other serial backends seem to simply drop characters
that they can not handle, so I think we should also do the same in
spapr-vty to fix this issue.

Buglink: https://bugs.launchpad.net/qemu/+bug/1639322
Signed-off-by: Thomas Huth <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: ad521238b458a6d54ab672ed3f94d5edaa786d5c
      
https://github.com/qemu/qemu/commit/ad521238b458a6d54ab672ed3f94d5edaa786d5c
  Author: Cédric Le Goater <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M hw/ppc/pnv.c
    M include/hw/ppc/pnv.h
    M include/hw/ppc/pnv_xscom.h

  Log Message:
  -----------
  ppc/pnv: add a 'xscom_core_base' field to PnvChipClass

The XSCOM addresses for the core registers are encoded in a slightly
different way on POWER8 and POWER9.

Signed-off-by: Cédric Le Goater <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: f81e551229070f01bf747eda3f05960182db9d2a
      
https://github.com/qemu/qemu/commit/f81e551229070f01bf747eda3f05960182db9d2a
  Author: Cédric Le Goater <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M hw/ppc/pnv_xscom.c

  Log Message:
  -----------
  ppc/pnv: fix xscom address translation for POWER9

High addresses can overflow the uint32_t pcba variable after the 8byte
shift.

Signed-off-by: Cédric Le Goater <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 27d9ffd4b3718707c302fc0aad4746b958443c3a
      
https://github.com/qemu/qemu/commit/27d9ffd4b3718707c302fc0aad4746b958443c3a
  Author: David Gibson <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M hw/ppc/pnv.c

  Log Message:
  -----------
  ppc/pnv: Fix fatal bug on 32-bit hosts

If the pnv machine type is compiled on a 32-bit host, the unsigned long
(host) type is 32-bit.  This means that the hweight_long() used to
calculate the number of allowed cores only considers the low 32 bits of
the cores_mask variable, and can thus return 0 in some circumstances.

This corrects the bug.

Signed-off-by: David Gibson <address@hidden>
Suggested-by: Richard Henderson <address@hidden>
[clg: replaced hweight_long() by ctpop64() ]
Signed-off-by: Cédric Le Goater <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: ca8e4bf4096190245700c4cfd98fca5255935de3
      
https://github.com/qemu/qemu/commit/ca8e4bf4096190245700c4cfd98fca5255935de3
  Author: David Gibson <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M tests/Makefile.include
    A tests/pnv-xscom-test.c

  Log Message:
  -----------
  tests: add XSCOM tests for the PowerNV machine

Add a couple of tests on the XSCOM bus of the PowerNV machine for the
the POWER8 and POWER9 CPUs. The first tests reads the CFAM identifier
of the chip. The second test goes further in the XSCOM address space
and reaches the cores to read their DTS registers.

Signed-off-by: Cédric Le Goater <address@hidden>
[dwg: Fixed an incorrect indentation, and a Makefile problem]]
Signed-off-by: David Gibson <address@hidden>


  Commit: 859c397e57a4c0f8be2e2be011892b7d81b72e8c
      
https://github.com/qemu/qemu/commit/859c397e57a4c0f8be2e2be011892b7d81b72e8c
  Author: Thomas Huth <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M tests/boot-serial-test.c

  Log Message:
  -----------
  boot-serial-test: Add a test for the powernv machine

The new powernv machine ships with a firmware that outputs
some text to the serial console, so we can automatically
test this machine type in the boot-serial tester, too.
And to get some (very limited) test coverage for the new
POWER9 CPU emulation, too, this test is also started with
"-cpu POWER9".

Signed-off-by: Thomas Huth <address@hidden>
Reviewed-by: Cédric Le Goater <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 1e93b9fba2e0e23105e91574fcfc193f899d8e74
      
https://github.com/qemu/qemu/commit/1e93b9fba2e0e23105e91574fcfc193f899d8e74
  Author: Vladimir Sementsov-Ogievskiy <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M blockjob.c

  Log Message:
  -----------
  blockjob: fix dead pointer in txn list

Though it is not intended to be reached through normal circumstances,
if we do not gracefully deconstruct the transaction QLIST, we may wind
up with stale pointers in the list.

The rest of this series attempts to address the underlying issues,
but this should fix list inconsistencies.

Signed-off-by: Vladimir Sementsov-Ogievskiy <address@hidden>
Tested-by: John Snow <address@hidden>
Reviewed-by: John Snow <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Kevin Wolf <address@hidden>
Signed-off-by: John Snow <address@hidden>
Message-id: address@hidden
[Rewrote commit message. --js]
Signed-off-by: John Snow <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Reviewed-by: Kevin Wolf <address@hidden>

Signed-off-by: John Snow <address@hidden>
Signed-off-by: Jeff Cody <address@hidden>


  Commit: e8a40bf71d606f9f87866fb2461eaed52814b38e
      
https://github.com/qemu/qemu/commit/e8a40bf71d606f9f87866fb2461eaed52814b38e
  Author: John Snow <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M block/backup.c
    M blockjob.c
    M include/block/blockjob_int.h

  Log Message:
  -----------
  blockjob: add .clean property

Cleaning up after we have deferred to the main thread but before the
transaction has converged can be dangerous and result in deadlocks
if the job cleanup invokes any BH polling loops.

A job may attempt to begin cleaning up, but may induce another job to
enter its cleanup routine. The second job, part of our same transaction,
will block waiting for the first job to finish, so neither job may now
make progress.

To rectify this, allow jobs to register a cleanup operation that will
always run regardless of if the job was in a transaction or not, and
if the transaction job group completed successfully or not.

Move sensitive cleanup to this callback instead which is guaranteed to
be run only after the transaction has converged, which removes sensitive
timing constraints from said cleanup.

Furthermore, in future patches these cleanup operations will be performed
regardless of whether or not we actually started the job. Therefore,
cleanup callbacks should essentially confine themselves to undoing create
operations, e.g. setup actions taken in what is now backup_start.

Reported-by: Vladimir Sementsov-Ogievskiy <address@hidden>
Signed-off-by: John Snow <address@hidden>
Reviewed-by: Kevin Wolf <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: a7815a764c40c9dcf204f666c2d90248095376a8
      
https://github.com/qemu/qemu/commit/a7815a764c40c9dcf204f666c2d90248095376a8
  Author: John Snow <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M block/backup.c
    M block/commit.c
    M block/mirror.c
    M block/stream.c
    M include/block/blockjob_int.h

  Log Message:
  -----------
  blockjob: add .start field

Add an explicit start field to specify the entrypoint. We already have
ownership of the coroutine itself AND managing the lifetime of the
coroutine, let's take control of creation of the coroutine, too.

This will allow us to delay creation of the actual coroutine until we
know we'll actually start a BlockJob in block_job_start. This avoids
the sticky question of how to "un-create" a Coroutine that hasn't been
started yet.

Signed-off-by: John Snow <address@hidden>
Reviewed-by: Kevin Wolf <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: 5ccac6f186e4a480074880d958760c7105cf9ba8
      
https://github.com/qemu/qemu/commit/5ccac6f186e4a480074880d958760c7105cf9ba8
  Author: John Snow <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M block/backup.c
    M block/commit.c
    M block/mirror.c
    M block/stream.c
    M block/trace-events
    M blockjob.c
    M include/block/blockjob.h
    M tests/test-blockjob-txn.c

  Log Message:
  -----------
  blockjob: add block_job_start

Instead of automatically starting jobs at creation time via backup_start
et al, we'd like to return a job object pointer that can be started
manually at later point in time.

For now, add the block_job_start mechanism and start the jobs
automatically as we have been doing, with conversions job-by-job coming
in later patches.

Of note: cancellation of unstarted jobs will perform all the normal
cleanup as if the job had started, particularly abort and clean. The
only difference is that we will not emit any events, because the job
never actually started.

Signed-off-by: John Snow <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: 111049a4ecefc9cf1ac75c773f4c5c165f27fe63
      
https://github.com/qemu/qemu/commit/111049a4ecefc9cf1ac75c773f4c5c165f27fe63
  Author: John Snow <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M block/backup.c
    M block/replication.c
    M blockdev.c
    M include/block/block_int.h

  Log Message:
  -----------
  blockjob: refactor backup_start as backup_job_create

Refactor backup_start as backup_job_create, which only creates the job,
but does not automatically start it. The old interface, 'backup_start',
is not kept in favor of limiting the number of nearly-identical interfaces
that would have to be edited to keep up with QAPI changes in the future.

Callers that wish to synchronously start the backup_block_job can
instead just call block_job_start immediately after calling
backup_job_create.

Transactions are updated to use the new interface, calling block_job_start
only during the .commit phase, which helps prevent race conditions where
jobs may finish before we even finish building the transaction. This may
happen, for instance, during empty block backup jobs.

Reported-by: Vladimir Sementsov-Ogievskiy <address@hidden>
Signed-off-by: John Snow <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: 0aef09b9c916e8824cabc55a7fd2ca1609b94810
      
https://github.com/qemu/qemu/commit/0aef09b9c916e8824cabc55a7fd2ca1609b94810
  Author: John Snow <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M tests/qemu-iotests/124
    M tests/qemu-iotests/124.out

  Log Message:
  -----------
  iotests: add transactional failure race test

Add a regression test for the case found by Vladimir.

Reported-by: Vladimir Sementsov-Ogievskiy <address@hidden>
Signed-off-by: John Snow <address@hidden>
Reviewed-by: Kevin Wolf <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: 0a4c0c3f90c3fb0239cb17d63a68c14742965a1c
      
https://github.com/qemu/qemu/commit/0a4c0c3f90c3fb0239cb17d63a68c14742965a1c
  Author: Paolo Bonzini <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M tests/qemu-iotests/109

  Log Message:
  -----------
  qemu-iotests: avoid spurious failure on test 109

In some cases it is possible that query-io-status is called just
before the job is completed, causing

    -{"timestamp": {"seconds":  TIMESTAMP, "microseconds":  TIMESTAMP}, 
"event": "BLOCK_JOB_COMPLETED", "data": {"device": "src", "len": 31457280, 
"offset": OFFSET, "speed": 0, "type": "mirror", "error": "Operation not 
permitted"}}
    -{"return": []}
    +{"return": [{"io-status": "ok", "device": "src", "busy": true, "len": 
31457280, "offset": OFFSET, "paused": false, "speed": 0, "ready": false, 
"type": "mirror"}]}

Assert that the completeion event eventually happens.

Signed-off-by: Paolo Bonzini <address@hidden>
Message-id: address@hidden
Reviewed-by: Jeff Cody <address@hidden>
Signed-off-by: Jeff Cody <address@hidden>


  Commit: 23dce3873f3aee6ee7d4a1c17dd26fb5f453bc5a
      
https://github.com/qemu/qemu/commit/23dce3873f3aee6ee7d4a1c17dd26fb5f453bc5a
  Author: Max Reitz <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M block/curl.c
    M docs/qmp-commands.txt
    M qapi/block-core.json
    M qemu-options.hx

  Log Message:
  -----------
  block/curl: Drop TFTP "support"

Because TFTP does not support byte ranges, it was never usable with our
curl block driver. Since apparently nobody has ever complained loudly
enough for someone to take care of the issue until now, it seems
reasonable to assume that nobody has ever actually used it.

Therefore, it should be safe to just drop it from curl's protocol list.

[Jeff Cody: Below is additional summary pulled, with some rewording,
      from followup emails between Max and Markus, to explain what
      worked and what didn't]

TFTP would sometimes work, to a limited extent, for images <= the curl
"readahead" size, so long as reads started at offset zero.  By default,
that readahead size is 256KB.

Reads starting at a non-zero offset would also have returned data from a
zero offset.  It can become more complicated still, with mixed reads at
zero offset and non-zero offsets, due to data buffering.

In short, TFTP could only have worked before in very specific scenarios
with unrealistic expectations and constraints.

Signed-off-by: Max Reitz <address@hidden>
Reviewed-by: Kevin Wolf <address@hidden>
Reviewed-by: Jeff Cody <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: 9054d9f6b00a3f0576b1a7310a3886d1783ad382
      
https://github.com/qemu/qemu/commit/9054d9f6b00a3f0576b1a7310a3886d1783ad382
  Author: Max Reitz <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M block/curl.c

  Log Message:
  -----------
  block/curl: Use BDRV_SECTOR_SIZE

Currently, curl defines its own constant SECTOR_SIZE. There is no
advantage over using the global BDRV_SECTOR_SIZE, so drop it.

Cc: address@hidden
Signed-off-by: Max Reitz <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: 4e7676571bccb42dd49b5efbb91ac49077ea5197
      
https://github.com/qemu/qemu/commit/4e7676571bccb42dd49b5efbb91ac49077ea5197
  Author: Max Reitz <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M block/curl.c

  Log Message:
  -----------
  block/curl: Fix return value from curl_read_cb

While commit 38bbc0a580f9f10570b1d1b5d3e92f0e6feb2970 is correct in that
the callback is supposed to return the number of bytes handled; what it
does not mention is that libcurl will throw an error if the callback did
not "handle" all of the data passed to it.

Therefore, if the callback receives some data that it cannot handle
(either because the receive buffer has not been set up yet or because it
would not fit into the receive buffer) and we have to ignore it, we
still have to report that the data has been handled.

Obviously, this should not happen normally. But it does happen at least
for FTP connections where some data (that we do not expect) may be
generated when the connection is established.

Cc: address@hidden
Signed-off-by: Max Reitz <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: ff5ca1664af85b24a4180d595ea6873fd3deac57
      
https://github.com/qemu/qemu/commit/ff5ca1664af85b24a4180d595ea6873fd3deac57
  Author: Max Reitz <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M block/curl.c

  Log Message:
  -----------
  block/curl: Remember all sockets

For some connection types (like FTP, generally), more than one socket
may be used (in FTP's case: control vs. data stream). As of commit
838ef602498b8d1985a231a06f5e328e2946a81d ("curl: Eliminate unnecessary
use of curl_multi_socket_all"), we have to remember all of the sockets
used by libcurl, but in fact we only did that for a single one. Since
one libcurl connection may use multiple sockets, however, we have to
remember them all.

Cc: address@hidden
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: 4e504535c16dfa66290281e704384abfaca08673
      
https://github.com/qemu/qemu/commit/4e504535c16dfa66290281e704384abfaca08673
  Author: Max Reitz <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M block/curl.c

  Log Message:
  -----------
  block/curl: Do not wait for data beyond EOF

libcurl will only give us as much data as there is, not more. The block
layer will deny requests beyond the end of file for us; but since this
block driver is still using a sector-based interface, we can still get
in trouble if the file size is not a multiple of 512.

While we have already made sure not to attempt transfers beyond the end
of the file, we are currently still trying to receive data from there if
the original request exceeds the file size. This patch fixes this issue
and invokes qemu_iovec_memset() on the iovec's tail.

Cc: address@hidden
Signed-off-by: Max Reitz <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: bdffb31d8eece1cbd4d88f136daccfe1f93a1bf6
      
https://github.com/qemu/qemu/commit/bdffb31d8eece1cbd4d88f136daccfe1f93a1bf6
  Author: Paolo Bonzini <address@hidden>
  Date:   2016-11-14 (Mon, 14 Nov 2016)

  Changed paths:
    M block/mirror.c

  Log Message:
  -----------
  mirror: do not flush every time the disks are synced

This puts a huge strain on the disks when there are many concurrent
migrations.  With this patch we only flush twice: just before issuing
the event, and just before pivoting to the destination.  If management
will complete the job close to the BLOCK_JOB_READY event, the cost of
the second flush should be small anyway.

Signed-off-by: Paolo Bonzini <address@hidden>
Message-id: address@hidden
Signed-off-by: Jeff Cody <address@hidden>


  Commit: 68b5f314a269979b4f2014eb22873732d4745bcc
      
https://github.com/qemu/qemu/commit/68b5f314a269979b4f2014eb22873732d4745bcc
  Author: Yuri Benditovich <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M hw/net/virtio-net.c

  Log Message:
  -----------
  net: skip virtio-net config of deleted nic's peers

https://bugzilla.redhat.com/show_bug.cgi?id=1373816
qemu core dump happens during repetitive unpug-plug
with multiple queues and Windows RSS-capable guest.
If back-end delete requested during virtio-net device
initialization, driver still can try configure the device
for multiple queues. The virtio-net device is expected
to be removed as soon as the initialization is done.

Signed-off-by: Yuri Benditovich <address@hidden>
Signed-off-by: Jason Wang <address@hidden>


  Commit: e79cd4068063ea2859199002a049010a11202939
      
https://github.com/qemu/qemu/commit/e79cd4068063ea2859199002a049010a11202939
  Author: Daniel P. Berrange <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M net/net.c
    M net/socket.c

  Log Message:
  -----------
  net: fix sending of data with -net socket, listen backend

The use of -net socket,listen was broken in the following
commit

  commit 16a3df403b10c4ac347159e39005fd520b2648bb
  Author: Zhang Chen <address@hidden>
  Date:   Fri May 13 15:35:19 2016 +0800

    net/net: Add SocketReadState for reuse codes

    This function is from net/socket.c, move it to net.c and net.h.
    Add SocketReadState to make others reuse net_fill_rstate().
    suggestion from jason.

This refactored the state out of NetSocketState into a
separate SocketReadState. This refactoring requires
that a callback is provided to be triggered upon
completion of a packet receive from the guest.

The patch only registered this callback in the codepaths
hit by -net socket,connect, not -net socket,listen. So
as a result packets sent by the guest in the latter case
get dropped on the floor.

This bug is hidden because net_fill_rstate() silently
does nothing if the callback is not set.

This patch adds in the middle callback registration
and also adds an assert so that QEMU aborts if there
are any other codepaths hit which are missing the
callback.

Signed-off-by: Daniel P. Berrange <address@hidden>
Reviewed-by: Zhang Chen <address@hidden>
Signed-off-by: Jason Wang <address@hidden>


  Commit: a38299bf431a891c0a21a77199e7148c0983413e
      
https://github.com/qemu/qemu/commit/a38299bf431a891c0a21a77199e7148c0983413e
  Author: Zhang Chen <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M docs/COLO-FT.txt

  Log Message:
  -----------
  docs: fix COLO architecture diagram

Fix COLO-Proxy part of COLO architecture diagram

Signed-off-by: Zhang Chen <address@hidden>
Reviewed-by: zhanghailiang <address@hidden>
Signed-off-by: Jason Wang <address@hidden>


  Commit: 972d233b1d3eacf29a281bb2dd20a52784632894
      
https://github.com/qemu/qemu/commit/972d233b1d3eacf29a281bb2dd20a52784632894
  Author: Stefan Hajnoczi <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M hmp.c
    M migration/migration.c
    M migration/ram.c
    M tests/test-vmstate.c

  Log Message:
  -----------
  Merge remote-tracking branch 'quintela/tags/migration/20161114' into staging

migration/next for 20161114

# gpg: Signature made Mon 14 Nov 2016 07:55:42 PM GMT
# gpg:                using RSA key 0xF487EF185872D723
# gpg: Good signature from "Juan Quintela <address@hidden>"
# gpg:                 aka "Juan Quintela <address@hidden>"
# Primary key fingerprint: 1899 FF8E DEBF 58CC EE03  4B82 F487 EF18 5872 D723

* quintela/tags/migration/20161114:
  migration: Fix return code of ram_save_iterate()
  tests/test-vmstate.c: add array of pointer to struct
  tests/test-vmstate.c: add save_buffer util func
  migration: fix missing assignment for has_x_checkpoint_delay

Message-id: address@hidden
Signed-off-by: Stefan Hajnoczi <address@hidden>


  Commit: 5d0df6de7529edfc3f27bc04bf09fe583bdcca3e
      
https://github.com/qemu/qemu/commit/5d0df6de7529edfc3f27bc04bf09fe583bdcca3e
  Author: Stefan Hajnoczi <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M slirp/socket.c

  Log Message:
  -----------
  Merge remote-tracking branch 'sthibault/tags/samuel-thibault' into staging

slirp updates

# gpg: Signature made Mon 14 Nov 2016 08:19:16 PM GMT
# gpg:                using RSA key 0xA003196827414880
# gpg: Good signature from "Samuel Thibault <address@hidden>"
# gpg:                 aka "Samuel Thibault <address@hidden>"
# gpg:                 aka "Samuel Thibault <address@hidden>"
# gpg:                 aka "Samuel Thibault <address@hidden>"
# gpg:                 aka "Samuel Thibault <address@hidden>"
# gpg:                 aka "Samuel Thibault <address@hidden>"
# Primary key fingerprint: 900C B024 B679 31D4 0F82  304B D017 8C76 7D06 9EE6
#      Subkey fingerprint: 6B0F AC21 8566 46E9 4AA2  D200 A003 1968 2741 4880

* sthibault/tags/samuel-thibault:
  slirp: Fix access to freed memory

Message-id: address@hidden
Signed-off-by: Stefan Hajnoczi <address@hidden>


  Commit: 8a7b5c189303b4542eda046c4606ffadf2deece7
      
https://github.com/qemu/qemu/commit/8a7b5c189303b4542eda046c4606ffadf2deece7
  Author: Stefan Hajnoczi <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M disas/ppc.c
    M hw/char/spapr_vty.c
    M hw/ppc/pnv.c
    M hw/ppc/pnv_core.c
    M hw/ppc/pnv_lpc.c
    M hw/ppc/pnv_xscom.c
    M hw/ppc/spapr_pci.c
    M include/hw/ppc/pnv.h
    M include/hw/ppc/pnv_xscom.h
    M include/qemu/bitops.h
    M target-ppc/cpu-models.c
    M target-ppc/cpu-models.h
    M target-ppc/excp_helper.c
    M target-ppc/helper.h
    M target-ppc/int_helper.c
    A target-ppc/internal.h
    M target-ppc/translate.c
    M target-ppc/translate/vmx-impl.inc.c
    M target-ppc/translate/vmx-ops.inc.c
    M tests/Makefile.include
    M tests/boot-serial-test.c
    A tests/pnv-xscom-test.c

  Log Message:
  -----------
  Merge remote-tracking branch 'dgibson/tags/ppc-for-2.8-20161115' into staging

ppc patch queue 2016-11-15

Latest set of ppc and spapr related patches.  Highlights are:
   * More POWER9 instructions
   * Fix some subtle outstanding bugs
   * Add some extra tests

One patch affects bitops.h, so isn't strictly ppc related.

# gpg: Signature made Tue 15 Nov 2016 02:46:48 AM GMT
# gpg:                using RSA key 0x6C38CACA20D9B392
# gpg: Good signature from "David Gibson <address@hidden>"
# gpg:                 aka "David Gibson (kernel.org) <address@hidden>"
# gpg:                 aka "David Gibson (Red Hat) <address@hidden>"
# gpg:                 aka "David Gibson (ozlabs.org) <address@hidden>"
# Primary key fingerprint: 75F4 6586 AE61 A66C C44E  87DC 6C38 CACA 20D9 B392

* dgibson/tags/ppc-for-2.8-20161115:
  boot-serial-test: Add a test for the powernv machine
  tests: add XSCOM tests for the PowerNV machine
  ppc/pnv: Fix fatal bug on 32-bit hosts
  ppc/pnv: fix xscom address translation for POWER9
  ppc/pnv: add a 'xscom_core_base' field to PnvChipClass
  spapr-vty: Fix bad assert() statement
  FU exceptions should carry a cause (IC)
  spapr: Fix migration of PCI host bridges from qemu-2.7
  target-ppc: Implement bcdctz. instruction
  target-ppc: Implement bcdcfz. instruction
  target-ppc: Implement bcdctn. instruction
  target-ppc: Implement bcdcfn. instruction
  ppc: Remove some stub POWER6 models
  ppc/pnv: fix compile breakage on old gcc
  powernv: CPU compatibility modes don't make sense for powernv
  target-ppc: add vprtyb[w/d/q] instructions
  target-ppc: add vrldnm and vrlwnm instructions
  target-ppc: add vrldnmi and vrlwmi instructions
  bitops: fix rol/ror when shift is zero

Message-id: address@hidden
Signed-off-by: Stefan Hajnoczi <address@hidden>


  Commit: 1ed9bd12c86b417669c22b4342ba27aec20c87e4
      
https://github.com/qemu/qemu/commit/1ed9bd12c86b417669c22b4342ba27aec20c87e4
  Author: Stefan Hajnoczi <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M block/backup.c
    M block/commit.c
    M block/curl.c
    M block/mirror.c
    M block/replication.c
    M block/stream.c
    M block/trace-events
    M blockdev.c
    M blockjob.c
    M docs/qmp-commands.txt
    M include/block/block_int.h
    M include/block/blockjob.h
    M include/block/blockjob_int.h
    M qapi/block-core.json
    M qemu-options.hx
    M tests/qemu-iotests/109
    M tests/qemu-iotests/124
    M tests/qemu-iotests/124.out
    M tests/test-blockjob-txn.c

  Log Message:
  -----------
  Merge remote-tracking branch 'jtc/tags/block-pull-request' into staging

# gpg: Signature made Tue 15 Nov 2016 04:10:29 AM GMT
# gpg:                using RSA key 0xBDBE7B27C0DE3057
# gpg: Good signature from "Jeffrey Cody <address@hidden>"
# gpg:                 aka "Jeffrey Cody <address@hidden>"
# gpg:                 aka "Jeffrey Cody <address@hidden>"
# Primary key fingerprint: 9957 4B4D 3474 90E7 9D98  D624 BDBE 7B27 C0DE 3057

* jtc/tags/block-pull-request:
  mirror: do not flush every time the disks are synced
  block/curl: Do not wait for data beyond EOF
  block/curl: Remember all sockets
  block/curl: Fix return value from curl_read_cb
  block/curl: Use BDRV_SECTOR_SIZE
  block/curl: Drop TFTP "support"
  qemu-iotests: avoid spurious failure on test 109
  iotests: add transactional failure race test
  blockjob: refactor backup_start as backup_job_create
  blockjob: add block_job_start
  blockjob: add .start field
  blockjob: add .clean property
  blockjob: fix dead pointer in txn list

Message-id: address@hidden
Signed-off-by: Stefan Hajnoczi <address@hidden>


  Commit: 97e53cf82ca0ffa9abe2def2fabc5fc75b914d90
      
https://github.com/qemu/qemu/commit/97e53cf82ca0ffa9abe2def2fabc5fc75b914d90
  Author: Stefan Hajnoczi <address@hidden>
  Date:   2016-11-15 (Tue, 15 Nov 2016)

  Changed paths:
    M docs/COLO-FT.txt
    M hw/net/virtio-net.c
    M net/net.c
    M net/socket.c

  Log Message:
  -----------
  Merge remote-tracking branch 'jasowang/tags/net-pull-request' into staging

# gpg: Signature made Tue 15 Nov 2016 07:37:27 AM GMT
# gpg:                using RSA key 0xEF04965B398D6211
# gpg: Good signature from "Jason Wang (Jason Wang on RedHat) <address@hidden>"
# gpg: WARNING: This key is not certified with sufficiently trusted signatures!
# gpg:          It is not certain that the signature belongs to the owner.
# Primary key fingerprint: 215D 46F4 8246 689E C77F  3562 EF04 965B 398D 6211

* jasowang/tags/net-pull-request:
  docs: fix COLO architecture diagram
  net: fix sending of data with -net socket, listen backend
  net: skip virtio-net config of deleted nic's peers

Message-id: address@hidden
Signed-off-by: Stefan Hajnoczi <address@hidden>


Compare: https://github.com/qemu/qemu/compare/682df581c65e...97e53cf82ca0