qemu-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-commits] [qemu/qemu] bd4480: migration: Revert mapped-ram multifd


From: Peter Maydell
Subject: [Qemu-commits] [qemu/qemu] bd4480: migration: Revert mapped-ram multifd support to fd...
Date: Mon, 25 Mar 2024 09:46:27 -0700

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: bd4480b0d02ee760b51aa82cc0915174753716ee
      
https://github.com/qemu/qemu/commit/bd4480b0d02ee760b51aa82cc0915174753716ee
  Author: Fabiano Rosas <farosas@suse.de>
  Date:   2024-03-22 (Fri, 22 Mar 2024)

  Changed paths:
    M migration/fd.c
    M migration/fd.h
    M migration/file.c
    M migration/migration.c
    M migration/multifd.c
    M tests/qtest/migration-test.c

  Log Message:
  -----------
  migration: Revert mapped-ram multifd support to fd: URI

This reverts commit decdc76772c453ff1444612e910caa0d45cd8eac in full
and also the relevant migration-tests from
7a09f092834641b7a793d50a3a261073bbb404a6.

After the addition of the new QAPI-based migration address API in 8.2
we've been converting an "fd:" URI into a SocketAddress, missing the
fact that the "fd:" syntax could also be used for a plain file instead
of a socket. This is a problem because the SocketAddress is part of
the API, so we're effectively asking users to create a "socket"
channel to pass in a plain file.

The easiest way to fix this situation is to deprecate the usage of
both SocketAddress and "fd:" when used with a plain file for
migration. Since this has been possible since 8.2, we can wait until
9.1 to deprecate it.

For 9.0, however, we should avoid adding further support to migration
to a plain file using the old "fd:" syntax or the new SocketAddress
API, and instead require the usage of either the old-style "file:" URI
or the FileMigrationArgs::filename field of the new API with the
"/dev/fdset/NN" syntax, both of which are already supported.

Signed-off-by: Fabiano Rosas <farosas@suse.de>
Link: https://lore.kernel.org/r/20240319210941.1907-1-farosas@suse.de
Signed-off-by: Peter Xu <peterx@redhat.com>


  Commit: 910c1647364f0c8c1f680f260a2b7d52587bc38e
      
https://github.com/qemu/qemu/commit/910c1647364f0c8c1f680f260a2b7d52587bc38e
  Author: Peter Xu <peterx@redhat.com>
  Date:   2024-03-22 (Fri, 22 Mar 2024)

  Changed paths:
    M migration/migration.c

  Log Message:
  -----------
  migration/postcopy: Fix high frequency sync

With current code base I can observe extremely high sync count during
precopy, as long as one enables postcopy-ram=on before switchover to
postcopy.

To provide some context of when QEMU decides to do a full sync: it checks
must_precopy (which implies "data must be sent during precopy phase"), and
as long as it is lower than the threshold size we calculated (out of
bandwidth and expected downtime) QEMU will kick off the slow/exact sync.

However, when postcopy is enabled (even if still during precopy phase), RAM
only reports all pages as can_postcopy, and report must_precopy==0.  Then
"must_precopy <= threshold_size" mostly always triggers and enforces a slow
sync for every call to migration_iteration_run() when postcopy is enabled
even if not used.  That is insane.

It turns out it was a regress bug introduced in the previous refactoring in
8.0 as reported by Nina [1]:

  (a) c8df4a7aef ("migration: Split save_live_pending() into state_pending_*")

Then a workaround patch is applied at the end of release (8.0-rc4) to fix it:

  (b) 28ef5339c3 ("migration: fix ram_state_pending_exact()")

However that "workaround" was overlooked when during the cleanup in this
9.0 release in this commit..

  (c) b0504edd40 ("migration: Drop unnecessary check in ram's pending_exact()")

Then the issue was re-exposed as reported by Nina [1].

The problem with (b) is that it only fixed the case for RAM, rather than
all the rest of iterators.  Here a slow sync should only be required if all
dirty data (precopy+postcopy) is less than the threshold_size that QEMU
calculated.  It is even debatable whether a sync is needed when switched to
postcopy.  Currently ram_state_pending_exact() will be mostly noop if
switched to postcopy, and that logic seems to apply too for all the rest of
iterators, as sync dirty bitmap during a postcopy doesn't make much sense.
However let's leave such change for later, as we're in rc phase.

