Branch: refs/heads/staging
Home: https://github.com/qemu/qemu
Commit: 3f99cd59b28ddb5697fdc1e6c823c82cc01304ff
https://github.com/qemu/qemu/commit/3f99cd59b28ddb5697fdc1e6c823c82cc01304ff
Author: Peter Xu <[email protected]>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M migration/migration.c
Log Message:
-----------
migration: Cleanup migrate_fd_cleanup() on accessing to_dst_file
The cleanup function can in many cases needs cleanup on its own.
The major thing we want to do here is not referencing to_dst_file when
without the file mutex. When at it, touch things elsewhere too to make it
look slightly better in general.
One thing to mention is, migration_thread has its own "running" boolean, so
it doesn't need to rely on to_dst_file being non-NULL. Multifd has a
dependency so it needs to be skipped if to_dst_file is not yet set; add a
richer comment for such reason.
Resolves: Coverity CID 1527402
Reported-by: Peter Maydell <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: e50e6a197ad7695a7855a6d71b754a7d2b478e56
https://github.com/qemu/qemu/commit/e50e6a197ad7695a7855a6d71b754a7d2b478e56
Author: Peter Xu <[email protected]>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M migration/colo.c
M migration/dirtyrate.c
M migration/migration.c
M migration/migration.h
M migration/multifd.c
M migration/postcopy-ram.c
M migration/savevm.c
Log Message:
-----------
migration: Put thread names together with macros
Keep migration thread names together, so it's easier to see a list of all
possible migration threads.
Still two functional changes below besides the macro defintions:
- There's one dirty rate thread that we overlooked before, now we add
that too and name it as "mig/dirtyrate" following the old rules.
- The old name "mig/src/rp-thr" has "-thr" but it may not be useful if
it's a thread name anyway, while "rp" can be slightly hard to read.
Taking this chance to rename it to "mig/src/return", hopefully a better
name.
Reviewed-by: Fabiano Rosas <[email protected]>
Acked-by: Hyman Huang <[email protected]>
Reviewed-by: Zhang Chen <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: a2bfa8f3c78c2e87f6dc0b6e8b3c207cd89e1223
https://github.com/qemu/qemu/commit/a2bfa8f3c78c2e87f6dc0b6e8b3c207cd89e1223
Author: Hanna Czenczek <[email protected]>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M migration/vmstate.c
Log Message:
-----------
migration: Ensure vmstate_save() sets errp
migration/savevm.c contains some calls to vmstate_save() that are
followed by migrate_set_error() if the integer return value indicates an
error. migrate_set_error() requires that the `Error *` object passed to
it is set. Therefore, vmstate_save() is assumed to always set *errp on
error.
Right now, that assumption is not met: vmstate_save_state_v() (called
internally by vmstate_save()) will not set *errp if
vmstate_subsection_save() or vmsd->post_save() fail. Fix that by adding
an *errp parameter to vmstate_subsection_save(), and by generating a
generic error in case post_save() fails (as is already done for
pre_save()).
Without this patch, qemu will crash after vmstate_subsection_save() or
post_save() have failed inside of a vmstate_save() call (unless
migrate_set_error() then happen to discard the new error because
s->error is already set). This happens e.g. when receiving the state
from a virtio-fs back-end (virtiofsd) fails.
Signed-off-by: Hanna Czenczek <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: c6a2eae865a77ff59997a3dc91cbdc291e9d78fe
https://github.com/qemu/qemu/commit/c6a2eae865a77ff59997a3dc91cbdc291e9d78fe
Author: Hyman Huang <[email protected]>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M accel/tcg/icount-common.c
Log Message:
-----------
accel/tcg/icount-common: Remove the reference to the unused header file
Signed-off-by: Hyman Huang <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link:
https://lore.kernel.org/r/5e33b423d0b8506e5cb33fff42b50aa301b7731b.1729146786.git.yong.hu...@smartx.com
Signed-off-by: Peter Xu <[email protected]>
Commit: d7211bd139e6cdc5ed4574a04bef3defdd29353f
https://github.com/qemu/qemu/commit/d7211bd139e6cdc5ed4574a04bef3defdd29353f
Author: Hyman Huang <[email protected]>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M migration/migration.c
Log Message:
-----------
migration: Stop CPU throttling conditionally
Since CPU throttling only occurs when auto-converge
is on, stop it conditionally.
Signed-off-by: Hyman Huang <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link:
https://lore.kernel.org/r/f0c787080bb9ab0c37952f0ca5bfaa525d5ddd14.1729146786.git.yong.hu...@smartx.com
Signed-off-by: Peter Xu <[email protected]>
Commit: 9921d30ea6dd92c83e80589faae2da1b3b0c1123
https://github.com/qemu/qemu/commit/9921d30ea6dd92c83e80589faae2da1b3b0c1123
Author: Hyman Huang <[email protected]>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
R include/sysemu/cpu-throttle.h
A migration/cpu-throttle.c
A migration/cpu-throttle.h
M migration/meson.build
M migration/migration.c
M migration/ram.c
M migration/trace-events
R system/cpu-throttle.c
M system/cpu-timers.c
M system/meson.build
M system/trace-events
Log Message:
-----------
migration: Move cpu-throttole.c from system to migration
Move cpu-throttle.c from system to migration since it's
only used for migration; this makes us avoid exporting the
util functions and variables in misc.h but export them in
migration.h when implementing the periodic ramblock dirty
sync feature in the upcoming commits.
Since CPU throttle timers are only used in migration, move
their registry to migration_object_init.
Signed-off-by: Hyman Huang <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link:
https://lore.kernel.org/r/c1b3efaa0cb49e03d422e9da97bdb65cc3d234d1.1729146786.git.yong.hu...@smartx.com
Signed-off-by: Peter Xu <[email protected]>
Commit: a8becc46de1d3ad94d10cbac6141126d837c8a28
https://github.com/qemu/qemu/commit/a8becc46de1d3ad94d10cbac6141126d837c8a28
Author: Hyman Huang <[email protected]>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M migration/ram.c
Log Message:
-----------
migration: Remove "rs" parameter in migration_bitmap_sync_precopy
The global static variable ram_state in fact is referred to by the
"rs" parameter in migration_bitmap_sync_precopy. For ease of calling
by the callees, use the global variable directly in
migration_bitmap_sync_precopy and remove "rs" parameter.
The migration_bitmap_sync_precopy will be exported in the next commit.
Signed-off-by: Hyman Huang <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Link:
https://lore.kernel.org/r/283c335d61463bf477160da91b24da45cdaf3e43.1729146786.git.yong.hu...@smartx.com
Signed-off-by: Peter Xu <[email protected]>
Commit: 0a8ce3c59c85d099d6abda07e2a77e823268a1e7
https://github.com/qemu/qemu/commit/0a8ce3c59c85d099d6abda07e2a77e823268a1e7
Author: Hyman Huang <[email protected]>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M migration/cpu-throttle.c
M migration/cpu-throttle.h
M migration/migration.c
M migration/migration.h
M migration/ram.c
M migration/trace-events
Log Message:
-----------
migration: Support periodic RAMBlock dirty bitmap sync
When VM is configured with huge memory, the current throttle logic
doesn't look like to scale, because migration_trigger_throttle()
is only called for each iteration, so it won't be invoked for a long
time if one iteration can take a long time.
The periodic dirty sync aims to fix the above issue by synchronizing
the ramblock from remote dirty bitmap and, when necessary, triggering
the CPU throttle multiple times during a long iteration.
This is a trade-off between synchronization overhead and CPU throttle
impact.
Signed-off-by: Hyman Huang <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link:
https://lore.kernel.org/r/f61f1b3653f2acf026901103e1c73d157d38b08f.1729146786.git.yong.hu...@smartx.com
[peterx: make prev_cnt global, and reset for each migration]
Signed-off-by: Peter Xu <[email protected]>
Commit: 2b4abf4a1d30ef21e0adfd0958d7d404813aa33b
https://github.com/qemu/qemu/commit/2b4abf4a1d30ef21e0adfd0958d7d404813aa33b
Author: Hyman Huang <[email protected]>
Date: 2024-10-21 (Mon, 21 Oct 2024)
Changed paths:
M tests/qtest/migration-test.c
Log Message:
-----------
tests/migration: Add case for periodic ramblock dirty sync
Signed-off-by: Hyman Huang <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link:
https://lore.kernel.org/r/cb61504f1a1e9d5f2ca4dac12e518deb076ce9f3.1729146786.git.yong.hu...@smartx.com
Signed-off-by: Peter Xu <[email protected]>
Commit: 918d0de0728c3840e3c459202f9bdbcc690a5727
https://github.com/qemu/qemu/commit/918d0de0728c3840e3c459202f9bdbcc690a5727
Author: Cornelia Huck <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M hw/arm/virt.c
M target/arm/cpu.c
M target/arm/cpu.h
M target/arm/kvm.c
M target/arm/kvm_arm.h
Log Message:
-----------
arm/kvm: add support for MTE
Extend the 'mte' property for the virt machine to cover KVM as
well. For KVM, we don't allocate tag memory, but instead enable
the capability.
If MTE has been enabled, we need to disable migration, as we do not
yet have a way to migrate the tags as well. Therefore, MTE will stay
off with KVM unless requested explicitly.
[gankulkarni: This patch is rework of commit b320e21c48
which broke TCG since it made the TCG -cpu max
report the presence of MTE to the guest even if the board hadn't
enabled MTE by wiring up the tag RAM. This meant that if the guest
then tried to use MTE QEMU would segfault accessing the
non-existent tag RAM.]
Signed-off-by: Cornelia Huck <[email protected]>
Reviewed-by: Gustavo Romero <[email protected]>
Signed-off-by: Ganapatrao Kulkarni <[email protected]>
Message-id: [email protected]
Signed-off-by: Peter Maydell <[email protected]>
Commit: bda8c24cb564afe88d7ab713e44aeefdcb10ff63
https://github.com/qemu/qemu/commit/bda8c24cb564afe88d7ab713e44aeefdcb10ff63
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M docs/system/cpu-hotplug.rst
Log Message:
-----------
docs/system/cpu-hotplug: Update example's socket-id/core-id
The example of how to do vCPU hotplug and hot-unlpug in the
cpu-hotplug documentation no longer works, because the way we
allocate socket-id and core-id to CPUs by default has changed at some
point. The output also no longer matches what current QEMU produces
in some more cosmetic ways.
Update the example to match current QEMU. The differences are:
* the second CPU is now socket-id=0 core-id=1,
not socket-id=1 core-id=0
* the order of fields in QMP responses is now in alphabetical order
* the "arch" member is no longer present in the query-cpus-fast
output (it was removed in QEMU 6.0)
Signed-off-by: Peter Maydell <[email protected]>
Acked-by: Igor Mammedov <[email protected]>
Message-id: [email protected]
Message-id: [email protected]
Commit: d9c7adb6019f2ac3d6a5a36c4121341f4b6424af
https://github.com/qemu/qemu/commit/d9c7adb6019f2ac3d6a5a36c4121341f4b6424af
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M target/arm/vfp_helper.c
Log Message:
-----------
target/arm: Store FPSR cumulative exception bits in env->vfp.fpsr
Currently we store the FPSR cumulative exception bits in the
float_status fields, and use env->vfp.fpsr only for the NZCV bits.
(The QC bit is stored in env->vfp.qc[].)
This works for TCG, but if QEMU was built without CONFIG_TCG (i.e.
with KVM support only) then we use the stub versions of
vfp_get_fpsr_from_host() and vfp_set_fpsr_to_host() which do nothing,
throwing away the cumulative exception bit state. The effect is that
if the FPSR state is round-tripped from KVM to QEMU then we lose the
cumulative exception bits. In particular, this will happen if the VM
is migrated. There is no user-visible bug when using KVM with a QEMU
binary that was built with CONFIG_TCG.
Fix this by always storing the cumulative exception bits in
env->vfp.fpsr. If we are using TCG then we may also keep pending
cumulative exception information in the float_status fields, so we
continue to fold that in on reads.
This change will also be helpful for implementing FEAT_AFP later,
because that includes a feature where in some situations we want to
cause input denormals to be flushed to zero without affecting the
existing state of the FPSR.IDC bit, so we need a place to store IDC
which is distinct from the various float_status fields.
(Note for stable backports: the bug goes back to 4a15527c9fee but
this code was refactored in commits ea8618382aba..a8ab8706d4cc461, so
fixing it in branches without those refactorings will mean either
backporting the refactor or else implementing a conceptually similar
fix for the old code.)
Cc: [email protected]
Fixes: 4a15527c9fee ("target/arm/vfp_helper: Restrict the SoftFloat use to TCG")
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Richard Henderson <[email protected]>
Message-id: [email protected]
Commit: 1505b651fdbd9af59a4a90876a62ae7ea2d4cd39
https://github.com/qemu/qemu/commit/1505b651fdbd9af59a4a90876a62ae7ea2d4cd39
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M target/arm/internals.h
Log Message:
-----------
target/arm: Don't assert in regime_is_user() for E10 mmuidx values
In regime_is_user() we assert if we're passed an ARMMMUIdx_E10_*
mmuidx value. This used to make sense because we only used this
function in ptw.c and would never use it on this kind of stage 1+2
mmuidx, only for an individual stage 1 or stage 2 mmuidx.
However, when we implemented FEAT_E0PD we added a callsite in
aa64_va_parameters(), which means this can now be called for
stage 1+2 mmuidx values if the guest sets the TCG_ELX.{E0PD0,E0PD1}
bits to enable use of the feature. This will then result in
an assertion failure later, for instance on a TLBI operation:
#6 0x00007ffff6d0e70f in g_assertion_message_expr
(domain=0x0, file=0x55555676eeba "../../target/arm/internals.h", line=978,
func=0x555556771d48 <__func__.5> "regime_is_user", expr=<optimised out>)
at ../../../glib/gtestutils.c:3279
#7 0x0000555555f286d2 in regime_is_user (env=0x555557f2fe00,
mmu_idx=ARMMMUIdx_E10_0) at ../../target/arm/internals.h:978
#8 0x0000555555f3e31c in aa64_va_parameters (env=0x555557f2fe00,
va=18446744073709551615, mmu_idx=ARMMMUIdx_E10_0, data=true, el1_is_aa32=false)
at ../../target/arm/helper.c:12048
#9 0x0000555555f3163b in tlbi_aa64_get_range (env=0x555557f2fe00,
mmuidx=ARMMMUIdx_E10_0, value=106721347371041) at ../../target/arm/helper.c:5214
#10 0x0000555555f317e8 in do_rvae_write (env=0x555557f2fe00,
value=106721347371041, idxmap=21, synced=true) at ../../target/arm/helper.c:5260
#11 0x0000555555f31925 in tlbi_aa64_rvae1is_write (env=0x555557f2fe00,
ri=0x555557fbeae0, value=106721347371041) at ../../target/arm/helper.c:5302
#12 0x0000555556036f8f in helper_set_cp_reg64 (env=0x555557f2fe00,
rip=0x555557fbeae0, value=106721347371041) at
../../target/arm/tcg/op_helper.c:965
Since we do know whether these mmuidx values are for usermode
or not, we can easily make regime_is_user() handle them:
ARMMMUIdx_E10_0 is user, and the other two are not.
Cc: [email protected]
Fixes: e4c93e44ab103f ("target/arm: Implement FEAT_E0PD")
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Richard Henderson <[email protected]>
Reviewed-by: Alex Bennée <[email protected]>
Tested-by: Alex Bennée <[email protected]>
Message-id: [email protected]
Commit: 77dd098a5e790e3ede0dea5ddd5f690086fe608c
https://github.com/qemu/qemu/commit/77dd098a5e790e3ede0dea5ddd5f690086fe608c
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M hw/sd/omap_mmc.c
M hw/sd/sd.c
M include/hw/sd/sd.h
Log Message:
-----------
hw/sd/omap_mmc: Don't use sd_cmd_type_t
In commit 1ab08790bb75e4 we did some refactoring of the SD card
implementation, which included a rearrangement of the sd_cmd_type_t
enum values. Unfortunately we didn't notice that this enum is not
used solely inside the SD card model itself, but is also used by the
OMAP MMC controller device. In the OMAP MMC controller, it is used
to implement the handling of the Type field of the MMC_CMD register,
so changing the enum values so that they no longer lined up with the
bit definitions for that register field broke the controller model.
The effect is that Linux fails to boot from an SD card on the "sx1"
machine.
Give omap-mmc its own enum which we can document as needing to match
the encoding used in this device's register, so it isn't sharing
sd_cmd_type_t with the SD card model any more. We can then move
sd_cmd_type_t's definition out of sd.h and into sd.c, which is the
only place that uses it.
Cc: [email protected]
Fixes: 1ab08790bb75 ("hw/sd/sdcard: Store command type in SDProto")
Signed-off-by: Peter Maydell <[email protected]>
Tested-by: Guenter Roeck <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Message-id: [email protected]
Commit: aff835834b745b5a60483aa436b7f3db4c45c753
https://github.com/qemu/qemu/commit/aff835834b745b5a60483aa436b7f3db4c45c753
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M MAINTAINERS
M tests/functional/meson.build
A tests/functional/test_arm_collie.py
Log Message:
-----------
tests/functional: Add a functional test for the collie board
Add a functional test for the collie board that uses the kernel and
rootfs provided by Guenter Roeck in the linux-test-downloads repo:
https://github.com/groeck/linux-test-downloads/
This just boots Linux with a userspace that immediately reboots
the board, so we wait for the reboot log line.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Message-id: [email protected]
Commit: bc4d45b275fe63184a633d7d4f2ea2959b1fa4e7
https://github.com/qemu/qemu/commit/bc4d45b275fe63184a633d7d4f2ea2959b1fa4e7
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M tests/functional/meson.build
A tests/functional/test_arm_sx1.py
Log Message:
-----------
tests/functional: Add a functional test for the sx1 board
Add a functional test for the sx1 board that uses the kernel and
rootfs provided by Guenter Roeck in the linux-test-downloads repo:
https://github.com/groeck/linux-test-downloads/
We have three variants of the test for this board:
* just boot initrd
* boot with filesystem on SD card
* boot from flash
In all cases these images have a userspace that is configured to
immediately reboot the system on successful boot, and the board
itself supports telling QEMU to do the reboot, so we only need to
wait for QEMU to exit (via -no-reboot).
Since there are three subtests, the test as a whole takes about
80s on my local machine. That's about the same as the aarch64_virt
test, so give it the same overall test timeout as that one.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Message-id: [email protected]
Commit: a3c3345cac7d2f9cc827d7ecce915795244ac230
https://github.com/qemu/qemu/commit/a3c3345cac7d2f9cc827d7ecce915795244ac230
Author: Akihiko Odaki <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M scripts/symlink-install-tree.py
Log Message:
-----------
scripts/symlink-install-tree.py: Fix MESONINTROSPECT parsing
The arguments in MESONINTROSPECT are quoted with shlex.quote() so it
must be parsed with shlex.split(). Otherwise the script will fail if
the build directory has a character like "~" in it.
Note: this fix cannot be backported directly to any stable branch
that doesn't require Meson version 1.4.0 or better; otherwise it will
work OK on Linux but will break on Windows hosts.
(Unfortunately, Meson prior to version 1.4.0 was inconsistent between
host OSes about how it quoted arguments, and used a different quoting
process on Windows hosts. Our current git trunk already requires
1.5.0 as of commit 07f0d32641e ("Require meson version 1.5.0"), but
the stable branches are still on older Meson.)
Fixes: cf60ccc330 ("cutils: Introduce bundle mechanism")
Reported-by: Michael Tokarev <[email protected]>
Signed-off-by: Akihiko Odaki <[email protected]>
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Pierrick Bouvier <[email protected]>
Tested-by: Pierrick Bouvier <[email protected]>
Message-id: [email protected]
[PMM: Updated commit message to give all the detail about the
Meson version compability requirements.]
Signed-off-by: Peter Maydell <[email protected]>
Commit: 800cbbfb01a3e5dece01dea6b7133c0a4c02e856
https://github.com/qemu/qemu/commit/800cbbfb01a3e5dece01dea6b7133c0a4c02e856
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M docs/system/arm/stm32.rst
Log Message:
-----------
docs/system/arm/stm32: List olimex-stm32-h405 in document title
List the olimex-stm32-h405 board in the document title, so that the
board name appears in the table of contents in system/target-arm.rst.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Alex Bennée <[email protected]>
Reviewed-by: Cédric Le Goater <[email protected]>
Message-id: [email protected]
Commit: 23a26bfeea5a9c831067cb0c4529d7c067b79564
https://github.com/qemu/qemu/commit/23a26bfeea5a9c831067cb0c4529d7c067b79564
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M docs/system/arm/aspeed.rst
M docs/system/arm/nuvoton.rst
Log Message:
-----------
docs/system/arm: Don't use wildcard '*-bmc' in doc titles
We have two Arm board doc files which both use '*-bmc' in their
documentation title. The result is that when you read the
table of contents in system/target-arm.html you don't know
which boards are covered by which file.
Expand out the board names entirely in the document titles.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Alex Bennée <[email protected]>
Reviewed-by: Cédric Le Goater <[email protected]>
Message-id: [email protected]
Commit: 6a98e614e5cc3ae9aa15a6bdf30fbdb4472bf2ff
https://github.com/qemu/qemu/commit/6a98e614e5cc3ae9aa15a6bdf30fbdb4472bf2ff
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M MAINTAINERS
M docs/system/arm/aspeed.rst
A docs/system/arm/fby35.rst
M docs/system/target-arm.rst
Log Message:
-----------
docs/system/arm: Split fby35 out from aspeed.rst
The fby35 machine is not implemented in hw/arm/aspeed.c,
but its documentation is currently stuck at the end of aspeed.rst,
formatted in a way that it gets its own heading in the top-level
list of boards in target-arm.html.
We don't have any other boards that we document like this; split it
out into its own rst file. This improves consistency with other
board docs and means we can have the entry in the target-arm
list be in the correct alphabetical order.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Alex Bennée <[email protected]>
Reviewed-by: Cédric Le Goater <[email protected]>
Message-id: [email protected]
Commit: f99e1d314d655561a0022902563eb5bffc260dc0
https://github.com/qemu/qemu/commit/f99e1d314d655561a0022902563eb5bffc260dc0
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M MAINTAINERS
A docs/system/arm/exynos.rst
M docs/system/target-arm.rst
Log Message:
-----------
docs/system/arm: Add placeholder doc for exynos4 boards
Add a placeholder doc for the exynos4 boards nuri and smdkc210.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Alex Bennée <[email protected]>
Reviewed-by: Cédric Le Goater <[email protected]>
Message-id: [email protected]
Commit: 6128720af88eb9b5b3857f88785d32bc052049a7
https://github.com/qemu/qemu/commit/6128720af88eb9b5b3857f88785d32bc052049a7
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M MAINTAINERS
A docs/system/arm/xlnx-zcu102.rst
M docs/system/target-arm.rst
Log Message:
-----------
docs/system/arm: Add placeholder doc for xlnx-zcu102 board
Add a placeholder doc for the xlnx-zcu102 board.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Alex Bennée <[email protected]>
Reviewed-by: Cédric Le Goater <[email protected]>
Reviewed-by: Alistair Francis <[email protected]>
Message-id: [email protected]
Commit: 946f9ef267f3da3a24cc052a337bfd5d54347e52
https://github.com/qemu/qemu/commit/946f9ef267f3da3a24cc052a337bfd5d54347e52
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M MAINTAINERS
A docs/system/arm/mcimx6ul-evk.rst
A docs/system/arm/mcimx7d-sabre.rst
M docs/system/target-arm.rst
Log Message:
-----------
docs/system/arm: Add placeholder docs for mcimx6ul-evk and mcimx7d-sabre
Add placeholder docs for the mcimx6ul-evk and mcimx7d-sabre boards.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Alex Bennée <[email protected]>
Reviewed-by: Cédric Le Goater <[email protected]>
Reviewed-by: Alistair Francis <[email protected]>
Message-id: [email protected]
Commit: a892728021e581019cbc9d6d19c4f20cdcd1afa0
https://github.com/qemu/qemu/commit/a892728021e581019cbc9d6d19c4f20cdcd1afa0
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M docs/system/target-arm.rst
Log Message:
-----------
docs/system/target-arm.rst: Remove "many boards are undocumented" note
We now have at least placeholder documentation for every Arm board,
so we can remove the apologetic note that says that there are
undocumented ones which you can only find out about via the
``--machine help`` option.
Signed-off-by: Peter Maydell <[email protected]>
Reviewed-by: Alex Bennée <[email protected]>
Reviewed-by: Cédric Le Goater <[email protected]>
Reviewed-by: Alistair Francis <[email protected]>
Message-id: [email protected]
Commit: bab209af35037b33f7eb1b8a3737085935bec3a3
https://github.com/qemu/qemu/commit/bab209af35037b33f7eb1b8a3737085935bec3a3
Author: Ido Plat <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M target/arm/tcg/helper-a64.c
Log Message:
-----------
target/arm: Fix arithmetic underflow in SETM instruction
Pass the stage size to step function callback, otherwise do_setm
would hang when size is larger then page size because stage size
would underflow. This fix changes do_setm to be more inline with
do_setp.
Cc: [email protected]
Fixes: 0e92818887dee ("target/arm: Implement the SET* instructions")
Signed-off-by: Ido Plat <[email protected]>
Reviewed-by: Richard Henderson <[email protected]>
Message-id: [email protected]
Signed-off-by: Peter Maydell <[email protected]>
Commit: 361dfa9757e8b7c233592f4d235b63aa834ce57a
https://github.com/qemu/qemu/commit/361dfa9757e8b7c233592f4d235b63aa834ce57a
Author: Peter Maydell <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M docs/devel/reset.rst
Log Message:
-----------
docs/devel/reset: Fix minor grammatical error
Fix a minor grammatical error in the reset documentation:
a couple of missing words and a singular/plural swap.
Signed-off-by: Axel Heider <[email protected]>
Message-id: [email protected]
[PMM: squashed two patches into one, tweaked commit message]
Reviewed-by: Peter Maydell <[email protected]>
Signed-off-by: Peter Maydell <[email protected]>
Commit: 84f298ea3e2f0627c09871561e55068db9ff9180
https://github.com/qemu/qemu/commit/84f298ea3e2f0627c09871561e55068db9ff9180
Author: Paolo Bonzini <[email protected]>
Date: 2024-10-29 (Tue, 29 Oct 2024)
Changed paths:
M hw/intc/arm_gic_kvm.c
M target/arm/kvm.c
M target/arm/kvm_arm.h
Log Message:
-----------
target/arm: kvm: require KVM_CAP_DEVICE_CTRL
The device control API was added in 2013, assume that it is present.
Signed-off-by: Paolo Bonzini <[email protected]>
Message-id: [email protected]
Reviewed-by: Peter Maydell <[email protected]>
Signed-off-by: Peter Maydell <[email protected]>
Commit: 33f040013fe67bd78b5d24b227d68aa321e5d74e
https://github.com/qemu/qemu/commit/33f040013fe67bd78b5d24b227d68aa321e5d74e
Author: Thomas Huth <[email protected]>
Date: 2024-10-30 (Wed, 30 Oct 2024)
Changed paths:
M migration/dirtyrate.c
Log Message:
-----------
migration/dirtyrate: Silence warning about strcpy() on OpenBSD
The linker on OpenBSD complains:
ld: warning: dirtyrate.c:447 (../src/migration/dirtyrate.c:447)(...):
warning: strcpy() is almost always misused, please use strlcpy()
It's currently not a real problem in this case since both arrays
have the same size (256 bytes). But just in case somebody changes
the size of the source array in the future, let's better play safe
and use g_strlcpy() here instead, with an additional check that the
string has been copied as a whole.
Signed-off-by: Thomas Huth <[email protected]>
Reviewed-by: Hyman Huang <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[peterx: Fix over-80 chars]
Signed-off-by: Peter Xu <[email protected]>
Commit: b623155e0145c6e550e14c748fe3f0031222498d
https://github.com/qemu/qemu/commit/b623155e0145c6e550e14c748fe3f0031222498d
Author: Peter Xu <[email protected]>
Date: 2024-10-30 (Wed, 30 Oct 2024)
Changed paths:
M docs/about/deprecated.rst
M qapi/migration.json
Log Message:
-----------
migration: Deprecate query-migrationthreads command
Per previous discussion [1,2], this patch deprecates query-migrationthreads
command.
To summarize, the major reason of the deprecation is due to no sensible way
to consume the API properly:
(1) The reported list of threads are incomplete (ignoring destination
threads and non-multifd threads).
(2) For CPU pinning, there's no way to properly pin the threads with
the API if the threads will start running right away after migration
threads can be queried, so the threads will always run on the default
cores for a short window.
(3) For VM debugging, one can use "-name $VM,debug-threads=on" instead,
which will provide proper names for all migration threads.
[1] https://lore.kernel.org/r/[email protected]
[2] https://lore.kernel.org/r/[email protected]
Reviewed-by: Fabiano Rosas <[email protected]>
Acked-by: Markus Armbruster <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 768deea481d0d1f60a97c8edc2b0c9eeec0e0b73
https://github.com/qemu/qemu/commit/768deea481d0d1f60a97c8edc2b0c9eeec0e0b73
Author: Peter Xu <[email protected]>
Date: 2024-10-30 (Wed, 30 Oct 2024)
Changed paths:
M migration/migration.c
Log Message:
-----------
migration: Take migration object refcount earlier for threads
Both migration thread or background snapshot thread will take a refcount of
the migration object at the entrace of the thread function.
That makes sense, because it protects the object from being freed by the
main thread in migration_shutdown() later, but it might still race with it
if the thread is scheduled too late. Consider the case right after
pthread_create() happened, VM shuts down with the object released, but
right after that the migration thread finally got created, referencing
MigrationState* in the opaque pointer which is already freed.
The only 100% safe way to make sure it won't get freed is taking the
refcount right before the thread is created, meanwhile when BQL is held.
Reviewed-by: Cédric Le Goater <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 589b58e5e6a9a8564a61c80528111931262dc8ff
https://github.com/qemu/qemu/commit/589b58e5e6a9a8564a61c80528111931262dc8ff
Author: Peter Xu <[email protected]>
Date: 2024-10-30 (Wed, 30 Oct 2024)
Changed paths:
M include/migration/misc.h
M migration/migration.h
Log Message:
-----------
migration: Unexport dirty_bitmap_mig_init()
It's only used within migration/, so it shouldn't be exported.
Reviewed-by: Cédric Le Goater <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 28c01bd24d508b05a5b75b11b4d6aa36249cf298
https://github.com/qemu/qemu/commit/28c01bd24d508b05a5b75b11b4d6aa36249cf298
Author: Peter Xu <[email protected]>
Date: 2024-10-30 (Wed, 30 Oct 2024)
Changed paths:
M include/migration/misc.h
M migration/ram.h
Log Message:
-----------
migration: Unexport ram_mig_init()
It's only used within migration/.
Reviewed-by: Cédric Le Goater <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: d3ffd69538f024b7d3946c53a2075bcdb10075ce
https://github.com/qemu/qemu/commit/d3ffd69538f024b7d3946c53a2075bcdb10075ce
Author: Peter Xu <[email protected]>
Date: 2024-10-30 (Wed, 30 Oct 2024)
Changed paths:
M hw/vfio/common.c
M include/migration/misc.h
M migration/migration.c
M migration/ram.c
M net/vhost-vdpa.c
Log Message:
-----------
migration: Drop migration_is_setup_or_active()
This helper is mostly the same as migration_is_running(), except that one
has COLO reported as true, the other has CANCELLING reported as true.
Per my past years experience on the state changes, none of them should
matter.
To make it slightly safer, report both COLO || CANCELLING to be true in
migration_is_running(), then drop the other one. We kept the 1st only
because the name is simpler, and clear enough.
Reviewed-by: Cédric Le Goater <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: dce7ad48d018d4b5fa99ebd94c307c0775442ad3
https://github.com/qemu/qemu/commit/dce7ad48d018d4b5fa99ebd94c307c0775442ad3
Author: Peter Xu <[email protected]>
Date: 2024-10-30 (Wed, 30 Oct 2024)
Changed paths:
M hw/virtio/virtio-mem.c
M include/migration/misc.h
M migration/migration.c
M migration/ram.c
M system/qdev-monitor.c
Log Message:
-----------
migration: Drop migration_is_idle()
Now with the current migration_is_running(), it will report exactly the
opposite of what will be reported by migration_is_idle().
Drop migration_is_idle(), instead use "!migration_is_running()" which
should be identical on functionality.
In reality, most of the idle check is inverted, so it's even easier to
write with "migrate_is_running()" check.
Reviewed-by: Cédric Le Goater <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 106ad11e2f0bf78be3e1b1ce9ef939394fc71940
https://github.com/qemu/qemu/commit/106ad11e2f0bf78be3e1b1ce9ef939394fc71940
Author: Maciej S. Szmigiero <[email protected]>
Date: 2024-10-30 (Wed, 30 Oct 2024)
Changed paths:
M migration/ram.c
M migration/trace-events
Log Message:
-----------
migration/ram: Add load start trace event
There's a RAM load complete trace event but there wasn't its start equivalent.
Signed-off-by: Maciej S. Szmigiero <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link:
https://lore.kernel.org/r/94ddfa7ecb83a78f73b82867dd30c8767592d257.1730203967.git.maciej.szmigi...@oracle.com
Signed-off-by: Peter Xu <[email protected]>
Commit: 53a60118d2654dd8e595e61f4e767ff747fd0b69
https://github.com/qemu/qemu/commit/53a60118d2654dd8e595e61f4e767ff747fd0b69
Author: Maciej S. Szmigiero <[email protected]>
Date: 2024-10-30 (Wed, 30 Oct 2024)
Changed paths:
M migration/multifd.c
Log Message:
-----------
migration/multifd: Zero p->flags before starting filling a packet
This way there aren't stale flags there.
p->flags can't contain SYNC to be sent at the next RAM packet since syncs
are now handled separately in multifd_send_thread.
Reviewed-by: Fabiano Rosas <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Signed-off-by: Maciej S. Szmigiero <[email protected]>
Link:
https://lore.kernel.org/r/1c96b6cdb797e6f035eb1a4ad9bfc24f4c7f5df8.1730203967.git.maciej.szmigi...@oracle.com
Signed-off-by: Peter Xu <[email protected]>
Commit: 6029f14e8f7260a3d399a81d6e3ed4ac51db1600
https://github.com/qemu/qemu/commit/6029f14e8f7260a3d399a81d6e3ed4ac51db1600
Author: Peter Maydell <[email protected]>
Date: 2024-10-31 (Thu, 31 Oct 2024)
Changed paths:
M MAINTAINERS
M docs/devel/reset.rst
M docs/system/arm/aspeed.rst
A docs/system/arm/exynos.rst
A docs/system/arm/fby35.rst
A docs/system/arm/mcimx6ul-evk.rst
A docs/system/arm/mcimx7d-sabre.rst
M docs/system/arm/nuvoton.rst
M docs/system/arm/stm32.rst
A docs/system/arm/xlnx-zcu102.rst
M docs/system/cpu-hotplug.rst
M docs/system/target-arm.rst
M hw/arm/virt.c
M hw/intc/arm_gic_kvm.c
M hw/sd/omap_mmc.c
M hw/sd/sd.c
M include/hw/sd/sd.h
M scripts/symlink-install-tree.py
M target/arm/cpu.c
M target/arm/cpu.h
M target/arm/internals.h
M target/arm/kvm.c
M target/arm/kvm_arm.h
M target/arm/tcg/helper-a64.c
M target/arm/vfp_helper.c
M tests/functional/meson.build
A tests/functional/test_arm_collie.py
A tests/functional/test_arm_sx1.py
Log Message:
-----------
Merge tag 'pull-target-arm-20241029' of
https://git.linaro.org/people/pmaydell/qemu-arm into staging
target-arm queue:
* arm/kvm: add support for MTE
* docs/system/cpu-hotplug: Update example's socket-id/core-id
* target/arm: Store FPSR cumulative exception bits in env->vfp.fpsr
* target/arm: Don't assert in regime_is_user() for E10 mmuidx values
* hw/sd/omap_mmc: Fix breakage of OMAP MMC controller
* tests/functional: Add functional tests for collie, sx1
* scripts/symlink-install-tree.py: Fix MESONINTROSPECT parsing
* docs/system/arm: Document remaining undocumented boards
* target/arm: Fix arithmetic underflow in SETM instruction
* docs/devel/reset: Fix minor grammatical error
* target/arm: kvm: require KVM_CAP_DEVICE_CTRL
# -----BEGIN PGP SIGNATURE-----
#
# iQJNBAABCAA3FiEE4aXFk81BneKOgxXPPCUl7RQ2DN4FAmcg+oYZHHBldGVyLm1h
# eWRlbGxAbGluYXJvLm9yZwAKCRA8JSXtFDYM3g/KD/4tzAD2zkWpnIPhY5ht4wBz
# Kioy+pnXJW5I6pAS4ljnI41pOFnPr6Ln1NfGkP+9pTND8lIQNY0Te2a/NjgEiYJc
# rYJ/A6UUuCqQ8+/oWWMPETcbbiKcSS2mzCJ/pNXeIquK5Co0Qk7mzdfObudwZpbw
# o3Cc9YrGZc64XAl2Rb83Oy2UHo1xjmV67wtEmcj+hmWC+tFc7pQpAKwIKcBMgns8
# ZILexX18RYZMDqQZQ5tvwTccJeFmljj9PyScou787RXK93BlF3sL/ypq1xMykRru
# JpMwAI6jD5LG9NO2zNr3FpBef8sJXqNF+O0DcYmhrKBwRkztuEU6DXF6xzdz/HRa
# c14hWK1jHku+HvKBXx3c5wibTbTU71Jv36Gw5VjOBQe/5cdKJAbZw8OH+IK8ozk9
# GwLVQ/JzrIi5m8FwXPwmkOPLX/CY8Wot6IWdJKKGTN8bY+9Cu2gTduFJIvi96HWU
# xkG1ySN61wKUR8Z26mizim2nBvQjybjqKEhrtQ21K548j4pWFVBgXJQX0Menca/v
# ziSLCd84Pmh9+DtElPCUyau/nX/jyUJ1gCScvcJjF5jAMPBREpAh53j/GL9JEgX6
# 9cX2WG6o+9R4Qcrh1O3Vy1bAUcJ27Tr2NitD+g5XObZ+vC6YgqfN2/M53so4rwws
# N4KCRdV6GcU70bQAul3mLQ==
# =KWM2
# -----END PGP SIGNATURE-----
# gpg: Signature made Tue 29 Oct 2024 15:08:54 GMT
# gpg: using RSA key E1A5C593CD419DE28E8315CF3C2525ED14360CDE
# gpg: issuer "[email protected]"
# gpg: Good signature from "Peter Maydell <[email protected]>" [ultimate]
# gpg: aka "Peter Maydell <[email protected]>" [ultimate]
# gpg: aka "Peter Maydell <[email protected]>"
[ultimate]
# gpg: aka "Peter Maydell <[email protected]>" [ultimate]
# Primary key fingerprint: E1A5 C593 CD41 9DE2 8E83 15CF 3C25 25ED 1436 0CDE
* tag 'pull-target-arm-20241029' of
https://git.linaro.org/people/pmaydell/qemu-arm:
target/arm: kvm: require KVM_CAP_DEVICE_CTRL
docs/devel/reset: Fix minor grammatical error
target/arm: Fix arithmetic underflow in SETM instruction
docs/system/target-arm.rst: Remove "many boards are undocumented" note
docs/system/arm: Add placeholder docs for mcimx6ul-evk and mcimx7d-sabre
docs/system/arm: Add placeholder doc for xlnx-zcu102 board
docs/system/arm: Add placeholder doc for exynos4 boards
docs/system/arm: Split fby35 out from aspeed.rst
docs/system/arm: Don't use wildcard '*-bmc' in doc titles
docs/system/arm/stm32: List olimex-stm32-h405 in document title
scripts/symlink-install-tree.py: Fix MESONINTROSPECT parsing
tests/functional: Add a functional test for the sx1 board
tests/functional: Add a functional test for the collie board
hw/sd/omap_mmc: Don't use sd_cmd_type_t
target/arm: Don't assert in regime_is_user() for E10 mmuidx values
target/arm: Store FPSR cumulative exception bits in env->vfp.fpsr
docs/system/cpu-hotplug: Update example's socket-id/core-id
arm/kvm: add support for MTE
Signed-off-by: Peter Maydell <[email protected]>
Commit: 2992b1c7b4558e7e5cfd0f3c264b780a31092609
https://github.com/qemu/qemu/commit/2992b1c7b4558e7e5cfd0f3c264b780a31092609
Author: Peter Maydell <[email protected]>
Date: 2024-10-31 (Thu, 31 Oct 2024)
Changed paths:
M accel/tcg/icount-common.c
M docs/about/deprecated.rst
M hw/vfio/common.c
M hw/virtio/virtio-mem.c
M include/migration/misc.h
R include/sysemu/cpu-throttle.h
M migration/colo.c
A migration/cpu-throttle.c
A migration/cpu-throttle.h
M migration/dirtyrate.c
M migration/meson.build
M migration/migration.c
M migration/migration.h
M migration/multifd.c
M migration/postcopy-ram.c
M migration/ram.c
M migration/ram.h
M migration/savevm.c
M migration/trace-events
M migration/vmstate.c
M net/vhost-vdpa.c
M qapi/migration.json
R system/cpu-throttle.c
M system/cpu-timers.c
M system/meson.build
M system/qdev-monitor.c
M system/trace-events
M tests/qtest/migration-test.c
Log Message:
-----------
Merge tag 'migration-20241030-pull-request' of https://gitlab.com/peterx/qemu
into staging
Migration pull request for softfreeze
NOTE: checkpatch.pl could report a false positive on this branch:
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#21:
{include/sysemu => migration}/cpu-throttle.h | 0
That's covered by "F: migration/" entry.
Changelog:
- Peter's cleanup patch on migrate_fd_cleanup()
- Peter's cleanup patch to introduce thread name macros
- Hanna's error path fix for vmstate subsection save()s
- Hyman's auto converge enhancement on background dirty sync
- Peter's additional tracepoints for save state entries
- Thomas's build fix for OpenBSD in dirtyrate.c
- Peter's deprecation of query-migrationthreads command
- Peter's cleanup/fixes from the "export misc.h" series
- Maciej's two small patches from multifd+vfio series
# -----BEGIN PGP SIGNATURE-----
#
# iIgEABYKADAWIQS5GE3CDMRX2s990ak7X8zN86vXBgUCZyJXUBIccGV0ZXJ4QHJl
# ZGhhdC5jb20ACgkQO1/MzfOr1wa9nwD/V57Wy+kLqfVN+BZlUWLR/ByA2p8B5Q2J
# cBbXiZhafxYBALDJPsiTMMwUUDc0zMBTX0/UnaGasHlKTUKLqFqvOUAE
# =gcbJ
# -----END PGP SIGNATURE-----
# gpg: Signature made Wed 30 Oct 2024 15:57:04 GMT
# gpg: using EDDSA key B9184DC20CC457DACF7DD1A93B5FCCCDF3ABD706
# gpg: issuer "[email protected]"
# gpg: Good signature from "Peter Xu <[email protected]>" [marginal]
# gpg: aka "Peter Xu <[email protected]>" [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-20241030-pull-request' of https://gitlab.com/peterx/qemu:
migration/multifd: Zero p->flags before starting filling a packet
migration/ram: Add load start trace event
migration: Drop migration_is_idle()
migration: Drop migration_is_setup_or_active()
migration: Unexport ram_mig_init()
migration: Unexport dirty_bitmap_mig_init()
migration: Take migration object refcount earlier for threads
migration: Deprecate query-migrationthreads command
migration/dirtyrate: Silence warning about strcpy() on OpenBSD
tests/migration: Add case for periodic ramblock dirty sync
migration: Support periodic RAMBlock dirty bitmap sync
migration: Remove "rs" parameter in migration_bitmap_sync_precopy
migration: Move cpu-throttole.c from system to migration
migration: Stop CPU throttling conditionally
accel/tcg/icount-common: Remove the reference to the unused header file
migration: Ensure vmstate_save() sets errp
migration: Put thread names together with macros
migration: Cleanup migrate_fd_cleanup() on accessing to_dst_file
Signed-off-by: Peter Maydell <[email protected]>
Compare: https://github.com/qemu/qemu/compare/e4bad9cc5e3a...2992b1c7b455
To unsubscribe from these emails, change your notification settings at
https://github.com/qemu/qemu/settings/notifications
