Branch: refs/heads/master
Home: https://github.com/qemu/qemu
Commit: 2e6a9f03ba1e8145cf71eced2b97611cfa754898
https://github.com/qemu/qemu/commit/2e6a9f03ba1e8145cf71eced2b97611cfa754898
Author: Gautam Gala <gg...@linux.ibm.com>
Date: 2025-04-30 (Wed, 30 Apr 2025)
Changed paths:
M target/s390x/kvm/pv.c
Log Message:
-----------
target/s390x: Introduce constant when checking if PV header couldn't be
decrypted
Introduce a named constant when checking the Set Secure Configuration parameters
UV call return code for the case where no valid host key was found and therefore
the PV header couldn't be decrypted (0x108).
Reviewed-by: Steffen Eiden <sei...@linux.ibm.com>
Reviewed-by: Janosch Frank <fran...@linux.ibm.com>
Signed-off-by: Gautam Gala <gg...@linux.ibm.com>
Message-ID: <20250423080915.1048123-2-gg...@linux.ibm.com>
Signed-off-by: Thomas Huth <th...@redhat.com>
Commit: e27cbd17dd5d46f92e2e9610e4ed12b525c548be
https://github.com/qemu/qemu/commit/e27cbd17dd5d46f92e2e9610e4ed12b525c548be
Author: Gautam Gala <gg...@linux.ibm.com>
Date: 2025-04-30 (Wed, 30 Apr 2025)
Changed paths:
M target/s390x/kvm/pv.c
Log Message:
-----------
target/s390x: Introduce function when exiting PV
Replace an existing macro (s390_pv_cmd_exit) that looks like
a function with an actual function. The function will be used
when exiting PV instead of the macro.
Reviewed-by: Steffen Eiden <sei...@linux.ibm.com>
Reviewed-by: Janosch Frank <fran...@linux.ibm.com>
Signed-off-by: Gautam Gala <gg...@linux.ibm.com>
Reviewed-by: Thomas Huth <th...@redhat.com>
Message-ID: <20250423080915.1048123-3-gg...@linux.ibm.com>
Signed-off-by: Thomas Huth <th...@redhat.com>
Commit: 55a494e53e1f0c73ba5cfb1b072fed9035b7961b
https://github.com/qemu/qemu/commit/55a494e53e1f0c73ba5cfb1b072fed9035b7961b
Author: Gautam Gala <gg...@linux.ibm.com>
Date: 2025-04-30 (Wed, 30 Apr 2025)
Changed paths:
M hw/s390x/ipl.c
M hw/s390x/ipl.h
M hw/s390x/s390-virtio-ccw.c
M target/s390x/kvm/pv.c
M target/s390x/kvm/pv.h
Log Message:
-----------
target/s390x: Return UVC cmd code, RC and RRC value when DIAG 308 Subcode 10
fails to enter secure mode
Extend DIAG308 subcode 10 to return the UVC RC, RRC and command code
in bit positions 32-47, 16-31, and 0-15 of register R1 + 1 if the
function does not complete successfully (in addition to the
previously returned diag response code in bit position 47-63).
Reviewed-by: Janosch Frank <fran...@linux.ibm.com>
Signed-off-by: Gautam Gala <gg...@linux.ibm.com>
Reviewed-by: Steffen Eiden <sei...@linux.ibm.com>
Message-ID: <20250423080915.1048123-4-gg...@linux.ibm.com>
Signed-off-by: Thomas Huth <th...@redhat.com>
Commit: 6b1c744ec0d66d6d568f9a156282153fc11a21cf
https://github.com/qemu/qemu/commit/6b1c744ec0d66d6d568f9a156282153fc11a21cf
Author: Daniel P. Berrangé <berra...@redhat.com>
Date: 2025-04-30 (Wed, 30 Apr 2025)
Changed paths:
M meson.build
M meson_options.txt
M scripts/meson-buildoptions.sh
Log Message:
-----------
meson/configure: add 'valgrind' option & --{en, dis}able-valgrind flag
Currently valgrind debugging support for coroutine stacks is enabled
unconditionally when valgrind/valgrind.h is found. There is no way
to disable valgrind support if valgrind.h is present in the build env.
This is bad for distros, as an dependency far down the chain may cause
valgrind.h to become installed, inadvertently enabling QEMU's valgrind
debugging support. It also means if a distro wants valgrind support
there is no way to mandate this.
The solution is to add a 'valgrind' build feature to meson and thus
configure script.
Signed-off-by: Daniel P. Berrangé <berra...@redhat.com>
Reviewed-by: Thomas Huth <th...@redhat.com>
Message-ID: <20250425121713.1913424-1-berra...@redhat.com>
Signed-off-by: Thomas Huth <th...@redhat.com>
Commit: d64db833d6e3cbe9ea5f36342480f920f3675cea
https://github.com/qemu/qemu/commit/d64db833d6e3cbe9ea5f36342480f920f3675cea
Author: Thomas Huth <th...@redhat.com>
Date: 2025-04-30 (Wed, 30 Apr 2025)
Changed paths:
M configure
M docs/about/build-platforms.rst
M python/Makefile
M python/setup.cfg
M python/tests/minreqs.txt
M scripts/qapi/mypy.ini
M tests/docker/dockerfiles/python.docker
Log Message:
-----------
Drop support for Python 3.8
Python 3.8 went "end of life" in October 2024 and Fedora 42 dropped
this version already, so the "python" CI job is currently failing.
Thus it's time to drop support for this Python version in QEMU, too.
While we're at it, also look for "python3.13" in the configure script.
Message-ID: <20250425120710.879518-1-th...@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <phi...@linaro.org>
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>
Signed-off-by: Thomas Huth <th...@redhat.com>
Commit: bcfee4938f8d4e8bf5f49981d3c8a78cf267cb4e
https://github.com/qemu/qemu/commit/bcfee4938f8d4e8bf5f49981d3c8a78cf267cb4e
Author: Thomas Huth <th...@redhat.com>
Date: 2025-04-30 (Wed, 30 Apr 2025)
Changed paths:
M tests/functional/test_ppc64_pseries.py
Log Message:
-----------
tests/functional/test_ppc64_pseries: Skip test_ppc64_linux_smt_boot if
necessary
The test_ppc64_linux_smt_boot function lacks the set_machine('pseries'),
so this test is currently failing in case the 'pseries' machine has not
been compiled into the binary. Add the check now to fix it.
Message-ID: <20250424085426.663377-1-th...@redhat.com>
Reviewed-by: Harsh Prateek Bora <hars...@linux.ibm.com>
Signed-off-by: Thomas Huth <th...@redhat.com>
Commit: c6d82df70e0ad3477ea97e9dc99b97c2fbfa0c1a
https://github.com/qemu/qemu/commit/c6d82df70e0ad3477ea97e9dc99b97c2fbfa0c1a
Author: Thomas Huth <th...@redhat.com>
Date: 2025-04-30 (Wed, 30 Apr 2025)
Changed paths:
M meson.build
Log Message:
-----------
meson.build: Put the D-Bus summary into the UI section
We've got a dedicated section for UI options nowadays, so the
D-Bus display should get reported here, too.
Message-ID: <20250325055125.253669-1-th...@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lur...@redhat.com>
Reviewed-by: Alex Bennée <alex.ben...@linaro.org>
Signed-off-by: Thomas Huth <th...@redhat.com>
Commit: 35817600089256a234eb23613564d94b80e93ac4
https://github.com/qemu/qemu/commit/35817600089256a234eb23613564d94b80e93ac4
Author: Philippe Mathieu-Daudé <phi...@linaro.org>
Date: 2025-04-30 (Wed, 30 Apr 2025)
Changed paths:
M hw/rtc/mc146818rtc.c
Log Message:
-----------
hw/rtc/mc146818rtc: Drop pre-v3 migration stream support
mc146818rtc's migration stream is at version 3 since commit
56038ef6234 ("RTC: Update the RTC clock only when reading it")
from 12 years ago, released in QEMU v1.3.0!
No versioned machines are that old, we can safely remove
support for older streams and the qdev_set_legacy_instance_id()
call.
Signed-off-by: Philippe Mathieu-Daudé <phi...@linaro.org>
Reviewed-by: Fabiano Rosas <faro...@suse.de>
Message-ID: <20250115210048.25396-1-phi...@linaro.org>
Signed-off-by: Thomas Huth <th...@redhat.com>
Commit: dce324fa06b358ccb01bf35611b6fc53b1f56b96
https://github.com/qemu/qemu/commit/dce324fa06b358ccb01bf35611b6fc53b1f56b96
Author: Pierrick Bouvier <pierrick.bouv...@linaro.org>
Date: 2025-04-30 (Wed, 30 Apr 2025)
Changed paths:
M docs/devel/build-environment.rst
Log Message:
-----------
docs/devel/build-environment: enhance MSYS2 instructions
Add missing prerequisite packages, and use more explicit makepkg
command.
Signed-off-by: Pierrick Bouvier <pierrick.bouv...@linaro.org>
Message-ID: <20250430181047.2043492-1-pierrick.bouv...@linaro.org>
Signed-off-by: Thomas Huth <th...@redhat.com>
Commit: e578dcc7e1590b20a84036afe5bdfa8d23a6048e
https://github.com/qemu/qemu/commit/e578dcc7e1590b20a84036afe5bdfa8d23a6048e
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M MAINTAINERS
M pc-bios/README
A pc-bios/ast27x0_bootrom.bin
M pc-bios/meson.build
Log Message:
-----------
pc-bios: Add AST27x0 vBootrom
The boot ROM is a minimal implementation designed to load an AST27x0 boot image.
Its source code is available at:
https://github.com/google/vbootrom
Commit id: d6e3386709b3e49322a94ffadc2aaab9944ab77b
Build Information:
```
Build Date : Apr 29 2025 01:23:18
FW Version : git-d6e3386
```
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Nabih Estefan <nabiheste...@google.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Tested-by: Nabih Estefan <nabiheste...@google.com>
Link:
https://lore.kernel.org/qemu-devel/20250429062822.1184920-2-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 57be554c2984de3261d1e5d446d797d8e5b2c997
https://github.com/qemu/qemu/commit/57be554c2984de3261d1e5d446d797d8e5b2c997
Author: Li Zhijian <lizhij...@fujitsu.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M migration/migration.c
M migration/options.c
M migration/options.h
Log Message:
-----------
migration: check RDMA and capabilities are compatible on both sides
Depending on the order of starting RDMA and setting capability,
they can be categorized into the following scenarios:
Source:
S1: [set capabilities] -> [Start RDMA outgoing]
Destination:
D1: [set capabilities] -> [Start RDMA incoming]
D2: [Start RDMA incoming] -> [set capabilities]
Previously, compatibility between RDMA and capabilities was verified only
in scenario D1, potentially causing migration failures in other situations.
For scenarios S1 and D1, we can seamlessly incorporate
migration_transport_compatible() to address compatibility between
channels and capabilities vs transport.
For scenario D2, ensure compatibility within migrate_caps_check().
Reviewed-by: Peter Xu <pet...@redhat.com>
Signed-off-by: Li Zhijian <lizhij...@fujitsu.com>
Message-ID: <20250305062825.772629-3-lizhij...@fujitsu.com>
Signed-off-by: Fabiano Rosas <faro...@suse.de>
Commit: 103fa641953bfadfe88fbe5f16c0afc9f1e508db
https://github.com/qemu/qemu/commit/103fa641953bfadfe88fbe5f16c0afc9f1e508db
Author: Li Zhijian <lizhij...@fujitsu.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M migration/options.c
Log Message:
-----------
migration: disable RDMA + postcopy-ram
It's believed that RDMA + postcopy-ram has been broken for a while.
Rather than spending time re-enabling it, let's simply disable it as a
trade-off.
Reviewed-by: Peter Xu <pet...@redhat.com>
Signed-off-by: Li Zhijian <lizhij...@fujitsu.com>
Message-ID: <20250305062825.772629-4-lizhij...@fujitsu.com>
Signed-off-by: Fabiano Rosas <faro...@suse.de>
Commit: 4ecd6beaf9ff4ad88a33eab78789335a6e929564
https://github.com/qemu/qemu/commit/4ecd6beaf9ff4ad88a33eab78789335a6e929564
Author: Li Zhijian <lizhij...@fujitsu.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M migration/rdma.c
Log Message:
-----------
migration/rdma: Remove redundant migration_in_postcopy checks
Since we have disabled RDMA + postcopy, it's safe to remove
the migration_in_postcopy() that follows the migrate_rdma().
Reviewed-by: Peter Xu <pet...@redhat.com>
Signed-off-by: Li Zhijian <lizhij...@fujitsu.com>
Message-ID: <20250305062825.772629-5-lizhij...@fujitsu.com>
Signed-off-by: Fabiano Rosas <faro...@suse.de>
Commit: 5e7ca4a7d79da6c9e584886879002f24917c8d27
https://github.com/qemu/qemu/commit/5e7ca4a7d79da6c9e584886879002f24917c8d27
Author: Li Zhijian <lizhij...@fujitsu.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M migration/ram.c
M migration/rdma.c
M migration/rdma.h
Log Message:
-----------
migration: Unfold control_save_page()
control_save_page() is for RDMA only, unfold it to make the code more
clear.
In addition:
- Similar to other branches style in ram_save_target_page(), involve RDMA
only if the condition 'migrate_rdma()' is true.
- Further simplify the code by removing the RAM_SAVE_CONTROL_NOT_SUPP.
Reviewed-by: Peter Xu <pet...@redhat.com>
Signed-off-by: Li Zhijian <lizhij...@fujitsu.com>
Message-ID: <20250305062825.772629-6-lizhij...@fujitsu.com>
Signed-off-by: Fabiano Rosas <faro...@suse.de>
Commit: 7d9849c3c41463ab9ba40348a8606927dc0fb85d
https://github.com/qemu/qemu/commit/7d9849c3c41463ab9ba40348a8606927dc0fb85d
Author: Li Zhijian <lizhij...@fujitsu.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M MAINTAINERS
A scripts/rdma-migration-helper.sh
M tests/qtest/migration/precopy-tests.c
Log Message:
-----------
migration: Add qtest for migration over RDMA
This qtest requires there is a RDMA(RoCE) link in the host.
In order to make the test work smoothly, introduce a
scripts/rdma-migration-helper.sh to detect existing RoCE link before
running the test.
Test will be skipped if there is no available RoCE link.
# Start of rdma tests
# Running /x86_64/migration/precopy/rdma/plain
ok 1 /x86_64/migration/precopy/rdma/plain # SKIP No rdma link available
# To enable the test:
# Run 'scripts/rdma-migration-helper.sh setup' with root to setup a new
rdma/rxe link and rerun the test
# Optional: run 'scripts/rdma-migration-helper.sh clean' to revert the 'setup'
# End of rdma tests
Cc: Philippe Mathieu-Daudé <phi...@linaro.org>
Cc: Stefan Hajnoczi <stefa...@gmail.com>
Reviewed-by: Peter Xu <pet...@redhat.com>
Signed-off-by: Li Zhijian <lizhij...@fujitsu.com>
Message-ID: <20250311024221.363421-1-lizhij...@fujitsu.com>
[add 'head -1' to script, reformat test message]
Signed-off-by: Fabiano Rosas <faro...@suse.de>
Commit: b407c9e74753ca0dbc00832bf5fcec44efd05308
https://github.com/qemu/qemu/commit/b407c9e74753ca0dbc00832bf5fcec44efd05308
Author: Markus Armbruster <arm...@redhat.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M migration/options.c
Log Message:
-----------
migration: Fix latent bug in migrate_params_test_apply()
migrate_params_test_apply() neglects to apply tls_authz. Currently
harmless, because migrate_params_check() doesn't care. Fix it anyway.
Signed-off-by: Markus Armbruster <arm...@redhat.com>
Reviewed-by: Fabiano Rosas <faro...@suse.de>
Message-ID: <20250407072833.2118928-1-arm...@redhat.com>
Signed-off-by: Fabiano Rosas <faro...@suse.de>
Commit: 56e3c89f44ecebc946fbe4ffed325d1a79b26e38
https://github.com/qemu/qemu/commit/56e3c89f44ecebc946fbe4ffed325d1a79b26e38
Author: Prasad Pandit <p...@fedoraproject.org>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M migration/multifd.c
M migration/multifd.h
Log Message:
-----------
migration/multifd: move macros to multifd header
Move MULTIFD_ macros to the header file so that
they are accessible from other source files.
Reviewed-by: Fabiano Rosas <faro...@suse.de>
Signed-off-by: Prasad Pandit <p...@fedoraproject.org>
Reviewed-by: Peter Xu <pet...@redhat.com>
Message-ID: <20250411114534.3370816-2-ppan...@redhat.com>
Signed-off-by: Fabiano Rosas <faro...@suse.de>
Commit: 00f3fcef1981eb23f98b956d9cda2df528bfef40
https://github.com/qemu/qemu/commit/00f3fcef1981eb23f98b956d9cda2df528bfef40
Author: Prasad Pandit <p...@fedoraproject.org>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M migration/migration.c
Log Message:
-----------
migration: refactor channel discovery mechanism
The various logical migration channels don't have a
standardized way of advertising themselves and their
connections may be seen out of order by the migration
destination. When a new connection arrives, the incoming
migration currently make use of heuristics to determine
which channel it belongs to.
The next few patches will need to change how the multifd
and postcopy capabilities interact and that affects the
channel discovery heuristic.
Refactor the channel discovery heuristic to make it less
opaque and simplify the subsequent patches.
Signed-off-by: Prasad Pandit <p...@fedoraproject.org>
Reviewed-by: Fabiano Rosas <faro...@suse.de>
Message-ID: <20250411114534.3370816-3-ppan...@redhat.com>
Signed-off-by: Fabiano Rosas <faro...@suse.de>
Commit: 1d481116015428c02f7e3635f9bc0b88b0978fdc
https://github.com/qemu/qemu/commit/1d481116015428c02f7e3635f9bc0b88b0978fdc
Author: Peter Xu <pet...@redhat.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M include/migration/register.h
M migration/migration.c
M migration/savevm.c
M migration/savevm.h
Log Message:
-----------
migration: Add save_postcopy_prepare() savevm handler
Add a savevm handler for a module to opt-in sending extra sections right
before postcopy starts, and before VM is stopped.
RAM will start to use this new savevm handler in the next patch to do flush
and sync for multifd pages.
Note that we choose to do it before VM stopped because the current only
potential user is not sensitive to VM status, so doing it before VM is
stopped is preferred to enlarge any postcopy downtime.
It is still a bit unfortunate that we need to introduce such a new savevm
handler just for the only use case, however it's so far the cleanest.
Signed-off-by: Peter Xu <pet...@redhat.com>
Signed-off-by: Prasad Pandit <p...@fedoraproject.org>
Reviewed-by: Fabiano Rosas <faro...@suse.de>
Message-ID: <20250411114534.3370816-4-ppan...@redhat.com>
Signed-off-by: Fabiano Rosas <faro...@suse.de>
Commit: ad8d82ffbb8b8034f58a570911e6e9c6328c9384
https://github.com/qemu/qemu/commit/ad8d82ffbb8b8034f58a570911e6e9c6328c9384
Author: Peter Xu <pet...@redhat.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M migration/ram.c
Log Message:
-----------
migration/ram: Implement save_postcopy_prepare()
Implement save_postcopy_prepare(), preparing for the enablement
of both multifd and postcopy.
Signed-off-by: Peter Xu <pet...@redhat.com>
Signed-off-by: Prasad Pandit <p...@fedoraproject.org>
Reviewed-by: Fabiano Rosas <faro...@suse.de>
Message-ID: <20250411114534.3370816-5-ppan...@redhat.com>
Signed-off-by: Fabiano Rosas <faro...@suse.de>
Commit: 115cec9d663c1a2f5a73df4a5ca02b3a676e8a2a
https://github.com/qemu/qemu/commit/115cec9d663c1a2f5a73df4a5ca02b3a676e8a2a
Author: Prasad Pandit <p...@fedoraproject.org>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M tests/qtest/migration/compression-tests.c
M tests/qtest/migration/cpr-tests.c
M tests/qtest/migration/file-tests.c
M tests/qtest/migration/framework.c
M tests/qtest/migration/framework.h
M tests/qtest/migration/misc-tests.c
M tests/qtest/migration/postcopy-tests.c
M tests/qtest/migration/precopy-tests.c
M tests/qtest/migration/tls-tests.c
Log Message:
-----------
tests/qtest/migration: consolidate set capabilities
Migration capabilities are set in multiple '.start_hook'
functions for various tests. Instead, consolidate setting
capabilities in 'migrate_start_set_capabilities()' function
which is called from the 'migrate_start()' function.
While simplifying the capabilities setting, it helps
to declutter the qtest sources.
Suggested-by: Fabiano Rosas <faro...@suse.de>
Signed-off-by: Prasad Pandit <p...@fedoraproject.org>
Reviewed-by: Fabiano Rosas <faro...@suse.de>
Message-ID: <20250411114534.3370816-7-ppan...@redhat.com>
[fix open brace]
Signed-off-by: Fabiano Rosas <faro...@suse.de>
Commit: 20d82622812d888478d04a2d0d8575d70eb5d749
https://github.com/qemu/qemu/commit/20d82622812d888478d04a2d0d8575d70eb5d749
Author: Peter Xu <pet...@redhat.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M migration/ram.c
Log Message:
-----------
migration/postcopy: Spatial locality page hint for preempt mode
The preempt mode postcopy has been introduced for a while. From latency
POV, it should always win the vanilla postcopy.
However there's one thing missing when preempt mode is enabled right now,
which is the spatial locality hint when there're page requests from the
destination side.
In vanilla postcopy, as long as a page request was unqueued, it will update
the PSS of the precopy background stream, so that after a page request the
background thread will move the pages after whatever was requested. It's
pretty much a natural behavior when there's only one channel anyway, and
one scanner to send the pages.
Preempt mode didn't follow that, because preempt mode has its own channel
and its own PSS (which doesn't linearly scan the guest memory, but
dedicated to resolve page requested from destination). So the page request
process and the background migration process are completely separate.
This patch adds the hint explicitly for preempt mode. With that, whenever
the preempt mode receives a page request on the source, it will service the
remote page fault in the return path, then it'll provide a hint to the
background thread so that we'll start sending the pages right after the
requested ones in the background, assuming the follow up pages have a
higher chance to be accessed later.
NOTE: since the background migration thread and return path thread run
completely concurrently, it doesn't always mean the hint will be applied
every single time. For example, it's possible that the return path thread
receives multiple page requests in a row without the background thread
getting the chance to consume one. In such case, the preempt thread only
provide the hint if the previous hint has been consumed. After all,
there's no point queuing hints when we only have one linear scanner.
This could measureably improve the simple sequential memory access pattern
during postcopy (when preempt is on). For random accesses, I can measure a
slight increase of remote page fault latency from ~500us -> ~600us, that
could be a trade-off to have such hint mechanism, and after all that's
still greatly improved comparing to vanilla postcopy on random (~10ms).
The patch is verified by our QE team in a video streaming test case, to
reduce the pause of the video from ~1min to a few seconds when switching
over to postcopy with preempt mode.
Reported-by: Xiaohui Li <xiao...@redhat.com>
Tested-by: Xiaohui Li <xiao...@redhat.com>
Reviewed-by: Juraj Marcin <jmar...@redhat.com>
Link: https://lore.kernel.org/r/20250424220705.195544-1-pet...@redhat.com
Signed-off-by: Peter Xu <pet...@redhat.com>
Commit: 0bafd6e9cbcdb1d857240f9f8c5df98a472b1b27
https://github.com/qemu/qemu/commit/0bafd6e9cbcdb1d857240f9f8c5df98a472b1b27
Author: Jack Wang <jinpu.w...@ionos.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M migration/rdma.c
Log Message:
-----------
migration/rdma: Remove qemu_rdma_broken_ipv6_kernel
I hit following error which testing migration in pure RoCE env:
"-incoming rdma:[::]:8089: RDMA ERROR: You only have RoCE / iWARP devices in
your
systems and your management software has specified '[::]', but IPv6 over RoCE /
iWARP is not supported in Linux.#012'."
In our setup, we use rdma bind on ipv6 on target host, while connect from source
with ipv4, remove the qemu_rdma_broken_ipv6_kernel, migration just work
fine.
Checking the git history, the function was added since introducing of
rdma migration, which is more than 10 years ago. linux-rdma has
improved support on RoCE/iWARP for ipv6 over past years. There are a few fixes
back in 2016 seems related to the issue, eg:
aeb76df46d11 ("IB/core: Set routable RoCE gid type for ipv4/ipv6 networks")
other fixes back in 2018, eg:
052eac6eeb56 RDMA/cma: Update RoCE multicast routines to use net namespace
8d20a1f0ecd5 RDMA/cma: Fix rdma_cm raw IB path setting for RoCE
9327c7afdce3 RDMA/cma: Provide a function to set RoCE path record L2 parameters
5c181bda77f4 RDMA/cma: Set default GID type as RoCE when resolving RoCE route
3c7f67d1880d IB/cma: Fix default RoCE type setting
be1d325a3358 IB/core: Set RoCEv2 MGID according to spec
63a5f483af0e IB/cma: Set default gid type to RoCEv2
So remove the outdated function and it's usage.
Cc: Peter Xu <pet...@redhat.com>
Cc: Li Zhijian <lizhij...@fujitsu.com>
Cc: Yu Zhang <yu.zh...@ionos.com>
Cc: Fabiano Rosas <faro...@suse.de>
Cc: qemu-de...@nongnu.org
Cc: linux-r...@vger.kernel.org
Cc: mich...@flatgalaxy.com
Signed-off-by: Jack Wang <jinpu.w...@ionos.com>
Tested-by: Li zhijian <lizhij...@fujitsu.com>
Reviewed-by: Michael Galaxy <mrgal...@nvidia.com>
Link: https://lore.kernel.org/r/20250402051306.6509-1-jinpu.w...@ionos.com
[peterx: some cosmetic changes]
Signed-off-by: Peter Xu <pet...@redhat.com>
Commit: e674fedbd1fd9953bc30026670aba6779848280a
https://github.com/qemu/qemu/commit/e674fedbd1fd9953bc30026670aba6779848280a
Author: Thomas Huth <th...@redhat.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M scripts/vmstate-static-checker.py
Log Message:
-----------
scripts/vmstate-static-checker.py: Allow new name for ghes_addr_le field
ghes_addr_le has been renamed to hw_error_le in commit 652f6d86cbb
("acpi/ghes: better name the offset of the hardware error firmware").
Adjust the checker script to allow that changed field name.
Signed-off-by: Thomas Huth <th...@redhat.com>
Reviewed-by: Peter Xu <pet...@redhat.com>
Link: https://lore.kernel.org/r/20250429152141.294380-3-th...@redhat.com
Signed-off-by: Peter Xu <pet...@redhat.com>
Commit: 6f8e6aed81277ec14d5a5dcafdd00dadf7ac465c
https://github.com/qemu/qemu/commit/6f8e6aed81277ec14d5a5dcafdd00dadf7ac465c
Author: Zhao Liu <zhao1....@intel.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M rust/qemu-api/src/vmstate.rs
Log Message:
-----------
rust/vmstate: Add support for field_exists checks
Unfortunately, at present it's not possible to have a const
"with_exist_check" method to append test_fn after vmstate_struct (due
to error on "constant functions cannot evaluate destructors" for `F`).
Before the vmstate builder, the only way to support "test_fn" is to
extend vmstate_struct macro to add the such new optional member (and
fortunately, Rust can still parse the current expansion!).
Abstract the previous callback implementation of vmstate_validate into
a separate macro, and moves it before vmstate_struct for vmstate_struct
to call.
Note that there's no need to add any extra flag for a new test_fn added
in the VMStateField.
Signed-off-by: Zhao Liu <zhao1....@intel.com>
Link: https://lore.kernel.org/r/20250414144943.1112885-2-zhao1....@intel.com
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: 756ea88fff96252dd76cf388fb8678cb97dd2658
https://github.com/qemu/qemu/commit/756ea88fff96252dd76cf388fb8678cb97dd2658
Author: Paolo Bonzini <pbonz...@redhat.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M rust/qemu-api/src/vmstate.rs
Log Message:
-----------
vmstate: support varray for vmstate_clock!
Make vmstate_struct and vmstate_clock more similar; they are basically the
same thing, except for the clock case having a built-in VMStateDescription.
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: fff99a88be34c82270c918b711f8fc3affd504d5
https://github.com/qemu/qemu/commit/fff99a88be34c82270c918b711f8fc3affd504d5
Author: Paolo Bonzini <pbonz...@redhat.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M rust/qemu-api/src/assertions.rs
Log Message:
-----------
rust: assertions: Support index field wrapped in BqlCell
Currently, if the `num` field of a varray is not a numeric type, such as
being placed in a wrapper, the array variant of assert_field_type will
fail the check.
HPET currently wraps num_timers in BqlCell<>. Although BqlCell<> is not
necessary from strictly speaking, it makes sense for vmstate to respect
BqlCell.
The failure of assert_field_type is because it cannot convert BqlCell<T>
into usize for use as the index. Use a constant 0 instead for the index,
by avoiding $(...)? and extracting the common parts of
assert_field_type! into an internal case.
Commit message based on a patch by Zhao Liu <zhao1....@intel.com>.
Link: https://lore.kernel.org/r/20250414144943.1112885-3-zhao1....@intel.com
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: cff1ec67509cacc2ea30d19ba61fa0ab0772e119
https://github.com/qemu/qemu/commit/cff1ec67509cacc2ea30d19ba61fa0ab0772e119
Author: Zhao Liu <zhao1....@intel.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M rust/qemu-api/tests/vmstate_tests.rs
Log Message:
-----------
rust/vmstate_test: Test varray with num field wrapped in BqlCell
Signed-off-by: Zhao Liu <zhao1....@intel.com>
Link: https://lore.kernel.org/r/20250414144943.1112885-4-zhao1....@intel.com
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: 8d9502b4e947a9cfcf1d1940cc70d1579b53ecaf
https://github.com/qemu/qemu/commit/8d9502b4e947a9cfcf1d1940cc70d1579b53ecaf
Author: Zhao Liu <zhao1....@intel.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M rust/qemu-api/src/timer.rs
Log Message:
-----------
rust/timer: Define NANOSECONDS_PER_SECOND binding as u64
NANOSECONDS_PER_SECOND is often used in operations with get_ns(), which
currently returns a u64.
Therefore, define a new NANOSECONDS_PER_SECOND binding is with u64 type
to eliminate unnecessary type conversions (from u32 to u64).
Signed-off-by: Zhao Liu <zhao1....@intel.com>
Link: https://lore.kernel.org/r/20250414144943.1112885-6-zhao1....@intel.com
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: db46654af893abed53dce35ebab86056ac9b3004
https://github.com/qemu/qemu/commit/db46654af893abed53dce35ebab86056ac9b3004
Author: Zhao Liu <zhao1....@intel.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M docs/devel/rust.rst
M rust/hw/timer/hpet/src/hpet.rs
Log Message:
-----------
rust/hpet: Support migration
Based on commit 1433e38cc8 ("hpet: do not overwrite properties on
post_load"), add the basic migration support to Rust HPET.
The current migration implementation introduces multiple unsafe
callbacks. Before the vmstate builder, one possible cleanup approach is
to wrap callbacks in the vmstate binding using a method similar to the
vmstate_exist_fn macro.
However, this approach would also create a lot of repetitive code (since
vmstate has so many callbacks: pre_load, post_load, pre_save, post_save,
needed and dev_unplug_pending). Although it would be cleaner, it would
somewhat deviate from the path of the vmstate builder.
Therefore, firstly focus on completing the functionality of HPET, and
those current unsafe callbacks can at least clearly indicate the needed
functionality of vmstate. The next step is to consider refactoring
vmstate to move towards the vmstate builder direction.
Additionally, update rust.rst about Rust HPET can support migration.
Signed-off-by: Zhao Liu <zhao1....@intel.com>
Link: https://lore.kernel.org/r/20250414144943.1112885-9-zhao1....@intel.com
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: 7c93067fe7e44f89a720fa5f0faf180697d5ac7e
https://github.com/qemu/qemu/commit/7c93067fe7e44f89a720fa5f0faf180697d5ac7e
Author: Magnus Kulke <magnusku...@linux.microsoft.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M target/i386/emulate/x86_decode.c
Log Message:
-----------
target/i386/emulate: remove rflags leftovers
Fixes: c901905ea670 ("target/i386/emulate: remove flags_mask")
In c901905ea670 rflags have been removed from `x86_decode`, but there
were some leftovers.
Signed-off-by: Magnus Kulke <magnusku...@linux.microsoft.com>
Link:
https://lore.kernel.org/r/20250429093319.5010-1-magnusku...@linux.microsoft.com
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: 785f945bd5ace415419d0fe4944fa5fce1bc1865
https://github.com/qemu/qemu/commit/785f945bd5ace415419d0fe4944fa5fce1bc1865
Author: Wei Liu <wei....@kernel.org>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M target/i386/hvf/hvf.c
Log Message:
-----------
target/i386/hvf: fix a compilation error
Include exec/target_page.h to fix the following build error.
x86_64-softmmu.a.p/target_i386_hvf_hvf.c.o -c ../target/i386/hvf/hvf.c
../target/i386/hvf/hvf.c:139:49: error: use of undeclared identifier
'TARGET_PAGE_SIZE'
139 | uint64_t dirty_page_start = gpa & ~(TARGET_PAGE_SIZE - 1u);
| ^
../target/i386/hvf/hvf.c:141:45: error: use of undeclared identifier
'TARGET_PAGE_SIZE'
141 | hv_vm_protect(dirty_page_start, TARGET_PAGE_SIZE,
| ^
Signed-off-by: Wei Liu <wei....@kernel.org>
Link:
https://lore.kernel.org/r/abbws1ikcdfyc...@liuwe-devbox-ubuntu-v2.tail21d00.ts.net
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: e54ef98c8a80d16158bab4341d9a898701270528
https://github.com/qemu/qemu/commit/e54ef98c8a80d16158bab4341d9a898701270528
Author: Paolo Bonzini <pbonz...@redhat.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M target/i386/tcg/emit.c.inc
M target/i386/tcg/translate.c
Log Message:
-----------
target/i386: do not trigger IRQ shadow for LSS
Because LSS need not trigger an IRQ shadow, gen_movl_seg can't just use
the destination register to decide whether to inhibit IRQs. Add an
argument.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: 1e94ddc6854431064c94a7d8f2f2886def285829
https://github.com/qemu/qemu/commit/1e94ddc6854431064c94a7d8f2f2886def285829
Author: Paolo Bonzini <pbonz...@redhat.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M target/i386/tcg/translate.c
Log Message:
-----------
target/i386: do not block singlestep for STI
STI will trigger a singlestep exception even if it has inhibit-IRQ
behavior. Do not suppress single-step for all IRQ-inhibiting
instructions, instead special case MOV SS and POP SS.
Cc: qemu-sta...@nongnu.org
Fixes: f0f0136abba ("target/i386: no single-step exception after MOV or POP
SS", 2024-05-25)
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: 8dc4f981004f17efe2d28f26b180f618f24f46de
https://github.com/qemu/qemu/commit/8dc4f981004f17efe2d28f26b180f618f24f46de
Author: BALATON Zoltan <bala...@eik.bme.hu>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M hw/char/diva-gsp.c
M hw/char/serial-pci-multi.c
M hw/char/serial-pci.c
Log Message:
-----------
hw/char/serial: Remove unused prog_if compat property
This property was added to preserve previous value when this was fixed
in version 2.1 but the last machine using it was already removed when
adding diva-gsp leaving this property unused and unnecessary.
Signed-off-by: BALATON Zoltan <bala...@eik.bme.hu>
Reviewed-by: Philippe Mathieu-Daudé <phi...@linaro.org>
Reviewed-by: Helge Deller <del...@gmx.de>
Link: https://lore.kernel.org/r/20250502095524.de1f355d...@zero.eik.bme.hu
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: ffd5a60e9b67e14f7bac7ea29300ea46a944e508
https://github.com/qemu/qemu/commit/ffd5a60e9b67e14f7bac7ea29300ea46a944e508
Author: Stefan Zabka <g...@zabka.it>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M rust/Cargo.toml
M rust/hw/char/pl011/Cargo.toml
M rust/hw/timer/hpet/Cargo.toml
M rust/qemu-api-macros/Cargo.toml
M rust/qemu-api/Cargo.toml
Log Message:
-----------
rust: centralize config in workspace root
This commit bundles common config option in the workspace
root and applies them through <config>.workspace = true
Signed-off-by: Stefan Zabka <g...@zabka.it>
Link: https://lore.kernel.org/r/20250502212748.124953-1-...@zabka.it
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: 03f50d7ee756eecbd4481c3008b5e01e999729c7
https://github.com/qemu/qemu/commit/03f50d7ee756eecbd4481c3008b5e01e999729c7
Author: Andrey Drobyshev <andrey.drobys...@virtuozzo.com>
Date: 2025-05-02 (Fri, 02 May 2025)
Changed paths:
M monitor/qmp.c
Log Message:
-----------
monitor: don't wake up qmp_dispatcher_co coroutine upon cleanup
Since the commit 3e6bed61 ("monitor: cleanup detection of qmp_dispatcher_co
shutting down"), coroutine pointer qmp_dispatcher_co is set to NULL upon
cleanup. If a QMP command is sent after monitor_cleanup() (e.g. after
shutdown), this may lead to SEGFAULT on aio_co_wake(NULL).
As mentioned in the comment inside monitor_cleanup(), the intention is to
allow incoming requests while shutting down, but simply leave them
without any response. Let's do exactly that, and if qmp_dispatcher_co
coroutine pointer has already been set to NULL, let's simply skip the
aio_co_wake() part.
Signed-off-by: Andrey Drobyshev <andrey.drobys...@virtuozzo.com>
Link:
https://lore.kernel.org/r/20250502214729.928380-2-andrey.drobys...@virtuozzo.com
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
Commit: ba27ba302a264117c8b8427f944ced1bed17c438
https://github.com/qemu/qemu/commit/ba27ba302a264117c8b8427f944ced1bed17c438
Author: Troy Lee <troy_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/arm/aspeed_ast27x0.c
M include/hw/arm/aspeed_soc.h
Log Message:
-----------
hw/arm: ast27x0: Wire up EHCI controllers
AST27x0 has 4 EHCI controllers, where each CPU and I/O die has 2
instances. This patch use existing TYPE_PLATFORM_EHCI. After wiring up
the EHCI controller, the ast2700a1-evb can find up to 4 USB EHCI
interfaces.
ehci-platform 12061000.usb: EHCI Host Controller
ehci-platform 12061000.usb: new USB bus registered, assigned bus number 2
ehci-platform 12063000.usb: EHCI Host Controller
ehci-platform 12063000.usb: new USB bus registered, assigned bus number 3
ehci-platform 12061000.usb: irq 88, io mem 0x12061000
ehci-platform 12063000.usb: irq 90, io mem 0x12063000
ehci-platform 14121000.usb: EHCI Host Controller
ehci-platform 14123000.usb: EHCI Host Controller
ehci-platform 12061000.usb: USB 2.0 started, EHCI 1.00
ehci-platform 14121000.usb: new USB bus registered, assigned bus number 5
ehci-platform 14123000.usb: new USB bus registered, assigned bus number 6
ehci-platform 14121000.usb: irq 91, io mem 0x14121000
ehci-platform 14123000.usb: irq 92, io mem 0x14123000
ehci-platform 12063000.usb: USB 2.0 started, EHCI 1.00
usb usb2: Manufacturer: Linux 6.6.78-dirty-bafd2830c17c-gbafd2830c17c-dirty
ehci_hcd
usb usb3: Manufacturer: Linux 6.6.78-dirty-bafd2830c17c-gbafd2830c17c-dirty
ehci_hcd
ehci-platform 14121000.usb: USB 2.0 started, EHCI 1.00
usb usb5: Manufacturer: Linux 6.6.78-dirty-bafd2830c17c-gbafd2830c17c-dirty
ehci_hcd
ehci-platform 14123000.usb: USB 2.0 started, EHCI 1.00
usb usb6: Manufacturer: Linux 6.6.78-dirty-bafd2830c17c-gbafd2830c17c-dirty
ehci_hcd
Note that, AST27x0A0 only has 2 EHCI controllers due to hw issue.
Signed-off-by: Troy Lee <troy_...@aspeedtech.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250317065938.1902272-2-troy_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 47cdaa46f3f2c6710911543f2ec836eeb624969e
https://github.com/qemu/qemu/commit/47cdaa46f3f2c6710911543f2ec836eeb624969e
Author: Joe Komlodi <koml...@google.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/ssi/aspeed_smc.c
Log Message:
-----------
hw/ssi/aspeed_smc: Allow 64-bit wide flash accesses
cde3247651dc998da5dc1005148302a90d72f21f fixed atomicity for LDRD, which
ends up making accesses 64-bits wide. However, the AST2600 bootloader
can sometimes compile with LDRD instructions, which causes the acceses
to fail when accessing the memory-mapped SPI flash.
To fix this, increase the MMIO region valid access size to allow for
64-bit accesses.
Signed-off-by: Joe Komlodi <koml...@google.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250422002747.2593465-1-koml...@google.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 9b671ea9bd88e8ad14325eac4240850792458136
https://github.com/qemu/qemu/commit/9b671ea9bd88e8ad14325eac4240850792458136
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M tests/functional/test_arm_aspeed_ast2500.py
Log Message:
-----------
tests/functional/aspeed: Update test ASPEED SDK v09.06 for AST2500
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250423014008.147542-2-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 88bff6d5b2955d4b629a664c21cb7d91ff8a236c
https://github.com/qemu/qemu/commit/88bff6d5b2955d4b629a664c21cb7d91ff8a236c
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M tests/functional/test_arm_aspeed_ast2600.py
Log Message:
-----------
tests/functional/aspeed: Update test ASPEED SDK v09.06 for AST2600
Update test for AST2600 production revision A3.
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250423014008.147542-3-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 53f3285e11876aae97d4240d944d45a4fe6c4597
https://github.com/qemu/qemu/commit/53f3285e11876aae97d4240d944d45a4fe6c4597
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M tests/functional/test_arm_aspeed_ast1030.py
Log Message:
-----------
tests/functional/aspeed: Update test ASPEED SDK v03.00 for AST1030
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250423014008.147542-4-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 8bc296c9b1122916166c021492c470c522e0fd16
https://github.com/qemu/qemu/commit/8bc296c9b1122916166c021492c470c522e0fd16
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/arm/aspeed_ast27x0.c
Log Message:
-----------
hw/arm/aspeed_ast27x0: Rename variable sram_name to name in ast2700 realize
The variable "sram_name" was only used for naming the SRAM memory region.
Rename it to "name" for consistency with similar code and avoid unnecessary
new local variable declarations.
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Tested-by: Nabih Estefan <nabiheste...@google.com>
Link:
https://lore.kernel.org/qemu-devel/20250423072350.541742-2-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 80c734ce92e3b68cdb8e82dfd094b3ba23900f17
https://github.com/qemu/qemu/commit/80c734ce92e3b68cdb8e82dfd094b3ba23900f17
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M tests/functional/test_aarch64_aspeed.py
Log Message:
-----------
tests/functional/aspeed: Move I2C test into shared helper for AST2700 reuse
Move the I2C test case into a common helper function (do_ast2700_i2c_test) so it
can be reused across multiple AST2700-based test cases. This reduces duplication
and improves maintainability.
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Nabih Estefan <nabiheste...@google.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250423072350.541742-8-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: b2a7c02a9a6d350005f722ca3df50df20d7f051e
https://github.com/qemu/qemu/commit/b2a7c02a9a6d350005f722ca3df50df20d7f051e
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M tests/functional/test_aarch64_aspeed.py
Log Message:
-----------
tests/functional/aspeed: Update test ASPEED SDK v09.06
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250423072350.541742-9-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: af93cef791b5976b9b6d977da36e25999a6cebe1
https://github.com/qemu/qemu/commit/af93cef791b5976b9b6d977da36e25999a6cebe1
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M tests/functional/test_aarch64_aspeed.py
Log Message:
-----------
tests/functional/aspeed: extract boot and login sequence into helper function
Extracted repeated boot and login steps into a new helper function.
No change in functional behavior.
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250423072350.541742-10-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 2e143da2fbd92d9c3ae2d7a315efca5c6af24e69
https://github.com/qemu/qemu/commit/2e143da2fbd92d9c3ae2d7a315efca5c6af24e69
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/arm/aspeed_ast27x0.c
M include/hw/arm/aspeed_soc.h
Log Message:
-----------
hw/arm/aspeed_ast27x0 Introduce vbootrom memory region
Introduce a new vbootrom memory region. The region is mapped at address
"0x00000000" and has a size of 128KB, identical to the SRAM region size.
This memory region is intended for loading a vbootrom image file as part of the
boot process.
The vbootrom registered in the SoC's address space using the ASPEED_DEV_VBOOTROM
index.
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Nabih Estefan <nabiheste...@google.com>
Tested-by: Nabih Estefan <nabiheste...@google.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250424075135.3715128-2-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: ee447054404ed8bbdea0eece888da354afe38d97
https://github.com/qemu/qemu/commit/ee447054404ed8bbdea0eece888da354afe38d97
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/arm/aspeed.c
M include/hw/arm/aspeed.h
Log Message:
-----------
hw/arm/aspeed: Add support for loading vbootrom image via "-bios"
Introduce "aspeed_load_vbootrom()" to support loading a virtual boot ROM image
into the vbootrom memory region, using the "-bios" command-line option.
Introduce a new "vbootrom" field in the AspeedMachineClass to indicate whether
a machine supports the virtual boot ROM region.
Set this field to true by default for the AST2700-A0 and AST2700-A1 EVB
machines.
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Nabih Estefan <nabiheste...@google.com>
Tested-by: Nabih Estefan <nabiheste...@google.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250424075135.3715128-4-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 9e3d7afd7da40c9a1ba1a6b4e1103037f3a77da8
https://github.com/qemu/qemu/commit/9e3d7afd7da40c9a1ba1a6b4e1103037f3a77da8
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M tests/functional/test_aarch64_aspeed.py
Log Message:
-----------
tests/functional/aspeed: Add to test vbootrom for AST2700
Add the AST2700 functional test to boot using the vbootrom image
instead of manually loading boot components with -device loader.
The boot ROM binary is now passed via the
-bios option, using the image located in pc-bios/ast27x0_bootrom.bin.
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250424075135.3715128-5-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 3eb01cfe9b85cd64255f6ef93346a3de17fa9632
https://github.com/qemu/qemu/commit/3eb01cfe9b85cd64255f6ef93346a3de17fa9632
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M docs/system/arm/aspeed.rst
Log Message:
-----------
docs/system/arm/aspeed: move AST2700 content to new section
Moved AST2700-related content from the general Aspeed board list into a
dedicated section for Aspeed 2700 family boards. Improves clarity and
readability.
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250424075135.3715128-6-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: d2b857ef9a997237ebedda53c3db50b264baf4fc
https://github.com/qemu/qemu/commit/d2b857ef9a997237ebedda53c3db50b264baf4fc
Author: Jamin Lin <jamin_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M docs/system/arm/aspeed.rst
Log Message:
-----------
docs/system/arm/aspeed: Support vbootrom for AST2700
Using the vbootrom image support and the boot ROM binary is
now passed via the -bios option, using the image located in
pc-bios/ast27x0_bootrom.bin.
Signed-off-by: Jamin Lin <jamin_...@aspeedtech.com>
Reviewed-by: Nabih Estefan <nabiheste...@google.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250424075135.3715128-7-jamin_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 91064bea6b2d747a981cb3bd2904e56f443e6c67
https://github.com/qemu/qemu/commit/91064bea6b2d747a981cb3bd2904e56f443e6c67
Author: Steven Lee <steven_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/arm/aspeed_ast27x0.c
M include/hw/arm/aspeed_soc.h
Log Message:
-----------
aspeed: ast27x0: Map unimplemented devices in SoC memory
Maps following unimplemented devices in SoC memory
- dpmcu
- iomem
- iomem0
- iomem1
- ltpi
Iomem, Iomem0 and Iomem1 include unimplemented controllers in the memory ranges
0x0 - 0x1000000, 0x120000000 - 0x121000000 and
0x14000000 - 0x141000000.
For instance:
- USB hub at 0x12010000
- eSPI at 0x14C5000
- PWM at 0x140C0000
DPMCU stands for Display Port MCU controller. LTPI is used to connect to
AST1700.
AST1700 is an I/O expander that supports the DC-SCM 2.1 LTPI protocol.
It provides AST2700 with additional GPIO, UART, I3C, and other interfaces.
Signed-off-by: Steven Lee <steven_...@aspeedtech.com>
Change-Id: Iae4db49a4818af3e2c43c16a27fc76329d2405d6
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250502103449.3091642-2-steven_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 78110f821aa0c372bb8141ce8ec9f543f8660c36
https://github.com/qemu/qemu/commit/78110f821aa0c372bb8141ce8ec9f543f8660c36
Author: Steven Lee <steven_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/arm/aspeed_ast27x0.c
Log Message:
-----------
aspeed: ast27x0: Correct hex notation for device addresses
Corrected the hexadecimal notation for several device addresses in the
aspeed_soc_ast2700_memmap array by changing the uppercase 'X' to
lowercase 'x'.
Signed-off-by: Steven Lee <steven_...@aspeedtech.com>
Change-Id: I45426e18ea8e68d7ccdf9b60c4ea235c4da33cc3
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250502103449.3091642-3-steven_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 8872b6717c37001e8f2e6c4ed0af20b1811d8f58
https://github.com/qemu/qemu/commit/8872b6717c37001e8f2e6c4ed0af20b1811d8f58
Author: Steven Lee <steven_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/intc/aspeed_intc.c
M include/hw/intc/aspeed_intc.h
Log Message:
-----------
hw/intc/aspeed: Add support for AST2700 SSP INTC
- Define new types for ast2700ssp INTC and INTCIO
- Add register definitions for SSP INTC and INTCIO
- Implement write handlers for SSP INTC and INTCIO
- Register new types in aspeed_intc_register_types
The design of the SSP INTC and INTCIO controllers is similar to
AST2700, with the following differences:
- AST2700
Support GICINT128 to GICINT136 in INTC
The INTCIO GIC_192_201 has 10 output pins, mapped as follows:
Bit 0 -> GIC 192
Bit 1 -> GIC 193
Bit 2 -> GIC 194
Bit 3 -> GIC 195
Bit 4 -> GIC 196
- AST2700-ssp
Support SSPINT128 to SSPINT136 in INTC
The INTCIO SSPINT_160_169 has 10 output pins, mapped as follows:
Bit 0 -> SSPINT 160
Bit 1 -> SSPINT 161
Bit 2 -> SSPINT 162
Bit 3 -> SSPINT 163
Bit 4 -> SSPINT 164
Signed-off-by: Steven Lee <steven_...@aspeedtech.com>
Change-Id: Ib8cb0e264505cef48e17f173e057f3b2d1ea35c4
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250502103449.3091642-4-steven_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: c528f10dce8eeaabe97f216d6488a6b8509b7067
https://github.com/qemu/qemu/commit/c528f10dce8eeaabe97f216d6488a6b8509b7067
Author: Steven Lee <steven_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/intc/aspeed_intc.c
M include/hw/intc/aspeed_intc.h
Log Message:
-----------
hw/intc/aspeed: Add support for AST2700 TSP INTC
- Define new types for ast2700tsp INTC and INTCIO
- Add register definitions for TSP INTC and INTCIO
- Implement write handlers for TSP INTC and INTCIO
- Register new types in aspeed_intc_register_types
The design of the TSP INTC and INTCIO controllers is similar to
AST2700, with the following differences:
- AST2700
Support GICINT128 to GICINT136 in INTC
The INTCIO GIC_192_201 has 10 output pins, mapped as follows:
Bit 0 -> GIC 192
Bit 1 -> GIC 193
Bit 2 -> GIC 194
Bit 3 -> GIC 195
Bit 4 -> GIC 196
- AST2700-tsp
Support TSPINT128 to TSPINT136 in INTC
The INTCIO TSPINT_160_169 has 10 output pins, mapped as follows:
Bit 0 -> TSPINT 160
Bit 1 -> TSPINT 161
Bit 2 -> TSPINT 162
Bit 3 -> TSPINT 163
Bit 4 -> TSPINT 164
Signed-off-by: Steven Lee <steven_...@aspeedtech.com>
Change-Id: I3f3aca4b90129640369cf4a92deb4b9a12df5b70
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250502103449.3091642-5-steven_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 541da2604fe157d9db5995808097230a9f966b4a
https://github.com/qemu/qemu/commit/541da2604fe157d9db5995808097230a9f966b4a
Author: Steven Lee <steven_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
A hw/arm/aspeed_ast27x0-ssp.c
M hw/arm/meson.build
M include/hw/arm/aspeed_soc.h
Log Message:
-----------
hw/arm/aspeed_ast27x0-ssp: Introduce AST27x0 A1 SSP SoC
The AST2700 SSP (Secondary Service Processor) is a Cortex-M4 coprocessor.
This patch adds support for A1 SSP with the following updates:
- Introduce Aspeed27x0SSPSoCState structure in aspeed_soc.h
- Define memory map and IRQ map for AST27x0 A1 SSP SoC
- Implement initialization and realization functions
- Add support for UART, INTC, and SCU devices
- Map unimplemented devices for IPC and SCUIO
The IRQ mapping is similar to AST2700 CA35 SoC, featuring a two-level
interrupt controller.
Difference from AST2700:
- AST2700
- Support GICINT128 to GICINT136 in INTC
- The INTCIO GIC_192_201 has 10 output pins, mapped as follows:
Bit 0 -> GIC 192
Bit 1 -> GIC 193
Bit 2 -> GIC 194
Bit 3 -> GIC 195
Bit 4 -> GIC 196
- AST2700-ssp
- Support SSPINT128 to SSPINT136 in INTC
- The INTCIO SSPINT_160_169 has 10 output pins, mapped as follows:
Bit 0 -> SSPINT 160
Bit 1 -> SSPINT 161
Bit 2 -> SSPINT 162
Bit 3 -> SSPINT 163
Bit 4 -> SSPINT 164
Signed-off-by: Steven Lee <steven_...@aspeedtech.com>
Change-Id: I924bf1a657f1e83f9e16d6673713f4a06ecdb496
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250502103449.3091642-6-steven_...@aspeedtech.com
[ clg: removed local 'Error* err' in aspeed_soc_ast27x0ssp_realize() ]
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 2d64e6a009e1efbf6d9ae63a3dc5d35f356641e7
https://github.com/qemu/qemu/commit/2d64e6a009e1efbf6d9ae63a3dc5d35f356641e7
Author: Steven Lee <steven_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
A hw/arm/aspeed_ast27x0-tsp.c
M hw/arm/meson.build
M include/hw/arm/aspeed_soc.h
Log Message:
-----------
hw/arm/aspeed_ast27x0-tsp: Introduce AST27x0 A1 TSP SoC
AST2700 TSP(Tertiary Service Processor) is a Cortex-M4 coprocessor
The patch adds support for TSP with following update:
- Introduce Aspeed27x0TSPSoCState structure in aspeed_soc.h
- Implement initialization and realization functions
- Add support for UART, INTC, and SCU devices
- Map unimplemented devices for IPC and SCUIO
- Defined memory map and IRQ maps for AST27x0 A1 TSP SoC
The IRQ mapping is similar to AST2700 CA35 SoC, featuring a two-level
interrupt controller.
Difference from AST2700:
- AST2700
- Support GICINT128 to GICINT136 in INTC
- The INTCIO GIC_192_201 has 10 output pins, mapped as follows:
Bit 0 -> GIC 192
Bit 1 -> GIC 193
Bit 2 -> GIC 194
Bit 3 -> GIC 195
Bit 4 -> GIC 196
- AST2700-tsp
- Support TSPINT128 to TSPINT136 in INTC
- The INTCIO TSPINT_160_169 has 10 output pins, mapped as follows:
Bit 0 -> TSPINT 160
Bit 1 -> TSPINT 161
Bit 2 -> TSPINT 162
Bit 3 -> TSPINT 163
Bit 4 -> TSPINT 164
Signed-off-by: Steven Lee <steven_...@aspeedtech.com>
Change-Id: I69eec2b68b26ef04187b2922c5f2e584b9076c66
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250502103449.3091642-7-steven_...@aspeedtech.com
[ clg: removed local 'Error* err' in aspeed_soc_ast27x0tsp_realize() ]
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: a74faf35efc5befb95d57041c9321a90a0edbb6d
https://github.com/qemu/qemu/commit/a74faf35efc5befb95d57041c9321a90a0edbb6d
Author: Steven Lee <steven_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
A hw/arm/aspeed_ast27x0-fc.c
M hw/arm/meson.build
Log Message:
-----------
hw/arm: Introduce ASPEED AST2700 A1 full core machine
- Added new machine type `ast2700fc` with full core support.
- Defined `Ast2700FCState` structure for the new machine type.
- Implemented initialization functions for CA35, SSP, and TSP components.
- Updated `ast2700fc_types` to include the new machine type.
- Set machine class properties for `ast2700fc`.
Test Step:
- Download ast2700-default-obmc.tar.gz from AspeedTech-BMC OpenBmc
release page.
- Run the following QEMU command:
```
IMGDIR=~/path/to/image
UBOOT_SIZE=$(stat --format=%s -L ${IMGDIR}/u-boot-nodtb.bin)
./qemu-system-aarch64 -machine ast2700fc \
-device loader,force-raw=on,addr=0x400000000,file=${IMGDIR}/u-boot-nodtb.bin \
-device loader,force-raw=on,addr=$((0x400000000 +
${UBOOT_SIZE})),file=${IMGDIR}/u-boot.dtb \
-device loader,force-raw=on,addr=0x430000000,file=${IMGDIR}/bl31.bin \
-device loader,force-raw=on,addr=0x430080000,file=${IMGDIR}/tee-raw.bin \
-device loader,cpu-num=0,addr=0x430000000 \
-device loader,cpu-num=1,addr=0x430000000 \
-device loader,cpu-num=2,addr=0x430000000 \
-device loader,cpu-num=3,addr=0x430000000 \
-device loader,file=${IMGDIR}/ast2700-ssp.elf,cpu-num=4 \
-device loader,file=${IMGDIR}/ast2700-tsp.elf,cpu-num=5 \
-drive file=${IMGDIR}/image-bmc,if=mtd,format=raw \
-serial pty -serial pty -serial pty \
-snapshot \
-S -nographic
```
- After starting QEMU, serial devices will be redirected:
char device redirected to /dev/pts/51 (label serial0)
char device redirected to /dev/pts/52 (label serial1)
char device redirected to /dev/pts/53 (label serial2)
- serial0 is the console for the four Cortex-A35 primary processors,
serial1 and serial2 are the consoles for the two Cortex-M4 coprocessors.
- Connect to the consoles using a terminal emulator.
Signed-off-by: Steven Lee <steven_...@aspeedtech.com>
Change-Id: I32447b9372a78eb53a07135afef59c2a19202328
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250502103449.3091642-8-steven_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 81c74475433c69f6a4d67fcba463622c63667807
https://github.com/qemu/qemu/commit/81c74475433c69f6a4d67fcba463622c63667807
Author: Steven Lee <steven_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M tests/functional/meson.build
R tests/functional/test_aarch64_aspeed.py
A tests/functional/test_aarch64_aspeed_ast2700.py
A tests/functional/test_aarch64_aspeed_ast2700fc.py
Log Message:
-----------
tests/function/aspeed: Add functional test for ast2700fc
Introduce a new test suite for ast2700fc machine.
Rename the original test_aarch64_aspeed.py to
test_aarch64_aspeed_ast2700.py.
Signed-off-by: Steven Lee <steven_...@aspeedtech.com>
Change-Id: I3855f55c9f6e5cca1270c179445f549f8d81f36c
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250505030618.3612042-1-steven_...@aspeedtech.com
[ clg: Added new tests in meson.build ]
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: f32ef57f7de98ec36da52b0a13bd5d18ac4bd583
https://github.com/qemu/qemu/commit/f32ef57f7de98ec36da52b0a13bd5d18ac4bd583
Author: Steven Lee <steven_...@aspeedtech.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M docs/system/arm/aspeed.rst
Log Message:
-----------
docs: Add support for ast2700fc machine
- Updated Aspeed family boards list to include `ast2700fc`.
- Added boot instructions for the `ast2700fc` machine.
- Detailed the configuration and loading of firmware for the
Cortex-A35 and Cortex-M4 processors.
Signed-off-by: Steven Lee <steven_...@aspeedtech.com>
Change-Id: Id41312e9c7cf79bc55c6f24a87a7ad9993dc7261
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/20250502103449.3091642-10-steven_...@aspeedtech.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 61da38db70affd925226ce1e8a61d761c20d045b
https://github.com/qemu/qemu/commit/61da38db70affd925226ce1e8a61d761c20d045b
Author: Christian Schoenebeck <qemu_...@crudebyte.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/9pfs/9p.c
M hw/9pfs/9p.h
Log Message:
-----------
9pfs: fix concurrent v9fs_reclaim_fd() calls
Even though this function is serialized to be always called from main
thread, v9fs_reclaim_fd() is dispatching the coroutine to a worker thread
in between via its v9fs_co_*() calls, hence leading to the situation where
v9fs_reclaim_fd() is effectively executed multiple times simultaniously,
which renders its LRU algorithm useless and causes high latency.
Fix this by adding a simple boolean variable to ensure this function is
only called once at a time. No synchronization needed for this boolean
variable as this function is only entered and returned on main thread.
Fixes: 7a46274529c ('hw/9pfs: Add file descriptor reclaim support')
Signed-off-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Reviewed-by: Greg Kurz <gr...@kaod.org>
Message-Id:
<5c622067efd66dd4ee5eca740dcf263f41db20b2.1741339452.git.qemu_...@crudebyte.com>
Commit: 89f7b4da7662ecc6840ffb0846045f03f9714bc6
https://github.com/qemu/qemu/commit/89f7b4da7662ecc6840ffb0846045f03f9714bc6
Author: Christian Schoenebeck <qemu_...@crudebyte.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/9pfs/9p.c
Log Message:
-----------
9pfs: fix FD leak and reduce latency of v9fs_reclaim_fd()
This patch fixes two different bugs in v9fs_reclaim_fd():
1. Reduce latency:
This function calls v9fs_co_close() and v9fs_co_closedir() in a loop. Each
one of the calls adds two thread hops (between main thread and a fs driver
background thread). Each thread hop adds latency, which sums up in
function's loop to a significant duration.
Reduce overall latency by open coding what v9fs_co_close() and
v9fs_co_closedir() do, executing those and the loop itself altogether in
only one background thread block, hence reducing the total amount of
thread hops to only two.
2. Fix file descriptor leak:
The existing code called v9fs_co_close() and v9fs_co_closedir() to close
file descriptors. Both functions check right at the beginning if the 9p
request was cancelled:
if (v9fs_request_cancelled(pdu)) {
return -EINTR;
}
So if client sent a 'Tflush' message, v9fs_co_close() / v9fs_co_closedir()
returned without having closed the file descriptor and v9fs_reclaim_fd()
subsequently freed the FID without its file descriptor being closed, hence
leaking those file descriptors.
This 2nd bug is fixed by this patch as well by open coding v9fs_co_close()
and v9fs_co_closedir() inside of v9fs_reclaim_fd() and not performing the
v9fs_request_cancelled(pdu) check there.
Fixes: 7a46274529c ('hw/9pfs: Add file descriptor reclaim support')
Fixes: bccacf6c792 ('hw/9pfs: Implement TFLUSH operation')
Signed-off-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Reviewed-by: Greg Kurz <gr...@kaod.org>
Message-Id:
<5747469d3f039c53147e850b456943a1d4b5485c.1741339452.git.qemu_...@crudebyte.com>
Commit: 4f82ce8cd94f2601fb2b2e4cfe0cf5b44131817e
https://github.com/qemu/qemu/commit/4f82ce8cd94f2601fb2b2e4cfe0cf5b44131817e
Author: Greg Kurz <gr...@kaod.org>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/9pfs/9p-local.c
Log Message:
-----------
9pfs: local : Introduce local_fid_fd() helper
Factor out duplicated code to a single helper. More users to come.
Signed-off-by: Greg Kurz <gr...@kaod.org>
Reviewed-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Message-Id: <20250312152933.383967-2-gr...@kaod.org>
Signed-off-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Commit: f2bb367d2b265c6c0ead1e0d4a8f7c43310b3107
https://github.com/qemu/qemu/commit/f2bb367d2b265c6c0ead1e0d4a8f7c43310b3107
Author: Greg Kurz <gr...@kaod.org>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M fsdev/file-op-9p.h
M hw/9pfs/9p-local.c
M hw/9pfs/9p-synth.c
M hw/9pfs/9p.c
Log Message:
-----------
9pfs: Don't use file descriptors in core code
v9fs_getattr() currently peeks into V9fsFidOpenState to know if a fid
has a valid file descriptor or directory stream. Even though the fields
are accessible, this is an implementation detail of the local backend
that should not be manipulated directly by the server code.
Abstract that with a new has_valid_file_handle() backend operation.
Signed-off-by: Greg Kurz <gr...@kaod.org>
Reviewed-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Message-Id: <20250312152933.383967-3-gr...@kaod.org>
Signed-off-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Commit: 0c798dd52355f3489b29bba0dfd7df0e24cfa1dd
https://github.com/qemu/qemu/commit/0c798dd52355f3489b29bba0dfd7df0e24cfa1dd
Author: Greg Kurz <gr...@kaod.org>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M fsdev/file-op-9p.h
M hw/9pfs/9p-local.c
M hw/9pfs/9p-synth.c
M hw/9pfs/9p.c
M hw/9pfs/cofs.c
M hw/9pfs/coth.h
Log Message:
-----------
9pfs: Introduce ftruncate file op
Add an ftruncate operation to the fs driver and use if when a fid has
a valid file descriptor. This is required to support more cases where
the client wants to do an action on an unlinked file which it still
has an open file decriptor for.
Only 9P2000.L was considered.
Signed-off-by: Greg Kurz <gr...@kaod.org>
Reviewed-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Message-Id: <20250312152933.383967-4-gr...@kaod.org>
Signed-off-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Commit: 371a269ff8ce561c28e4fa03bb49e4940f990637
https://github.com/qemu/qemu/commit/371a269ff8ce561c28e4fa03bb49e4940f990637
Author: Greg Kurz <gr...@kaod.org>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M fsdev/file-op-9p.h
M hw/9pfs/9p-local.c
M hw/9pfs/9p-synth.c
M hw/9pfs/9p-util.h
M hw/9pfs/9p.c
M hw/9pfs/cofs.c
M hw/9pfs/coth.h
Log Message:
-----------
9pfs: Introduce futimens file op
Add an futimens operation to the fs driver and use if when a fid has
a valid file descriptor. This is required to support more cases where
the client wants to do an action on an unlinked file which it still
has an open file decriptor for.
Only 9P2000.L was considered.
Signed-off-by: Greg Kurz <gr...@kaod.org>
Reviewed-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Message-Id: <20250312152933.383967-5-gr...@kaod.org>
Signed-off-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Commit: 4719a2d59176a6c850e2b4f1af44cecd25430fce
https://github.com/qemu/qemu/commit/4719a2d59176a6c850e2b4f1af44cecd25430fce
Author: Christian Schoenebeck <qemu_...@crudebyte.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M tests/qtest/libqos/virtio-9p-client.c
M tests/qtest/libqos/virtio-9p-client.h
M tests/qtest/virtio-9p-test.c
Log Message:
-----------
tests/9p: add 'Tsetattr' request to test client
Add and implement functions to 9pfs test client for sending a 9p2000.L
'Tsetattr' request and receiving its 'Rsetattr' response counterpart.
Signed-off-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Signed-off-by: Greg Kurz <gr...@kaod.org>
Message-Id: <20250312152933.383967-6-gr...@kaod.org>
Commit: 610dc187e52605c8ea8d14c5e7d8e7384f8af290
https://github.com/qemu/qemu/commit/610dc187e52605c8ea8d14c5e7d8e7384f8af290
Author: Greg Kurz <gr...@kaod.org>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M tests/qtest/virtio-9p-test.c
Log Message:
-----------
tests/9p: Test `Tsetattr` can truncate unlinked file
Enhance the `use-after-unlink` test with a new check for the
case where the client wants to alter the size of an unlinked
file for which it still has an active fid.
Suggested-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Signed-off-by: Greg Kurz <gr...@kaod.org>
Reviewed-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Message-Id: <20250312152933.383967-7-gr...@kaod.org>
Signed-off-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Commit: cdafeda35709ddf8cd982a7eb653c2a5028c8074
https://github.com/qemu/qemu/commit/cdafeda35709ddf8cd982a7eb653c2a5028c8074
Author: Christian Schoenebeck <qemu_...@crudebyte.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M hw/9pfs/9p.c
M hw/9pfs/codir.c
M hw/9pfs/cofile.c
Log Message:
-----------
9pfs: fix 'total_open_fd' decrementation
According to 'man 2 close' errors returned by close() should only be used
for either diagnostic purposes or for catching data loss due to a previous
write error, as an error result of close() usually indicates a deferred
error of a previous write operation.
Therefore not decrementing 'total_open_fd' on a close() error is wrong
and would yield in a higher open file descriptor count than actually the
case, leading to 9p server reclaiming open file descriptors too soon.
Based-on: <20250312152933.383967-7-gr...@kaod.org>
Signed-off-by: Christian Schoenebeck <qemu_...@crudebyte.com>
Reviewed-by: Greg Kurz <gr...@kaod.org>
Message-Id: <e1tveyj-004dma...@kylie.crudebyte.com>
Commit: d0394ab5b94c2536603ea804c06201a1f0634c37
https://github.com/qemu/qemu/commit/d0394ab5b94c2536603ea804c06201a1f0634c37
Author: Stefan Hajnoczi <stefa...@redhat.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M configure
M docs/about/build-platforms.rst
M docs/devel/build-environment.rst
M hw/rtc/mc146818rtc.c
M hw/s390x/ipl.c
M hw/s390x/ipl.h
M hw/s390x/s390-virtio-ccw.c
M meson.build
M meson_options.txt
M python/Makefile
M python/setup.cfg
M python/tests/minreqs.txt
M scripts/meson-buildoptions.sh
M scripts/qapi/mypy.ini
M target/s390x/kvm/pv.c
M target/s390x/kvm/pv.h
M tests/docker/dockerfiles/python.docker
M tests/functional/test_ppc64_pseries.py
Log Message:
-----------
Merge tag 'pull-request-2025-04-30' of https://gitlab.com/thuth/qemu into
staging
* Extend s390x diagnose call 308 subcode 10 to return more information
* Make valgrind support configurable
* Drop support for Python 3.8
* Some other misc cosmetic changes
# -----BEGIN PGP SIGNATURE-----
#
# iQJFBAABCAAvFiEEJ7iIR+7gJQEY8+q5LtnXdP5wLbUFAmgScIQRHHRodXRoQHJl
# ZGhhdC5jb20ACgkQLtnXdP5wLbXf+hAAnt6RcceX8e9CSXaggozXMeI5c/7nMUJl
# PTJrWV0HXhspKR2SEYADkKk5cVGWnSum7PDgrwHXMyykUSE2jOsUhIrWauyLaiuE
# fKIOhTOX6DiYPINVJzsJ8JXrJ7jkYmnGMnrbZg1i1wnYwx9ZkAAZOagGu4pMguml
# digEVMJp7KiGztCrQwA/Og1zrTTPP9a6071tCvungQJDMrLuJgYb+hafpoNBaAy3
# WoOqP/Fh5AXHkySZlKGhL/mqrj7FVSUMWsNoBncZXtTcnnSP4u6gVt0fd7W9LC6u
# QGGGTEV8UkRhiW4s/Dxd6HOt0OS9m4sDWbubYv9nzIfRM1X8rfKqOCnjKxbeU/lI
# kdoZpK1FSyzKcH+QvEVYaQv33BitVrx3h+WQKgSCZTmTit9TjshBAEDAvzfL6oML
# xYM4oqf0kWqlJjIfatx11dfLJLpAwk8jtgKz9iSPH11lLqGQmsdPNMEdXvUiuiSZ
# tddvuKn0AKwTNO+OWonztBO2aiADSO9hZhWAPVuZUTYCt9zWyQF4ddAgOm2+FZOg
# B9u01aBNSodTaBFASDabWnoi/09lPuhcqINB18XJXG3EsdbrtTP9PjHkSL8Oj+eA
# v2g+uuxIlD3OfvTdrRAVpRjrGBcz3yKkPOw4KA/pnCyP/w3SnoObu0GjFcD4Okuk
# pfvd8eAw7dI=
# =K0wD
# -----END PGP SIGNATURE-----
# gpg: Signature made Wed 30 Apr 2025 14:48:36 EDT
# gpg: using RSA key 27B88847EEE0250118F3EAB92ED9D774FE702DB5
# gpg: issuer "th...@redhat.com"
# gpg: Good signature from "Thomas Huth <th.h...@gmx.de>" [full]
# gpg: aka "Thomas Huth <th...@redhat.com>" [full]
# gpg: aka "Thomas Huth <h...@tuxfamily.org>" [full]
# gpg: aka "Thomas Huth <th.h...@posteo.de>" [unknown]
# Primary key fingerprint: 27B8 8847 EEE0 2501 18F3 EAB9 2ED9 D774 FE70 2DB5
* tag 'pull-request-2025-04-30' of https://gitlab.com/thuth/qemu:
docs/devel/build-environment: enhance MSYS2 instructions
hw/rtc/mc146818rtc: Drop pre-v3 migration stream support
meson.build: Put the D-Bus summary into the UI section
tests/functional/test_ppc64_pseries: Skip test_ppc64_linux_smt_boot if
necessary
Drop support for Python 3.8
meson/configure: add 'valgrind' option & --{en, dis}able-valgrind flag
target/s390x: Return UVC cmd code, RC and RRC value when DIAG 308 Subcode 10
fails to enter secure mode
target/s390x: Introduce function when exiting PV
target/s390x: Introduce constant when checking if PV header couldn't be
decrypted
Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com>
Commit: b6f568262b48ca0cb3dc018909908017551b5679
https://github.com/qemu/qemu/commit/b6f568262b48ca0cb3dc018909908017551b5679
Author: Stefan Hajnoczi <stefa...@redhat.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M MAINTAINERS
M include/migration/register.h
M migration/migration.c
M migration/multifd.c
M migration/multifd.h
M migration/options.c
M migration/options.h
M migration/ram.c
M migration/rdma.c
M migration/rdma.h
M migration/savevm.c
M migration/savevm.h
A scripts/rdma-migration-helper.sh
M scripts/vmstate-static-checker.py
M tests/qtest/migration/compression-tests.c
M tests/qtest/migration/cpr-tests.c
M tests/qtest/migration/file-tests.c
M tests/qtest/migration/framework.c
M tests/qtest/migration/framework.h
M tests/qtest/migration/misc-tests.c
M tests/qtest/migration/postcopy-tests.c
M tests/qtest/migration/precopy-tests.c
M tests/qtest/migration/tls-tests.c
Log Message:
-----------
Merge tag 'migration-20250502-pull-request' of https://gitlab.com/peterx/qemu
into staging
Migration pull request
- Prasad's few pre-requisite patches from multifd+postcopy enablement series
- Markus's fix on a latent bug for tls_authz setup
- Zhijian's latest RDMA series (includes the rdma soft-RoCE unit test)
- Jack's RDMA migration patch to re-enable ipv6
- Thomas's vmstate static checker update on rename field in acpi/ghes
- Peter's postcopy preempt optimization for locality hint
# -----BEGIN PGP SIGNATURE-----
#
# iIgEABYKADAWIQS5GE3CDMRX2s990ak7X8zN86vXBgUCaBT1DBIccGV0ZXJ4QHJl
# ZGhhdC5jb20ACgkQO1/MzfOr1wbp5QD8DIxndg/ssr2s+jb4T3tLHj5887FqH9P3
# vU8aoppi4dkA/iYifF8eK+jmhh4yEAP+/NzbmDy+kLO7uEAJDIK+Z/UM
# =Ae6/
# -----END PGP SIGNATURE-----
# gpg: Signature made Fri 02 May 2025 12:38:36 EDT
# gpg: using EDDSA key B9184DC20CC457DACF7DD1A93B5FCCCDF3ABD706
# gpg: issuer "pet...@redhat.com"
# gpg: Good signature from "Peter Xu <xzpe...@gmail.com>" [full]
# gpg: aka "Peter Xu <pet...@redhat.com>" [full]
# Primary key fingerprint: B918 4DC2 0CC4 57DA CF7D D1A9 3B5F CCCD F3AB D706
* tag 'migration-20250502-pull-request' of https://gitlab.com/peterx/qemu:
scripts/vmstate-static-checker.py: Allow new name for ghes_addr_le field
migration/rdma: Remove qemu_rdma_broken_ipv6_kernel
migration/postcopy: Spatial locality page hint for preempt mode
tests/qtest/migration: consolidate set capabilities
migration/ram: Implement save_postcopy_prepare()
migration: Add save_postcopy_prepare() savevm handler
migration: refactor channel discovery mechanism
migration/multifd: move macros to multifd header
migration: Fix latent bug in migrate_params_test_apply()
migration: Add qtest for migration over RDMA
migration: Unfold control_save_page()
migration/rdma: Remove redundant migration_in_postcopy checks
migration: disable RDMA + postcopy-ram
migration: check RDMA and capabilities are compatible on both sides
Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com>
Commit: dc1ed8f256c446cbf33e090f0e214d0311a771a7
https://github.com/qemu/qemu/commit/dc1ed8f256c446cbf33e090f0e214d0311a771a7
Author: Stefan Hajnoczi <stefa...@redhat.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M docs/devel/rust.rst
M hw/char/diva-gsp.c
M hw/char/serial-pci-multi.c
M hw/char/serial-pci.c
M monitor/qmp.c
M rust/Cargo.toml
M rust/hw/char/pl011/Cargo.toml
M rust/hw/timer/hpet/Cargo.toml
M rust/hw/timer/hpet/src/hpet.rs
M rust/qemu-api-macros/Cargo.toml
M rust/qemu-api/Cargo.toml
M rust/qemu-api/src/assertions.rs
M rust/qemu-api/src/timer.rs
M rust/qemu-api/src/vmstate.rs
M rust/qemu-api/tests/vmstate_tests.rs
M target/i386/emulate/x86_decode.c
M target/i386/hvf/hvf.c
M target/i386/tcg/emit.c.inc
M target/i386/tcg/translate.c
Log Message:
-----------
Merge tag 'for-upstream' of https://gitlab.com/bonzini/qemu into staging
* rust: support migration of HPET device
* target/i386/hvf: fix compilation errors
* target/i386/tcg: fix some interrupt shadow cases
* hw/char/serial: remove unused prog_if compat property
* rust: centralize config in workspace root
* monitor: fix race on exiting QEMU
# -----BEGIN PGP SIGNATURE-----
#
# iQFIBAABCgAyFiEE8TM4V0tmI4mGbHaCv/vSX3jHroMFAmgVQzkUHHBib256aW5p
# QHJlZGhhdC5jb20ACgkQv/vSX3jHroOR8Af/Tke7kRZQyvoKURaKpVOBgP91fTQu
# IKwmX1OYe9JMPBwZV5g/++2HSaAddDzkFq90gmgTY+hpvRE3kDWOA86QtDRP4LKa
# Oq3yW48yrFiRZBAxERgRxRCsEvzlPC3cAEqCQd4fTL+cW6NVorbj4x/tQcALb47V
# cgXXVp59TW4lJk7nJUjd0mCFK1qEoIbZuuBgMn32K+fpBV/UghcoImT2giMeM24Y
# WW3olrLA9UN2fh5da7923WUvA9mSjnE0Yfdk6eKC3nCzlgMKktofwKHilm0tA6xA
# 7sJbwYTDSB9QxgnNw3WvAFAOMapJmedaSNorZdmcxCss7ed0s8hV8am9vQ==
# =LFS/
# -----END PGP SIGNATURE-----
# gpg: Signature made Fri 02 May 2025 18:12:09 EDT
# gpg: using RSA key F13338574B662389866C7682BFFBD25F78C7AE83
# gpg: issuer "pbonz...@redhat.com"
# gpg: Good signature from "Paolo Bonzini <bonz...@gnu.org>" [full]
# gpg: aka "Paolo Bonzini <pbonz...@redhat.com>" [full]
# Primary key fingerprint: 46F5 9FBD 57D6 12E7 BFD4 E2F7 7E15 100C CD36 69B1
# Subkey fingerprint: F133 3857 4B66 2389 866C 7682 BFFB D25F 78C7 AE83
* tag 'for-upstream' of https://gitlab.com/bonzini/qemu:
monitor: don't wake up qmp_dispatcher_co coroutine upon cleanup
rust: centralize config in workspace root
hw/char/serial: Remove unused prog_if compat property
target/i386: do not block singlestep for STI
target/i386: do not trigger IRQ shadow for LSS
target/i386/hvf: fix a compilation error
target/i386/emulate: remove rflags leftovers
rust/hpet: Support migration
rust/timer: Define NANOSECONDS_PER_SECOND binding as u64
rust/vmstate_test: Test varray with num field wrapped in BqlCell
rust: assertions: Support index field wrapped in BqlCell
vmstate: support varray for vmstate_clock!
rust/vmstate: Add support for field_exists checks
Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com>
Commit: 6d0d9add0d98effc7045466249921a09845225ac
https://github.com/qemu/qemu/commit/6d0d9add0d98effc7045466249921a09845225ac
Author: Stefan Hajnoczi <stefa...@redhat.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M MAINTAINERS
M docs/system/arm/aspeed.rst
M hw/arm/aspeed.c
A hw/arm/aspeed_ast27x0-fc.c
A hw/arm/aspeed_ast27x0-ssp.c
A hw/arm/aspeed_ast27x0-tsp.c
M hw/arm/aspeed_ast27x0.c
M hw/arm/meson.build
M hw/intc/aspeed_intc.c
M hw/ssi/aspeed_smc.c
M include/hw/arm/aspeed.h
M include/hw/arm/aspeed_soc.h
M include/hw/intc/aspeed_intc.h
M pc-bios/README
A pc-bios/ast27x0_bootrom.bin
M pc-bios/meson.build
M tests/functional/meson.build
R tests/functional/test_aarch64_aspeed.py
A tests/functional/test_aarch64_aspeed_ast2700.py
A tests/functional/test_aarch64_aspeed_ast2700fc.py
M tests/functional/test_arm_aspeed_ast1030.py
M tests/functional/test_arm_aspeed_ast2500.py
M tests/functional/test_arm_aspeed_ast2600.py
Log Message:
-----------
Merge tag 'pull-aspeed-20250505' of https://github.com/legoater/qemu into
staging
aspeed queue:
* Fixed AST2700 SPI model issues
* Updated SDK images
* Added FW support to the AST2700 EVB machines
* Introduced an AST27x0 multi-SoC machine
# -----BEGIN PGP SIGNATURE-----
#
# iQIzBAABCAAdFiEEoPZlSPBIlev+awtgUaNDx8/77KEFAmgYf0sACgkQUaNDx8/7
# 7KGYGxAAokBF+jSjl7DgDbpkKu0RhJeV02rUPXIDehyBW+NcjL3xcG8f36wraZ4+
# SYGESnWCymKlQi9ZYdqIQ86w4WSNDQ1s1pjefcvqEFBTCny1TRwNgocBQkdBcNhb
# 1iIBpOu5c8j6i83U73W46OXwPBopXI2OzcxvX0lclOze3+qzHT6CDYgezXoNlJtG
# RSJjeFO9sEghPgXzkBMrCotV4n7pDGeSpB9nSFfkzRekEbq3rzT6s6JxS1pylzut
# g6YU6YqFl+RrR/5HRo5hIFE+YmqDvTpYnd8k5sJq9CxYSIXMkJImxssvg2oO5aoF
# BVv/XxWVJ/oDEorXg5qNaRHzVk3StEX42boDQgj+dWsp1Q/4jdokrgFu7KSUT22q
# mp4Px+Z5xlX5z6TNwp6yvb9Wobr23KjgXRqqqqLEftYrqaI6Nr/vcKjZZ438GzCd
# SpKXxIAlXci1bAaDUTdfQnJyKe+ltJ7wOX1auQFqpI0CYe5Jcu3En6M799ne9azy
# TvfMq0GN1oGNJoYRRmH51gNF0vlnDsDhDHod6i6ZmBFWGnMOtbti3nnEaAdk7JWB
# pueux79YdE+f1q7SuA2X2OEchFxE/kA0B6SxP+IwXEcDyGNfZ6UJWoZGB9amc090
# pTQB1HHOGDEkYsReely1isTDCoZBqzDUreEhPssO0E9Pb/ZfeCE=
# =vBwk
# -----END PGP SIGNATURE-----
# gpg: Signature made Mon 05 May 2025 05:05:15 EDT
# gpg: using RSA key A0F66548F04895EBFE6B0B6051A343C7CFFBECA1
# gpg: Good signature from "Cédric Le Goater <c...@redhat.com>" [full]
# gpg: aka "Cédric Le Goater <c...@kaod.org>" [full]
# Primary key fingerprint: A0F6 6548 F048 95EB FE6B 0B60 51A3 43C7 CFFB ECA1
* tag 'pull-aspeed-20250505' of https://github.com/legoater/qemu: (24 commits)
docs: Add support for ast2700fc machine
tests/function/aspeed: Add functional test for ast2700fc
hw/arm: Introduce ASPEED AST2700 A1 full core machine
hw/arm/aspeed_ast27x0-tsp: Introduce AST27x0 A1 TSP SoC
hw/arm/aspeed_ast27x0-ssp: Introduce AST27x0 A1 SSP SoC
hw/intc/aspeed: Add support for AST2700 TSP INTC
hw/intc/aspeed: Add support for AST2700 SSP INTC
aspeed: ast27x0: Correct hex notation for device addresses
aspeed: ast27x0: Map unimplemented devices in SoC memory
docs/system/arm/aspeed: Support vbootrom for AST2700
docs/system/arm/aspeed: move AST2700 content to new section
tests/functional/aspeed: Add to test vbootrom for AST2700
hw/arm/aspeed: Add support for loading vbootrom image via "-bios"
hw/arm/aspeed_ast27x0 Introduce vbootrom memory region
tests/functional/aspeed: extract boot and login sequence into helper function
tests/functional/aspeed: Update test ASPEED SDK v09.06
tests/functional/aspeed: Move I2C test into shared helper for AST2700 reuse
hw/arm/aspeed_ast27x0: Rename variable sram_name to name in ast2700 realize
tests/functional/aspeed: Update test ASPEED SDK v03.00 for AST1030
tests/functional/aspeed: Update test ASPEED SDK v09.06 for AST2600
...
Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com>
Commit: a9e0c9c0f14e19d23443ac24c8080b4708d2eab8
https://github.com/qemu/qemu/commit/a9e0c9c0f14e19d23443ac24c8080b4708d2eab8
Author: Stefan Hajnoczi <stefa...@redhat.com>
Date: 2025-05-05 (Mon, 05 May 2025)
Changed paths:
M fsdev/file-op-9p.h
M hw/9pfs/9p-local.c
M hw/9pfs/9p-synth.c
M hw/9pfs/9p-util.h
M hw/9pfs/9p.c
M hw/9pfs/9p.h
M hw/9pfs/codir.c
M hw/9pfs/cofile.c
M hw/9pfs/cofs.c
M hw/9pfs/coth.h
M tests/qtest/libqos/virtio-9p-client.c
M tests/qtest/libqos/virtio-9p-client.h
M tests/qtest/virtio-9p-test.c
Log Message:
-----------
Merge tag 'pull-9p-20250505' of https://github.com/cschoenebeck/qemu into
staging
9pfs changes:
* Fixes for file descriptor reclaiming algorithm (i.e. when running
towards host's allowed limit of max. open file descriptors).
* Additional fixes on use-after-unlink idiom (i.e. client operations on a
file descriptor after file has been removed).
# -----BEGIN PGP SIGNATURE-----
#
# iQJLBAABCgA1FiEEltjREM96+AhPiFkBNMK1h2Wkc5UFAmgYie0XHHFlbXVfb3Nz
# QGNydWRlYnl0ZS5jb20ACgkQNMK1h2Wkc5XbDRAAq5SW7Hxifdhf1ZRBtkVOD88q
# Iw/OrMLIke4pCQwRElCDrE0mhycqyUpNX67eIye7qx0dJl2btFQUI9L6YuCDFtcG
# fPORZl51V81BOXqS8MhbK1oDxidl+cnpA8GcA1OyhYjxBifOy/x/0KG0pZVwzi0Y
# jhAIdsfeSenTE0Zzb02oh9mVmlMtKnwrSz7R0IB3Sv575CQiO76OM5B9sps1TUPu
# NrnQYBIB+EwJnI+l9NOKzNa7AUxV/S73OFCyJkQCON2ZHWiVadgXxjlX3kHyh9oL
# 3uiiTdC2694jU0RaVMMSNLfdIG4YK2GkKPHM7qLYF8Kdc5QogEJifS/RoihCnZFR
# X72G7mOVo8/7goRBt3DGQCwz3eUgqTO9iPFn1hJRvx9x/CVlFi2eOP+5nHR5PMEO
# qSY2of6LziCslNXvxjjhf7HmRhlugkHqpr+UGTxwMGazr88bHKNFbsh/3BcTmWwW
# /wGRfEFse3exgFiCtoebavxbJaUeI0Y93S4KidOhhqrQFz24k2AElgFrb1gEpbht
# GWW8YEblL7Lj8mecFATXKiInHCyhVPFmuAO//Wbu9juJVcNPtl67f017bCR+90H3
# GrRJqorHrp6icGQmXSM+Qdrr3B21RZwqb3W4mdMOWN3Zg5bHPHJ6rx8BRe7qDHBH
# mWtvrsUfcL0sRW0nkgc=
# =hfW6
# -----END PGP SIGNATURE-----
# gpg: Signature made Mon 05 May 2025 05:50:37 EDT
# gpg: using RSA key 96D8D110CF7AF8084F88590134C2B58765A47395
# gpg: issuer "qemu_...@crudebyte.com"
# gpg: Good signature from "Christian Schoenebeck <qemu_...@crudebyte.com>"
[unknown]
# gpg: WARNING: The key's User ID is not certified with a trusted signature!
# gpg: There is no indication that the signature belongs to the owner.
# Primary key fingerprint: ECAB 1A45 4014 1413 BA38 4926 30DB 47C3 A012 D5F4
# Subkey fingerprint: 96D8 D110 CF7A F808 4F88 5901 34C2 B587 65A4 7395
* tag 'pull-9p-20250505' of https://github.com/cschoenebeck/qemu:
9pfs: fix 'total_open_fd' decrementation
tests/9p: Test `Tsetattr` can truncate unlinked file
tests/9p: add 'Tsetattr' request to test client
9pfs: Introduce futimens file op
9pfs: Introduce ftruncate file op
9pfs: Don't use file descriptors in core code
9pfs: local : Introduce local_fid_fd() helper
9pfs: fix FD leak and reduce latency of v9fs_reclaim_fd()
9pfs: fix concurrent v9fs_reclaim_fd() calls
Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com>
Compare: https://github.com/qemu/qemu/compare/5134cf9b5d3a...a9e0c9c0f14e
To unsubscribe from these emails, change your notification settings at
https://github.com/qemu/qemu/settings/notifications