So rather than reusing commit (b), this patch provides the complete fix for
all iterators.  When at it, cleanup a little bit on the lines around.

[1] https://gitlab.com/qemu-project/qemu/-/issues/1565

Reported-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
Fixes: b0504edd40 ("migration: Drop unnecessary check in ram's pending_exact()")
Reviewed-by: Fabiano Rosas <farosas@suse.de>
Link: https://lore.kernel.org/r/20240320214453.584374-1-peterx@redhat.com
Signed-off-by: Peter Xu <peterx@redhat.com>


  Commit: 8fa1a21c6edc2bf7de85984944848ab9ac49e937
      
https://github.com/qemu/qemu/commit/8fa1a21c6edc2bf7de85984944848ab9ac49e937
  Author: Fabiano Rosas <farosas@suse.de>
  Date:   2024-03-22 (Fri, 22 Mar 2024)

  Changed paths:
    M migration/multifd.c

  Log Message:
  -----------
  migration/multifd: Fix clearing of mapped-ram zero pages

When the zero page detection is done in the multifd threads, we need
to iterate the second part of the pages->offset array and clear the
file bitmap for each zero page. The piece of code we merged to do that
is wrong.

The reason this has passed all the tests is because the bitmap is
initialized with zeroes already, so clearing the bits only really has
an effect during live migration and when a data page goes from having
data to no data.

