[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] acbcd0: clock-vmstate: Add missing END_OF_LIS
|
From: |
Peter Maydell |
|
Subject: |
[Qemu-commits] [qemu/qemu] acbcd0: clock-vmstate: Add missing END_OF_LIST |
|
Date: |
Thu, 03 Mar 2022 06:46:56 -0800 |
Branch: refs/heads/master
Home: https://github.com/qemu/qemu
Commit: acbcd06e5d2c181afd87b413e92a92f4594ec084
https://github.com/qemu/qemu/commit/acbcd06e5d2c181afd87b413e92a92f4594ec084
Author: Dr. David Alan Gilbert <dgilbert@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M hw/core/clock-vmstate.c
Log Message:
-----------
clock-vmstate: Add missing END_OF_LIST
Add the missing VMSTATE_END_OF_LIST to vmstate_muldiv
Fixes: 99abcbc7600 ("clock: Provide builtin multiplier/divider")
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Message-Id: <20220111101934.115028-1-dgilbert@redhat.com>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Luc Michel <luc@lmichel.fr>
Cc: qemu-stable@nongnu.org
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: 4ce7a08d3e3a869f89c2af622fa77e967ade7cbf
https://github.com/qemu/qemu/commit/4ce7a08d3e3a869f89c2af622fa77e967ade7cbf
Author: Hanna Reitz <hreitz@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M meson.build
M tools/virtiofsd/passthrough_ll.c
Log Message:
-----------
virtiofsd: Let meson check for statx.stx_mnt_id
In virtiofsd, we assume that the presence of the STATX_MNT_ID macro
implies existence of the statx.stx_mnt_id field. Unfortunately, that is
not necessarily the case: glibc has introduced the macro in its commit
88a2cf6c4bab6e94a65e9c0db8813709372e9180, but the statx.stx_mnt_id field
is still missing from its own headers.
Let meson.build actually chek for both STATX_MNT_ID and
statx.stx_mnt_id, and set CONFIG_STATX_MNT_ID if both are present.
Then, use this config macro in virtiofsd.
Closes: https://gitlab.com/qemu-project/qemu/-/issues/882
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
Message-Id: <20220223092340.9043-1-hreitz@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: 26fcd766179e8a27c4c6c702201bdb0fe60eb091
https://github.com/qemu/qemu/commit/26fcd766179e8a27c4c6c702201bdb0fe60eb091
Author: Stefan Reiter <s.reiter@proxmox.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M monitor/hmp.c
M monitor/monitor-internal.h
Log Message:
-----------
monitor/hmp: add support for flag argument with value
Adds support for the "-xs" parameter type, where "-x" denotes a flag
name and the "s" suffix indicates that this flag is supposed to take
an arbitrary string parameter.
These parameters are always optional, the entry in the qdict will be
omitted if the flag is not given.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
[FE: fixed typo pointed out by Eric Blake
use s instead of V to indicate string parameter]
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
Message-Id: <20220225084949.35746-2-f.ebner@proxmox.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: 7277db9103bc82a79cdd5db633560d2638fbfc33
https://github.com/qemu/qemu/commit/7277db9103bc82a79cdd5db633560d2638fbfc33
Author: Stefan Reiter <s.reiter@proxmox.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M monitor/hmp-cmds.c
M monitor/qmp-cmds.c
M qapi/ui.json
Log Message:
-----------
qapi/monitor: refactor set/expire_password with enums
'protocol' and 'connected' are better suited as enums than as strings,
make use of that. No functional change intended.
Suggested-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
[FE: update "Since: " from 6.2 to 7.0
put 'keep' first in enum to ease use as a default]
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
Message-Id: <20220225084949.35746-3-f.ebner@proxmox.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: 675fd3c96b93abd50a3856089d832c0666dfab52
https://github.com/qemu/qemu/commit/675fd3c96b93abd50a3856089d832c0666dfab52
Author: Stefan Reiter <s.reiter@proxmox.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M hmp-commands.hx
M monitor/hmp-cmds.c
M monitor/qmp-cmds.c
M qapi/ui.json
Log Message:
-----------
qapi/monitor: allow VNC display id in set/expire_password
It is possible to specify more than one VNC server on the command line,
either with an explicit ID or the auto-generated ones à la "default",
"vnc2", "vnc3", ...
It is not possible to change the password on one of these extra VNC
displays though. Fix this by adding a "display" parameter to the
"set_password" and "expire_password" QMP and HMP commands.
For HMP, the display is specified using the "-d" value flag.
For QMP, the schema is updated to explicitly express the supported
variants of the commands with protocol-discriminated unions.
Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
[FE: update "Since: " from 6.2 to 7.0
make @connected a common member of @SetPasswordOptions]
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
Message-Id: <20220225084949.35746-4-f.ebner@proxmox.com>
Acked-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: f736e414ee16d7a515e755bf7f4a022b5851844e
https://github.com/qemu/qemu/commit/f736e414ee16d7a515e755bf7f4a022b5851844e
Author: Jack Wang <jinpu.wang@ionos.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M migration/rdma.c
Log Message:
-----------
migration/rdma: set the REUSEADDR option for destination
We hit following error during testing RDMA transport:
in case of migration error, mgmt daemon pick one migration port,
incoming rdma:[::]:8089: RDMA ERROR: Error: could not rdma_bind_addr
Then try another -incoming rdma:[::]:8103, sometime it worked,
sometimes need another try with other ports number.
Set the REUSEADDR option for destination, This allow address could
be reused to avoid rdma_bind_addr error out.
Signed-off-by: Jack Wang <jinpu.wang@ionos.com>
Message-Id: <20220208085640.19702-1-jinpu.wang@ionos.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Pankaj Gupta <pankaj.gupta@ionos.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
dgilbert: Fixed up some tabs
Commit: a7060ba3ccc0ec6b8674988b46fc131d2f299458
https://github.com/qemu/qemu/commit/a7060ba3ccc0ec6b8674988b46fc131d2f299458
Author: Peter Xu <peterx@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M migration/savevm.c
M migration/trace-events
Log Message:
-----------
migration: Dump sub-cmd name in loadvm_process_command tp
It'll be easier to read the name rather than index of sub-cmd when debugging.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20220301083925.33483-2-peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: c84f976e913187eecdd9db5e45cae2ea6dd1a82b
https://github.com/qemu/qemu/commit/c84f976e913187eecdd9db5e45cae2ea6dd1a82b
Author: Peter Xu <peterx@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M migration/savevm.c
M migration/trace-events
Log Message:
-----------
migration: Finer grained tracepoints for POSTCOPY_LISTEN
The enablement of postcopy listening has a few steps, add a few tracepoints to
be there ready for some basic measurements for them.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20220301083925.33483-3-peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: b9a040b93536b6b89a569b577ff22317c0287879
https://github.com/qemu/qemu/commit/b9a040b93536b6b89a569b577ff22317c0287879
Author: Peter Xu <peterx@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M migration/savevm.c
M migration/trace-events
Log Message:
-----------
migration: Tracepoint change in postcopy-run bottom half
Remove the old two tracepoints and they're even near each other:
trace_loadvm_postcopy_handle_run_cpu_sync()
trace_loadvm_postcopy_handle_run_vmstart()
Add trace_loadvm_postcopy_handle_run_bh() with a finer granule trace.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20220301083925.33483-4-peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: 77dadc3f83745cbdc56500efd4384950415a2158
https://github.com/qemu/qemu/commit/77dadc3f83745cbdc56500efd4384950415a2158
Author: Peter Xu <peterx@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M migration/migration.h
M migration/postcopy-ram.c
M migration/ram.c
M migration/savevm.c
Log Message:
-----------
migration: Introduce postcopy channels on dest node
Postcopy handles huge pages in a special way that currently we can only have
one "channel" to transfer the page.
It's because when we install pages using UFFDIO_COPY, we need to have the whole
huge page ready, it also means we need to have a temp huge page when trying to
receive the whole content of the page.
Currently all maintainance around this tmp page is global: firstly we'll
allocate a temp huge page, then we maintain its status mostly within
ram_load_postcopy().
To enable multiple channels for postcopy, the first thing we need to do is to
prepare N temp huge pages as caching, one for each channel.
Meanwhile we need to maintain the tmp huge page status per-channel too.
To give some example, some local variables maintained in ram_load_postcopy()
are listed; they are responsible for maintaining temp huge page status:
- all_zero: this keeps whether this huge page contains all zeros
- target_pages: this counts how many target pages have been copied
- host_page: this keeps the host ptr for the page to install
Move all these fields to be together with the temp huge pages to form a new
structure called PostcopyTmpPage. Then for each (future) postcopy channel, we
need one structure to keep the state around.
For vanilla postcopy, obviously there's only one channel. It contains both
precopy and postcopy pages.
This patch teaches the dest migration node to start realize the possible number
of postcopy channels by introducing the "postcopy_channels" variable. Its
value is calculated when setup postcopy on dest node (during POSTCOPY_LISTEN
phase).
Vanilla postcopy will have channels=1, but when postcopy-preempt capability is
enabled (in the future), we will boost it to 2 because even during partial
sending of a precopy huge page we still want to preempt it and start sending
the postcopy requested page right away (so we start to keep two temp huge
pages; more if we want to enable multifd). In this patch there's a TODO marked
for that; so far the channels is always set to 1.
We need to send one "host huge page" on one channel only and we cannot split
them, because otherwise the data upon the same huge page can locate on more
than one channel so we need more complicated logic to manage. One temp host
huge page for each channel will be enough for us for now.
Postcopy will still always use the index=0 huge page even after this patch.
However it prepares for the latter patches where it can start to use multiple
channels (which needs src intervention, because only src knows which channel we
should use).
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20220301083925.33483-5-peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
dgilbert: Fixed up long line
Commit: cfc7dc8abfdb71e39e48bdb297b5e86fe2121d97
https://github.com/qemu/qemu/commit/cfc7dc8abfdb71e39e48bdb297b5e86fe2121d97
Author: Peter Xu <peterx@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M migration/ram.c
Log Message:
-----------
migration: Dump ramblock and offset too when non-same-page detected
In ram_load_postcopy() we'll try to detect non-same-page case and dump error.
This error is very helpful for debugging. Adding ramblock & offset into the
error log too.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20220301083925.33483-6-peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
dgilbert: Fix up long line
Commit: 095c12a4a2df4bb45e8d1b1f74dc7ea80fef9ca4
https://github.com/qemu/qemu/commit/095c12a4a2df4bb45e8d1b1f74dc7ea80fef9ca4
Author: Peter Xu <peterx@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M migration/migration.h
M migration/postcopy-ram.c
M migration/postcopy-ram.h
M migration/savevm.c
Log Message:
-----------
migration: Add postcopy_thread_create()
Postcopy create threads. A common manner is we init a sem and use it to sync
with the thread. Namely, we have fault_thread_sem and listen_thread_sem and
they're only used for this.
Make it a shared infrastructure so it's easier to create yet another thread.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20220301083925.33483-7-peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: 755e8d7cb6ce2ba62d282ffbb367de391fe0cc3d
https://github.com/qemu/qemu/commit/755e8d7cb6ce2ba62d282ffbb367de391fe0cc3d
Author: Peter Xu <peterx@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M migration/migration.h
M migration/ram.c
Log Message:
-----------
migration: Move static var in ram_block_from_stream() into global
Static variable is very unfriendly to threading of ram_block_from_stream().
Move it into MigrationIncomingState.
Make the incoming state pointer to be passed over to ram_block_from_stream() on
both caller sites.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20220301083925.33483-8-peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: d5c8f2afe866b84ce9372d5c52c130d1e457fc95
https://github.com/qemu/qemu/commit/d5c8f2afe866b84ce9372d5c52c130d1e457fc95
Author: Peter Xu <peterx@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M migration/migration.c
M migration/postcopy-ram.c
Log Message:
-----------
migration: Enlarge postcopy recovery to capture !-EIO too
We used to have quite a few places making sure -EIO happened and that's the
only way to trigger postcopy recovery. That's based on the assumption that
we'll only return -EIO for channel issues.
It'll work in 99.99% cases but logically that won't cover some corner cases.
One example is e.g. ram_block_from_stream() could fail with an interrupted
network, then -EINVAL will be returned instead of -EIO.
I remembered Dave Gilbert pointed that out before, but somehow this is
overlooked. Neither did I encounter anything outside the -EIO error.
However we'd better touch that up before it triggers a rare VM data loss during
live migrating.
To cover as much those cases as possible, remove the -EIO restriction on
triggering the postcopy recovery, because even if it's not a channel failure,
we can't do anything better than halting QEMU anyway - the corpse of the
process may even be used by a good hand to dig out useful memory regions, or
the admin could simply kill the process later on.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20220301083925.33483-11-peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: 27dd21b461569f3b85a9db409f9117ae9d976548
https://github.com/qemu/qemu/commit/27dd21b461569f3b85a9db409f9117ae9d976548
Author: Peter Xu <peterx@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M migration/postcopy-ram.c
Log Message:
-----------
migration: postcopy_pause_fault_thread() never fails
Per the title, remove the return code and simplify the callers as the errors
will never be triggered. No functional change intended.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20220301083925.33483-12-peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: e031149c78489413038e934eec9f54ac699cf322
https://github.com/qemu/qemu/commit/e031149c78489413038e934eec9f54ac699cf322
Author: Peter Xu <peterx@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M migration/migration.c
M migration/migration.h
Log Message:
-----------
migration: Add migration_incoming_transport_cleanup()
Add a helper to cleanup the transport listener.
When do it, we should also null-ify the cleanup hook and the data, then it's
even safe to call it multiple times.
Move the socket_address_list cleanup altogether, because that's a mirror of the
listener channels and only for the purpose of query-migrate. Hence when
someone wants to cleanup the listener transport, it should also want to cleanup
the socket list too, always.
No functional change intended.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20220301083925.33483-15-peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: 3ff57401870481825c50d17afd393f64fa64a0b0
https://github.com/qemu/qemu/commit/3ff57401870481825c50d17afd393f64fa64a0b0
Author: Peter Xu <peterx@redhat.com>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M tests/qtest/migration-test.c
Log Message:
-----------
tests: Pass in MigrateStart** into test_migrate_start()
test_migrate_start() will release the MigrateStart structure that passed
in, however that's not super clear to the caller because after the call
returned the pointer can still be referenced by the callers. It can easily
be a source of use-after-free.
Let's pass in a double pointer of that, then we can safely clear the
pointer for the caller after the struct is released.
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20220301083925.33483-26-peterx@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
dgilbert: Fixup apply since I didn't take 24/25
Commit: 18621987027b1800f315fb9e29967e7b5398ef6f
https://github.com/qemu/qemu/commit/18621987027b1800f315fb9e29967e7b5398ef6f
Author: Peter Maydell <peter.maydell@linaro.org>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M docs/devel/migration.rst
M hw/ssi/xlnx-versal-ospi.c
M include/migration/vmstate.h
M migration/vmstate.c
Log Message:
-----------
migration: Remove load_state_old and minimum_version_id_old
There are no longer any VMStateDescription structs in the tree which
use the load_state_old support for custom handling of incoming
migration from very old QEMU. Remove the mechanism entirely.
This includes removing one stray useless setting of
minimum_version_id_old in a VMStateDescription with no load_state_old
function, which crept in after the global weeding-out of them in
commit 17e313406126.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Message-Id: <20220215175705.3846411-1-peter.maydell@linaro.org>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Francisco Iglesias <francisco.iglesias@xilinx.com>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Commit: 36eae3a732a1f2aa81391e871ac0e9bb3233e7d7
https://github.com/qemu/qemu/commit/36eae3a732a1f2aa81391e871ac0e9bb3233e7d7
Author: Peter Maydell <peter.maydell@linaro.org>
Date: 2022-03-02 (Wed, 02 Mar 2022)
Changed paths:
M docs/devel/migration.rst
M hmp-commands.hx
M hw/core/clock-vmstate.c
M hw/ssi/xlnx-versal-ospi.c
M include/migration/vmstate.h
M meson.build
M migration/migration.c
M migration/migration.h
M migration/postcopy-ram.c
M migration/postcopy-ram.h
M migration/ram.c
M migration/rdma.c
M migration/savevm.c
M migration/trace-events
M migration/vmstate.c
M monitor/hmp-cmds.c
M monitor/hmp.c
M monitor/monitor-internal.h
M monitor/qmp-cmds.c
M qapi/ui.json
M tests/qtest/migration-test.c
M tools/virtiofsd/passthrough_ll.c
Log Message:
-----------
Merge remote-tracking branch
'remotes/dgilbert-gitlab/tags/pull-migration-20220302b' into staging
Migration/HMP/Virtio pull 2022-03-02
A bit of a mix this time:
* Minor fixes from myself, Hanna, and Jack
* VNC password rework by Stefan and Fabian
* Postcopy changes from Peter X that are
the start of a larger series to come
* Removing the prehistoic load_state_old
code from Peter M
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
# gpg: Signature made Wed 02 Mar 2022 18:25:12 GMT
# gpg: using RSA key 45F5C71B4A0CB7FB977A9FA90516331EBC5BFDE7
# gpg: Good signature from "Dr. David Alan Gilbert (RH2) <dgilbert@redhat.com>"
[full]
# Primary key fingerprint: 45F5 C71B 4A0C B7FB 977A 9FA9 0516 331E BC5B FDE7
* remotes/dgilbert-gitlab/tags/pull-migration-20220302b:
migration: Remove load_state_old and minimum_version_id_old
tests: Pass in MigrateStart** into test_migrate_start()
migration: Add migration_incoming_transport_cleanup()
migration: postcopy_pause_fault_thread() never fails
migration: Enlarge postcopy recovery to capture !-EIO too
migration: Move static var in ram_block_from_stream() into global
migration: Add postcopy_thread_create()
migration: Dump ramblock and offset too when non-same-page detected
migration: Introduce postcopy channels on dest node
migration: Tracepoint change in postcopy-run bottom half
migration: Finer grained tracepoints for POSTCOPY_LISTEN
migration: Dump sub-cmd name in loadvm_process_command tp
migration/rdma: set the REUSEADDR option for destination
qapi/monitor: allow VNC display id in set/expire_password
qapi/monitor: refactor set/expire_password with enums
monitor/hmp: add support for flag argument with value
virtiofsd: Let meson check for statx.stx_mnt_id
clock-vmstate: Add missing END_OF_LIST
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Compare: https://github.com/qemu/qemu/compare/64ada298b98a...36eae3a732a1