Branch: refs/heads/staging-7.2
Home: https://github.com/qemu/qemu
Commit: 5e1f406424b3a67e8d540e99d9d657c2d32cda47
https://github.com/qemu/qemu/commit/5e1f406424b3a67e8d540e99d9d657c2d32cda47
Author: Geoffrey Thomas <[email protected]>
Date: 2025-07-13 (Sun, 13 Jul 2025)
Changed paths:
M linux-user/fd-trans.h
M linux-user/main.c
Log Message:
-----------
linux-user: Hold the fd-trans lock across fork
If another thread is holding target_fd_trans_lock during a fork,
then the lock becomes permanently locked in the child and the
emulator deadlocks at the next interaction with the fd-trans table.
As with other locks, acquire the lock in fork_start() and release
it in fork_end().
Cc: [email protected]
Signed-off-by: Geoffrey Thomas <[email protected]>
Fixes: c093364f4d91 "fd-trans: Fix race condition on reallocation of the
translation table."
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2846
Buglink: https://github.com/astral-sh/uv/issues/6105
Reviewed-by: Richard Henderson <[email protected]>
Signed-off-by: Richard Henderson <[email protected]>
Message-ID: <[email protected]>
(cherry picked from commit e4e839b2eeea5745c48ce47144c7842eb7cd455f)
(Mjt: adjust context in linux/main.c for 7.2)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: 94ab5f6743b6d56f8ff6366ebde42e62e93b517d
https://github.com/qemu/qemu/commit/94ab5f6743b6d56f8ff6366ebde42e62e93b517d
Author: Chaney, Ben <[email protected]>
Date: 2025-07-13 (Sun, 13 Jul 2025)
Changed paths:
M migration/ram.c
Log Message:
-----------
migration: Don't sync volatile memory after migration completes
Syncing volatile memory provides no benefit, instead it can cause
performance issues in some cases. Only sync memory that is marked as
non-volatile after migration completes on destination.
Signed-off-by: Ben Chaney <[email protected]>
Fixes: bd108a44bc29 (migration: ram: Switch to ram block writeback)
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
(cherry picked from commit 983899eab4939dc4dff67fa4d822c5b4df7eae21)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: cd4ac461e161ba794cef048f4796de84c62ae25b
https://github.com/qemu/qemu/commit/cd4ac461e161ba794cef048f4796de84c62ae25b
Author: Alejandro Jimenez <[email protected]>
Date: 2025-07-16 (Wed, 16 Jul 2025)
Changed paths:
M hw/i386/amd_iommu.h
Log Message:
-----------
amd_iommu: Fix Miscellaneous Information Register 0 encoding
The definitions encoding the maximum Virtual, Physical, and Guest Virtual
Address sizes supported by the IOMMU are using incorrect offsets i.e. the
VASize and GVASize offsets are switched. The value in the GVAsize field is
also modified, since it was incorrectly encoded.
Cc: [email protected]
Fixes: d29a09ca6842 ("hw/i386: Introduce AMD IOMMU")
Co-developed-by: Ethan MILON <[email protected]>
Signed-off-by: Ethan MILON <[email protected]>
Signed-off-by: Alejandro Jimenez <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Vasant Hegde <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
(cherry picked from commit 091c7d7924f33781c2fb8e7297dc54971e0c3785)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: 4002ea511dcb39efdc2aad0b6f9e85c5e6e4c390
https://github.com/qemu/qemu/commit/4002ea511dcb39efdc2aad0b6f9e85c5e6e4c390
Author: Alejandro Jimenez <[email protected]>
Date: 2025-07-16 (Wed, 16 Jul 2025)
Changed paths:
M hw/i386/amd_iommu.c
Log Message:
-----------
amd_iommu: Fix Device ID decoding for INVALIDATE_IOTLB_PAGES command
The DeviceID bits are extracted using an incorrect offset in the call to
amdvi_iotlb_remove_page(). This field is read (correctly) earlier, so use
the value already retrieved for devid.
Cc: [email protected]
Fixes: d29a09ca6842 ("hw/i386: Introduce AMD IOMMU")
Signed-off-by: Alejandro Jimenez <[email protected]>
Reviewed-by: Vasant Hegde <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
(cherry picked from commit c63b8d1425ba8b3b08ee4f7346457fd8a7f12a24)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: c309fddb3af8b4f0a234fa51eb022dc86d23c371
https://github.com/qemu/qemu/commit/c309fddb3af8b4f0a234fa51eb022dc86d23c371
Author: Alejandro Jimenez <[email protected]>
Date: 2025-07-16 (Wed, 16 Jul 2025)
Changed paths:
M hw/i386/amd_iommu.c
M hw/i386/amd_iommu.h
Log Message:
-----------
amd_iommu: Update bitmasks representing DTE reserved fields
The DTE validation method verifies that all bits in reserved DTE fields are
unset. Update them according to the latest definition available in AMD I/O
Virtualization Technology (IOMMU) Specification - Section 2.2.2.1 Device
Table Entry Format. Remove the magic numbers and use a macro helper to
generate bitmasks covering the specified ranges for better legibility.
Note that some reserved fields specify that events are generated when they
contain non-zero bits, or checks are skipped under certain configurations.
This change only updates the reserved masks, checks for special conditions
are not yet implemented.
Cc: [email protected]
Signed-off-by: Alejandro Jimenez <[email protected]>
Reviewed-by: Vasant Hegde <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
(cherry picked from commit ff3dcb3bf652912466dcc1cd10d3267f185c212e)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: 7d8c916b772dead117c9d0aff30db00fa5ae7afe
https://github.com/qemu/qemu/commit/7d8c916b772dead117c9d0aff30db00fa5ae7afe
Author: Alejandro Jimenez <[email protected]>
Date: 2025-07-16 (Wed, 16 Jul 2025)
Changed paths:
M hw/i386/amd_iommu.h
Log Message:
-----------
amd_iommu: Fix masks for various IOMMU MMIO Registers
Address various issues with definitions of the MMIO registers e.g. for the
Device Table Address Register, the size mask currently encompasses reserved
bits [11:9], so change it to only extract the bits [8:0] encoding size.
Convert masks to use GENMASK64 for consistency, and make unrelated
definitions independent.
Cc: [email protected]
Fixes: d29a09ca6842 ("hw/i386: Introduce AMD IOMMU")
Signed-off-by: Alejandro Jimenez <[email protected]>
Reviewed-by: Vasant Hegde <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
(cherry picked from commit 108e10ff69099c3ebe147f505246be7c2ad2a499)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: dc0191c7c13f1151c65834259cba85a12d5ac69f
https://github.com/qemu/qemu/commit/dc0191c7c13f1151c65834259cba85a12d5ac69f
Author: Alejandro Jimenez <[email protected]>
Date: 2025-07-16 (Wed, 16 Jul 2025)
Changed paths:
M hw/i386/amd_iommu.h
Log Message:
-----------
amd_iommu: Fix mask to retrieve Interrupt Table Root Pointer from DTE
Fix an off-by-one error in the definition of AMDVI_IR_PHYS_ADDR_MASK. The
current definition masks off the most significant bit of the Interrupt Table
Root ptr i.e. it only generates a mask with bits [50:6] set. See the AMD I/O
Virtualization Technology (IOMMU) Specification for the Interrupt Table
Root Pointer[51:6] field in the Device Table Entry format.
Cc: [email protected]
Fixes: b44159fe0078 ("x86_iommu/amd: Add interrupt remap support when VAPIC is
not enabled")
Signed-off-by: Alejandro Jimenez <[email protected]>
Reviewed-by: Vasant Hegde <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
(cherry picked from commit 123cf4bdd378f746dfa2f5415ba084148dded3e3)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: 452a0cb27bf8a2c3aa98e28c24fbce12c1034fb0
https://github.com/qemu/qemu/commit/452a0cb27bf8a2c3aa98e28c24fbce12c1034fb0
Author: Alejandro Jimenez <[email protected]>
Date: 2025-07-16 (Wed, 16 Jul 2025)
Changed paths:
M hw/i386/amd_iommu.c
Log Message:
-----------
amd_iommu: Fix the calculation for Device Table size
Correctly calculate the Device Table size using the format encoded in the
Device Table Base Address Register (MMIO Offset 0000h).
Cc: [email protected]
Fixes: d29a09ca6842 ("hw/i386: Introduce AMD IOMMU")
Signed-off-by: Alejandro Jimenez <[email protected]>
Reviewed-by: Vasant Hegde <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
(cherry picked from commit 67d3077ee403472d45794399e97c9f329242fce9)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: cae7315f45ae6662e193e7126959e775a6d49040
https://github.com/qemu/qemu/commit/cae7315f45ae6662e193e7126959e775a6d49040
Author: Alejandro Jimenez <[email protected]>
Date: 2025-07-16 (Wed, 16 Jul 2025)
Changed paths:
M hw/i386/amd_iommu.h
Log Message:
-----------
amd_iommu: Remove duplicated definitions
No functional change.
Signed-off-by: Alejandro Jimenez <[email protected]>
Reviewed-by: Vasant Hegde <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
(cherry picked from commit 5959b641c98b5ae9677e2c1d89902dac31b344d9)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: 385eb77f6051d265322782a6f53a89bca9967d61
https://github.com/qemu/qemu/commit/385eb77f6051d265322782a6f53a89bca9967d61
Author: Ethan Milon <[email protected]>
Date: 2025-07-16 (Wed, 16 Jul 2025)
Changed paths:
M hw/i386/amd_iommu.c
Log Message:
-----------
amd_iommu: Fix truncation of oldval in amdvi_writeq
The variable `oldval` was incorrectly declared as a 32-bit `uint32_t`.
This could lead to truncation and incorrect behavior where the upper
read-only 32 bits are significant.
Fix the type of `oldval` to match the return type of `ldq_le_p()`.
Cc: [email protected]
Fixes: d29a09ca6842 ("hw/i386: Introduce AMD IOMMU")
Signed-off-by: Ethan Milon <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Vasant Hegde <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
(cherry picked from commit 5788929e05e18ed5f76dc8ade4210f022c9ba5a1)
Signed-off-by: Michael Tokarev <[email protected]>
Commit: 196137c1c6653adf6a49889814fe1d209d937861
https://github.com/qemu/qemu/commit/196137c1c6653adf6a49889814fe1d209d937861
Author: Akihiko Odaki <[email protected]>
Date: 2025-07-16 (Wed, 16 Jul 2025)
Changed paths:
M ui/vnc-enc-zlib.c
M ui/vnc.c
M ui/vnc.h
Log Message:
-----------
ui/vnc: Do not copy z_stream
vnc_worker_thread_loop() copies z_stream stored in its local VncState to
the persistent VncState, and the copied one is freed with deflateEnd()
later. However, deflateEnd() refuses to operate with a copied z_stream
and returns Z_STREAM_ERROR, leaking the allocated memory.
Avoid copying the zlib state to fix the memory leak.
Fixes: bd023f953e5e ("vnc: threaded VNC server")
Signed-off-by: Akihiko Odaki <[email protected]>
Reviewed-by: Marc-André Lureau <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Message-Id: <[email protected]>
(cherry picked from commit aef22331b5a4670f42638a5f63a26e93bf779aae)
Signed-off-by: Michael Tokarev <[email protected]>
Compare: https://github.com/qemu/qemu/compare/1aa8057181ba...196137c1c665
To unsubscribe from these emails, change your notification settings at
https://github.com/qemu/qemu/settings/notifications