Fixes: 303e6f54f9 ("migration/multifd: Implement zero page transmission on the 
multifd thread.")
Signed-off-by: Fabiano Rosas <farosas@suse.de>
Link: https://lore.kernel.org/r/20240321201242.6009-1-farosas@suse.de
Signed-off-by: Peter Xu <peterx@redhat.com>


  Commit: 0235540bba9b80668ce388dff9a904c04618f9aa
      
https://github.com/qemu/qemu/commit/0235540bba9b80668ce388dff9a904c04618f9aa
  Author: Thomas Huth <thuth@redhat.com>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M .travis.yml

  Log Message:
  -----------
  .travis.yml: Shorten the runtime of the problematic jobs

The "[s390x] GCC (other-system)" and the "[s390x] GCC check-tcg"
jobs are hitting the 50 minutes timeout in Travis quite frequently
since a while.

To fix it, we've got to drop a lot of the targets from the target
list in the jobs to make them work again.

With regards to the "check-tcg" test, we can move the check with
"s390x-linux-user" to the "user" job instead which also builds
the s390x-linux-user target.

And while we're at it, remove the "--enable-fdt=system" configure
switch (since this is not required nowadays anymore).

Message-ID: <20240320104144.823425-2-thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 8c37f869f32df97401e61636a1140e03669479d6
      
https://github.com/qemu/qemu/commit/8c37f869f32df97401e61636a1140e03669479d6
  Author: Thomas Huth <thuth@redhat.com>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M .travis.yml

  Log Message:
  -----------
  .travis.yml: Remove the unused xfslib-dev package

Drop the "xfslibs-dev" package which should not be necessary anymore
since commit a5730b8bd3 ("block/file-posix: Simplify the XFS_IOC_DIOINFO
handling").

Message-ID: <20240320104144.823425-3-thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: ed355dc107f16f980b20794aa498fa9588e61de5
      
https://github.com/qemu/qemu/commit/ed355dc107f16f980b20794aa498fa9588e61de5
  Author: Thomas Huth <thuth@redhat.com>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M hw/microblaze/xlnx-zynqmp-pmu.c

  Log Message:
  -----------
  hw/microblaze: Do not allow xlnx-zynqmp-pmu-soc to be created by the user

Using xlnx-zynqmp-pmu-soc on the command line causes QEMU to crash:

 ./qemu-system-microblazeel -M petalogix-ml605 -device xlnx-zynqmp-pmu-soc
 **
 ERROR:tcg/tcg.c:813:tcg_register_thread: assertion failed: (n < tcg_max_ctxs)
 Bail out!
 Aborted (core dumped)

Mark the device with "user_creatable = false" to avoid that this can happen.

Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2229
Message-ID: <20240322183153.1023359-1-thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: ed6d5c2e584e4ce828ffb55785b4164a4bf5dbcc
      
https://github.com/qemu/qemu/commit/ed6d5c2e584e4ce828ffb55785b4164a4bf5dbcc
  Author: Cédric Le Goater <clg@redhat.com>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M hw/arm/aspeed_ast2600.c

  Log Message:
  -----------
  aspeed: Make the ast2600-a3 SoC not user creatable

Aspeed SoCs are complex devices that can not be specified on the
command line. Fix that to avoid QEMU aborts.

Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2227
Fixes: f25c0ae1079d ("aspeed/soc: Add AST2600 support")
Reported-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-ID: <20240319150903.413662-1-clg@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 1967e9e06709c2b3de8b071d94da3856ba5b1ce6
      
https://github.com/qemu/qemu/commit/1967e9e06709c2b3de8b071d94da3856ba5b1ce6
  Author: Cédric Le Goater <clg@redhat.com>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M hw/arm/aspeed_ast10x0.c

  Log Message:
  -----------
  aspeed: Make the ast1030-a1 SoC not user creatable

Aspeed SoCs are complex devices that can not be specified on the
command line. Fix that to avoid QEMU aborts.

Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2227
Fixes: 356b230ed138 ("aspeed/soc : Add AST1030 support")
Reported-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-ID: <20240319150903.413662-2-clg@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 80e9791a93b856ae959cf0efa04cee53390ed000
      
https://github.com/qemu/qemu/commit/80e9791a93b856ae959cf0efa04cee53390ed000
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M tests/qtest/npcm7xx_emc-test.c

  Log Message:
  -----------
  tests/qtest/npcm7xx_emc_test: Don't leak cmd_line

In test_rx() and test_tx() we allocate a GString *cmd_line
but never free it. This is pretty harmless in a test case, but
Coverity spotted it.

Resolves: Coverity CID 1507122
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-id: 20240312183810.557768-2-peter.maydell@linaro.org


  Commit: e921e00d4ba6840063d69cb637331d0dc4905e4b
      
https://github.com/qemu/qemu/commit/e921e00d4ba6840063d69cb637331d0dc4905e4b
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M tests/unit/socket-helpers.c

  Log Message:
  -----------
  tests/unit/socket-helpers: Don't close(-1)

In socket_check_afunix_support() we call socket(PF_UNIX, SOCK_STREAM, 0)
to see if it works, but we call close() on the result whether it
worked or not. Only close the fd if the socket() call succeeded.
Spotted by Coverity.

Resolves: Coverity CID 1497481

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-id: 20240312183810.557768-3-peter.maydell@linaro.org


  Commit: bed150be5b94ee499384fa6d052c0cb398a20d95
      
https://github.com/qemu/qemu/commit/bed150be5b94ee499384fa6d052c0cb398a20d95
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M net/af-xdp.c

  Log Message:
  -----------
  net/af-xdp.c: Don't leak sock_fds array in net_init_af_xdp()

In net_init_af_xdp() we parse the arguments and allocate
a buffer of ints into sock_fds. However, although we
free this in the error exit path, we don't ever free it
in the successful return path. Coverity spots this leak.

Switch to g_autofree so we don't need to manually free the
array.

Resolves: Coverity CID 1534906
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-id: 20240312183810.557768-4-peter.maydell@linaro.org


  Commit: c67f7580697198800c57ced59f1dfbce1aaeb4ae
      
https://github.com/qemu/qemu/commit/c67f7580697198800c57ced59f1dfbce1aaeb4ae
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M hw/misc/pca9554.c

  Log Message:
  -----------
  hw/misc/pca9554: Correct error check bounds in get/set pin functions

In pca9554_get_pin() and pca9554_set_pin(), we try to detect an
incorrect pin value, but we get the condition wrong, using ">"
when ">=" was intended.

This has no actual effect, because in pca9554_initfn() we
use the correct test when creating the properties and so
we'll never be called with an out of range value. However,
Coverity complains about the mismatch between the check and
the later use of the pin value in a shift operation.

Use the correct condition.

Resolves: Coverity CID 1534917
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-id: 20240312183810.557768-5-peter.maydell@linaro.org


  Commit: b13ba381ca4d0b3e96a9e5bd138a1f3e11b5a637
      
https://github.com/qemu/qemu/commit/b13ba381ca4d0b3e96a9e5bd138a1f3e11b5a637
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M hw/nvram/mac_nvram.c

  Log Message:
  -----------
  hw/nvram/mac_nvram: Report failure to write data

There's no way for the macio_nvram device to report failure to write
data, but we can at least report it to the user with error_report()
as we do in other devices like xlnx-efuse.

Spotted by Coverity.

Resolves: Coverity CID 1507628
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-id: 20240312183810.557768-6-peter.maydell@linaro.org


  Commit: 6328d8ffa6cb9d750e4bfcfd73ac25d3a39ceb63
      
https://github.com/qemu/qemu/commit/6328d8ffa6cb9d750e4bfcfd73ac25d3a39ceb63
  Author: Cédric Le Goater <clg@redhat.com>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M MAINTAINERS
    M hw/arm/aspeed.c
    M hw/gpio/meson.build
    A hw/gpio/pca9552.c
    A hw/gpio/pca9554.c
    M hw/gpio/trace-events
    M hw/misc/meson.build
    R hw/misc/pca9552.c
    R hw/misc/pca9554.c
    M hw/misc/trace-events
    A include/hw/gpio/pca9552.h
    A include/hw/gpio/pca9552_regs.h
    A include/hw/gpio/pca9554.h
    A include/hw/gpio/pca9554_regs.h
    R include/hw/misc/pca9552.h
    R include/hw/misc/pca9552_regs.h
    R include/hw/misc/pca9554.h
    R include/hw/misc/pca9554_regs.h
    M tests/qtest/pca9552-test.c
    M tests/qtest/pnv-host-i2c-test.c

  Log Message:
  -----------
  misc/pca955*: Move models under hw/gpio

The PCA9552 and PCA9554 devices are both I2C GPIO controllers and the
PCA9552 also can drive LEDs. Do all the necessary adjustments to move
the models under hw/gpio.

Cc: Glenn Miles <milesg@linux.vnet.ibm.com>
Signed-off-by: Cédric Le Goater <clg@redhat.com>
Message-ID: <20240325134833.1484265-1-clg@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 66e411885a23c96ff73742d06b793fec3ceaebb7
      
https://github.com/qemu/qemu/commit/66e411885a23c96ff73742d06b793fec3ceaebb7
  Author: Zheyu Ma <zheyuma97@gmail.com>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M tests/qtest/libqos/virtio.c

  Log Message:
  -----------
  libqos/virtio.c: Correct 'flags' reading in qvirtqueue_kick

In qvirtqueue_kick(), the 'flags' were previously being incorrectly read from
vq->avail instead of the correct vq->used location. This update ensures 'flags'
are read from the correct location as per the virtio standard.

Signed-off-by: Zheyu Ma <zheyuma97@gmail.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20240320090442.267525-1-zheyuma97@gmail.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 272fba9779af0bb1c29cd30302fc1e31c59274d0
      
https://github.com/qemu/qemu/commit/272fba9779af0bb1c29cd30302fc1e31c59274d0
  Author: Ido Plat <ido.plat@ibm.com>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M target/s390x/tcg/translate.c

  Log Message:
  -----------
  target/s390x: Use mutable temporary value for op_ts

Otherwise TCG would assume the register that holds t1 would be constant
and reuse whenever it needs the value within it.

Cc: qemu-stable@nongnu.org
Fixes: f1ea739bd598 ("target/s390x: Use tcg_constant_* in local contexts")
Reviewed-by: Ilya Leoshkevich <iii@linux.ibm.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
[iii: Adjust a newline and capitalization, add tags]
Signed-off-by: Ido Plat <ido.plat@ibm.com>
Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Message-ID: <20240318202722.20675-1-iii@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: f9b29c636442e917a56a725d774ea99be3b28111
      
https://github.com/qemu/qemu/commit/f9b29c636442e917a56a725d774ea99be3b28111
  Author: Ilya Leoshkevich <iii@linux.ibm.com>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M tests/tcg/s390x/Makefile.target
    A tests/tcg/s390x/ts.c

  Log Message:
  -----------
  tests/tcg/s390x: Test TEST AND SET

Add a small test to prevent regressions.

Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-ID: <20240318202722.20675-2-iii@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>


  Commit: 43199b13938aa693b2f10d8d17c59eebfe4e40c5
      
https://github.com/qemu/qemu/commit/43199b13938aa693b2f10d8d17c59eebfe4e40c5
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M tests/unit/test-throttle.c

  Log Message:
  -----------
  tests/unit/test-throttle: Avoid unintended integer division

In test_compute_wait() we do
 double units = bkt.max / 10;
which does an integer division and then assigns it to a double variable,
and similarly later on in the expression for an assertion.

Use 10.0 so that we do a floating point division and calculate the
exact value, rather than doing an integer division.

Spotted by Coverity.

Resolves: Coverity CID 1432564
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-id: 20240312183810.557768-7-peter.maydell@linaro.org


  Commit: fe3e38390126c2202292911c49d46fc7ee4a163a
      
https://github.com/qemu/qemu/commit/fe3e38390126c2202292911c49d46fc7ee4a163a
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M tests/qtest/libqtest.c

  Log Message:
  -----------
  tests/qtest/libqtest.c: Check for g_setenv() failure

Coverity points out that g_setenv() can fail and we don't
check for this in qtest_inproc_init(). In practice this will
only fail if a memory allocation failed in setenv() or if
the caller passed an invalid architecture name (e.g. one
with an '=' in it), so rather than requiring the callsite
to check for failure, make g_setenv() failure fatal here,
similarly to what we did in commit aca68d95c515.

Resolves: Coverity CID 1497485
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-id: 20240312183810.557768-8-peter.maydell@linaro.org


  Commit: 022356d79da100ba0af97b7c18a5351e58519d9f
      
https://github.com/qemu/qemu/commit/022356d79da100ba0af97b7c18a5351e58519d9f
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M migration/fd.c
    M migration/fd.h
    M migration/file.c
    M migration/migration.c
    M migration/multifd.c
    M tests/qtest/migration-test.c

  Log Message:
  -----------
  Merge tag 'migration-20240322-pull-request' of https://gitlab.com/peterx/qemu 
into staging

Migration pull for 9.0-rc1

- Fabiano's patch to revert fd: support on mapped-ram
- Peter's fix on postcopy regression on unnecessary dirty syncs
- Fabiano's fix on mapped-ram rare corrupt on zero page handling

# -----BEGIN PGP SIGNATURE-----
#
# iIgEABYKADAWIQS5GE3CDMRX2s990ak7X8zN86vXBgUCZf2uIxIccGV0ZXJ4QHJl
# ZGhhdC5jb20ACgkQO1/MzfOr1waqTgD/RjaWrcUYlHcfFcWlEQGrYqikCtZYI+oW
# YYdbLcCBOlQBAL/ecCbsFyaWyPnB1Eg3YFcj5g8AgogDHdg37HSxydgL
# =aWGi
# -----END PGP SIGNATURE-----
# gpg: Signature made Fri 22 Mar 2024 16:13:23 GMT
# gpg:                using EDDSA key B9184DC20CC457DACF7DD1A93B5FCCCDF3ABD706
# gpg:                issuer "peterx@redhat.com"
# gpg: Good signature from "Peter Xu <xzpeter@gmail.com>" [marginal]
# gpg:                 aka "Peter Xu <peterx@redhat.com>" [marginal]
# 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: B918 4DC2 0CC4 57DA CF7D  D1A9 3B5F CCCD F3AB D706

* tag 'migration-20240322-pull-request' of https://gitlab.com/peterx/qemu:
  migration/multifd: Fix clearing of mapped-ram zero pages
  migration/postcopy: Fix high frequency sync
  migration: Revert mapped-ram multifd support to fd: URI

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>


  Commit: 0cf74ffedd043813d8fc5549746e390017f56173
      
https://github.com/qemu/qemu/commit/0cf74ffedd043813d8fc5549746e390017f56173
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M hw/misc/pca9554.c
    M hw/nvram/mac_nvram.c
    M net/af-xdp.c
    M tests/qtest/libqtest.c
    M tests/qtest/npcm7xx_emc-test.c
    M tests/unit/socket-helpers.c
    M tests/unit/test-throttle.c

  Log Message:
  -----------
  Merge tag 'pull-target-arm-20240325-1' of 
https://git.linaro.org/people/pmaydell/qemu-arm into staging

target-arm queue:
 * Fixes for seven minor coverity issues

# -----BEGIN PGP SIGNATURE-----
#
# iQJNBAABCAA3FiEE4aXFk81BneKOgxXPPCUl7RQ2DN4FAmYBh5wZHHBldGVyLm1h
# eWRlbGxAbGluYXJvLm9yZwAKCRA8JSXtFDYM3lb8D/9XDbRFB3kIHVBaDxZyE4bs
# QH8u80C08f/PzJ5SQos5D+R07xtPid1dyeiLND/RvwZUN3WAGKf9pmPUQL4aluz5
# gHMalq/+nGNam2qz+tKTI0q0otndiJrGNlOYhw2QqFJ9GUp2T9e61izgw0XeQtzF
# GKm6aE8LytH7h2H9ndIpJFQDggqkQev/uZ625hwhYxo0ND5uRqBNE7Wjy104DULo
# oEGZBhIB2CtyDiQdxgCfC8TOXVT3NAEbk6carbYdGshrMTpWNsjOHbLVcsuqUaZC
# eeRnOprsQq+YE5aAByfipGgCuoGNE5rn6ZTrDpSdfLe8LFfU/hEASnOmIjMtMbSM
# HKhKcKKzvLk/KQZZNJCbh+MKl1GsTvXMrB/DjLaVu2643MyQY7XZu3/XX3PE6Zee
# WqJC+NazfXCdHDyYqfPELkmnpeS5Tka/PCoku1VNWmnr7Qr6SYIqzbxI+zCsbDCs
# uqDfxzwN1lTKCkgUD3SVQrmrQ3u9nTLCpTqmaEd6H3+0UgpEUBpW51bMPUxO3KIk
# ouvjVJ3oDSdNMyVrEl3zDoxykU99trRYbIRALrW+rd1ghn4SE0WorAGJ96GLGYP0
# QfFtveTmDqsfKOvxHfBx6gng0aQw0GK145uXLciRaPuX51wZGbAjp/Muhs6oswtR
# j7GgfYAbVdc1QwKTqBK0tw==
# =0H37
# -----END PGP SIGNATURE-----
# gpg: Signature made Mon 25 Mar 2024 14:18:04 GMT
# gpg:                using RSA key E1A5C593CD419DE28E8315CF3C2525ED14360CDE
# gpg:                issuer "peter.maydell@linaro.org"
# gpg: Good signature from "Peter Maydell <peter.maydell@linaro.org>" [ultimate]
# gpg:                 aka "Peter Maydell <pmaydell@gmail.com>" [ultimate]
# gpg:                 aka "Peter Maydell <pmaydell@chiark.greenend.org.uk>" 
[ultimate]
# gpg:                 aka "Peter Maydell <peter@archaic.org.uk>" [ultimate]
# Primary key fingerprint: E1A5 C593 CD41 9DE2 8E83  15CF 3C25 25ED 1436 0CDE

* tag 'pull-target-arm-20240325-1' of 
https://git.linaro.org/people/pmaydell/qemu-arm:
  tests/qtest/libqtest.c: Check for g_setenv() failure
  tests/unit/test-throttle: Avoid unintended integer division
  hw/nvram/mac_nvram: Report failure to write data
  hw/misc/pca9554: Correct error check bounds in get/set pin functions
  net/af-xdp.c: Don't leak sock_fds array in net_init_af_xdp()
  tests/unit/socket-helpers: Don't close(-1)
  tests/qtest/npcm7xx_emc_test: Don't leak cmd_line

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>


  Commit: 6a4180af9686830d88c387baab6d79563ce42a15
      
https://github.com/qemu/qemu/commit/6a4180af9686830d88c387baab6d79563ce42a15
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2024-03-25 (Mon, 25 Mar 2024)

  Changed paths:
    M .travis.yml
    M MAINTAINERS
    M hw/arm/aspeed.c
    M hw/arm/aspeed_ast10x0.c
    M hw/arm/aspeed_ast2600.c
    M hw/gpio/meson.build
    A hw/gpio/pca9552.c
    A hw/gpio/pca9554.c
    M hw/gpio/trace-events
    M hw/microblaze/xlnx-zynqmp-pmu.c
    M hw/misc/meson.build
    R hw/misc/pca9552.c
    R hw/misc/pca9554.c
    M hw/misc/trace-events
    A include/hw/gpio/pca9552.h
    A include/hw/gpio/pca9552_regs.h
    A include/hw/gpio/pca9554.h
    A include/hw/gpio/pca9554_regs.h
    R include/hw/misc/pca9552.h
    R include/hw/misc/pca9552_regs.h
    R include/hw/misc/pca9554.h
    R include/hw/misc/pca9554_regs.h
    M target/s390x/tcg/translate.c
    M tests/qtest/libqos/virtio.c
    M tests/qtest/pca9552-test.c
    M tests/qtest/pnv-host-i2c-test.c
    M tests/tcg/s390x/Makefile.target
    A tests/tcg/s390x/ts.c

  Log Message:
  -----------
  Merge tag 'pull-request-2024-03-25' of https://gitlab.com/thuth/qemu into 
staging

* Fix timeouts in Travis-CI jobs
* Mark devices with user_creatable = false that can crash QEMU otherwise
* Fix s390x TEST-AND-SET TCG instruction emulation
* Move pc955* devices to hw/gpio/

# -----BEGIN PGP SIGNATURE-----
#
# iQJFBAABCAAvFiEEJ7iIR+7gJQEY8+q5LtnXdP5wLbUFAmYBhdgRHHRodXRoQHJl
# ZGhhdC5jb20ACgkQLtnXdP5wLbVcfA/9FulEN4HrjD3ObyboA+WfibXURwChui98
# 8LvL/fAGe3BZXQtspuNmPyrKRtIOrIwHJyFuxf2N5+8BuvGhEHQIuvIhQIj/rvfy
# X14KlldmQ3w3HlI3Ud4YiebLyK3AAFC2ApIywzFsnN+HoaHJR2EyDIb+T7OsGJZf
# ZLE/Z7qANxoNeZ+a3+rQR3SVpijyS3fXxDSaILrq2uW4kCCs/55O8Rt3Qb+PFSVd
# fF+OlpG6o+z73ACZc1u9Io4IO1ZZc/NdkmDTNz4HknkvJLTLF6kOECAxLl0ytgAG
# YRzBGKes29Zpa9wn/9rc75/OYNS0Ks+B19sQnijWUNX0zq5FkReXNXiyVcbT7d4p
# 6jFzlFnjj4ifB8uQkZTGcx/lL4s4VkPzF+f7fgHq9CKNrNsx8uca0TyQ8s4y+NGb
# C98kJdHd+QhCcuNnAbifCwuFaxQ8C4BdgzxVbU/sGDKNkINNkiTp+uue4TxnRKvV
# MfhqdnWRvqgZ0Rl4TxqcNfODK72Z1YNv3933OKE/mRJYS1Q529TIq4vfp8WIMsWQ
# 7+ipo4WKXhkiSOJZD6AkCoFum1W8yaDzUDJTw2Xt2bPBL3+FXcQyKkKVUMfzIJ8M
# KLe0Bb9W/pYU1ToTciTP0dkQF/02tG0Vik273445wPgH0x8OyHJkPF/ny1a7lKFO
# 5jreYdMxWdc=
# =lfZM
# -----END PGP SIGNATURE-----
# gpg: Signature made Mon 25 Mar 2024 14:10:32 GMT
# gpg:                using RSA key 27B88847EEE0250118F3EAB92ED9D774FE702DB5
# gpg:                issuer "thuth@redhat.com"
# gpg: Good signature from "Thomas Huth <th.huth@gmx.de>" [full]
# gpg:                 aka "Thomas Huth <thuth@redhat.com>" [full]
# gpg:                 aka "Thomas Huth <huth@tuxfamily.org>" [full]
# gpg:                 aka "Thomas Huth <th.huth@posteo.de>" [unknown]
# Primary key fingerprint: 27B8 8847 EEE0 2501 18F3  EAB9 2ED9 D774 FE70 2DB5

* tag 'pull-request-2024-03-25' of https://gitlab.com/thuth/qemu:
  tests/tcg/s390x: Test TEST AND SET
  target/s390x: Use mutable temporary value for op_ts
  libqos/virtio.c: Correct 'flags' reading in qvirtqueue_kick
  misc/pca955*: Move models under hw/gpio
  aspeed: Make the ast1030-a1 SoC not user creatable
  aspeed: Make the ast2600-a3 SoC not user creatable
  hw/microblaze: Do not allow xlnx-zynqmp-pmu-soc to be created by the user
  .travis.yml: Remove the unused xfslib-dev package
  .travis.yml: Shorten the runtime of the problematic jobs

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>


Compare: https://github.com/qemu/qemu/compare/853546f81284...6a4180af9686

To unsubscribe from these emails, change your notification settings at 
https://github.com/qemu/qemu/settings/notifications



reply via email to

[Prev in Thread] Current Thread [Next in Thread]