Branch: refs/heads/staging
Home: https://github.com/qemu/qemu
Commit: 76cfb87f5fcad4008359e44bf37508c265da1221
https://github.com/qemu/qemu/commit/76cfb87f5fcad4008359e44bf37508c265da1221
Author: Steve Sistare <steven.sist...@oracle.com>
Date: 2025-08-09 (Sat, 09 Aug 2025)
Changed paths:
M hw/vfio/cpr.c
M hw/vfio/pci.c
M hw/vfio/pci.h
Log Message:
-----------
vfio/pci: augment set_handler
Extend vfio_pci_msi_set_handler() so it can set or clear the handler.
Add a similar accessor for INTx. No functional change.
Signed-off-by: Steve Sistare <steven.sist...@oracle.com>
Reviewed-by: Cédric Le Goater <c...@redhat.com>
Link:
https://lore.kernel.org/qemu-devel/1752689169-233452-2-git-send-email-steven.sist...@oracle.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 322ee16824dc3d301477812a5dacb0249e1efe8c
https://github.com/qemu/qemu/commit/322ee16824dc3d301477812a5dacb0249e1efe8c
Author: Steve Sistare <steven.sist...@oracle.com>
Date: 2025-08-09 (Sat, 09 Aug 2025)
Changed paths:
M hw/vfio/cpr.c
M hw/vfio/pci.c
M hw/vfio/pci.h
M include/hw/vfio/vfio-cpr.h
Log Message:
-----------
vfio/pci: preserve pending interrupts
cpr-transfer may lose a VFIO interrupt because the KVM instance is
destroyed and recreated. If an interrupt arrives in the middle, it is
dropped. To fix, stop pending new interrupts during cpr save, and pick
up the pieces. In more detail:
Stop the VCPUs. Call kvm_irqchip_remove_irqfd_notifier_gsi --> KVM_IRQFD to
deassign the irqfd gsi that routes interrupts directly to the VCPU and KVM.
After this call, interrupts fall back to the kernel vfio_msihandler, which
writes to QEMU's kvm_interrupt eventfd. CPR already preserves that
eventfd. When the route is re-established in new QEMU, the kernel tests
the eventfd and injects an interrupt to KVM if necessary.
Deassign INTx in a similar manner. For both MSI and INTx, remove the
eventfd handler so old QEMU does not consume an event.
If an interrupt was already pended to KVM prior to the completion of
kvm_irqchip_remove_irqfd_notifier_gsi, it will be recovered by the
subsequent call to cpu_synchronize_all_states, which pulls KVM interrupt
state to userland prior to saving it in vmstate.
Signed-off-by: Steve Sistare <steven.sist...@oracle.com>
Reviewed-by: Zhenzhong Duan <zhenzhong.d...@intel.com>
Link:
https://lore.kernel.org/qemu-devel/1752689169-233452-3-git-send-email-steven.sist...@oracle.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: d9f4b45713e4e000a42ed1f33cb06b806173b559
https://github.com/qemu/qemu/commit/d9f4b45713e4e000a42ed1f33cb06b806173b559
Author: Cédric Le Goater <c...@redhat.com>
Date: 2025-08-09 (Sat, 09 Aug 2025)
Changed paths:
M hw/vfio/pci.c
Log Message:
-----------
vfio: Document 'use-legacy-x86-rom' property
Commit 350785d41d8b ("ramfb: Add property to control if load the
romfile") introduced the `use-legacy-x86-rom` property for the
`vfio-pci-nohotplug` device. Add documentation for the property.
Fixes: d5fcf0d960d8 ("hw/i386: Add the ramfb romfile compatibility")
Reviewed-by: Philippe Mathieu-Daudé <phi...@linaro.org>
Link: https://lore.kernel.org/qemu-devel/20250805065543.120091-1-...@redhat.com
Signed-off-by: Cédric Le Goater <c...@redhat.com>
Commit: 31b737b19dca4d50758f5e9834d27b683102f2f1
https://github.com/qemu/qemu/commit/31b737b19dca4d50758f5e9834d27b683102f2f1
Author: Klaus Jensen <k.jen...@samsung.com>
Date: 2025-08-11 (Mon, 11 Aug 2025)
Changed paths:
M hw/nvme/ctrl.c
Log Message:
-----------
hw/nvme: fix namespace attachment
Commit 6ccca4b6bb9f ("hw/nvme: rework csi handling") introduced a bug in
Namespace Attachment, causing it to
a) not allow a controller to attach namespaces to other controllers
b) assert if a valid non-attached namespace is detached
This fixes both issues.
Fixes: 6ccca4b6bb9f ("hw/nvme: rework csi handling")
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2976
Reviewed-by: Jesper Wendel Devantier <f...@defmacro.it>
Signed-off-by: Klaus Jensen <k.jen...@samsung.com>
Commit: bc0c24fdb157b014932a5012fe4ccbeba7617f17
https://github.com/qemu/qemu/commit/bc0c24fdb157b014932a5012fe4ccbeba7617f17
Author: Klaus Jensen <k.jen...@samsung.com>
Date: 2025-08-11 (Mon, 11 Aug 2025)
Changed paths:
M hw/nvme/ctrl.c
Log Message:
-----------
hw/nvme: revert CMIC behavior
Commit cd59f50ab017 ("hw/nvme: always initialize a subsystem") causes
the controller to always set the CMIC.MCTRS ("Multiple Controllers")
bit. While spec-compliant, this is a deviation from the previous
behavior where this was only set if an nvme-subsys device was explicitly
created (to configure a subsystem with multiple controllers/namespaces).
Revert the behavior to only set CMIC.MCTRS if an nvme-subsys device is
created explicitly.
Reported-by: Alan Adamson <alan.adam...@oracle.com>
Fixes: cd59f50ab017 ("hw/nvme: always initialize a subsystem")
Reviewed-by: Alan Adamson <alan.adam...@oracle.com>
Tested-by: Alan Adamson <alan.adam...@oracle.com>
Signed-off-by: Klaus Jensen <k.jen...@samsung.com>
Commit: 53493c1f836f4dda90a6b5f2fb3d9264918c6871
https://github.com/qemu/qemu/commit/53493c1f836f4dda90a6b5f2fb3d9264918c6871
Author: Keith Busch <kbu...@kernel.org>
Date: 2025-08-11 (Mon, 11 Aug 2025)
Changed paths:
M hw/nvme/ctrl.c
Log Message:
-----------
hw/nvme: cap MDTS value for internal limitation
The emulated device had let the user set whatever max transfers size
they wanted, including no limit. However the device does have an
internal limit of 1024 segments. NVMe doesn't report max segments,
though. This is implicitly inferred based on the MDTS and MPSMIN values.
IOV_MAX is currently 1024 which 4k PRPs can exceed with 2MB transfers.
Don't allow MDTS values that can exceed this, otherwise users risk
seeing "internal error" status to their otherwise protocol compliant
commands.
Signed-off-by: Keith Busch <kbu...@kernel.org>
Signed-off-by: Klaus Jensen <k.jen...@samsung.com>
Commit: 621dbaee0152a283042db3cac6a51f91b3e06024
https://github.com/qemu/qemu/commit/621dbaee0152a283042db3cac6a51f91b3e06024
Author: Stefan Hajnoczi <stefa...@redhat.com>
Date: 2025-08-11 (Mon, 11 Aug 2025)
Changed paths:
M tests/functional/test_aarch64_hotplug_pci.py
Log Message:
-----------
tests/functional: fix URLs in PCI hotplug test for aarch64
Debian trixie has been released. The "stable" alias no longer refers to
the Debian bookworm release, so URLs referring to bookworm artifacts via
the "stable" alias no longer work.
Switch to explicit release naming ("bookworm") to make a permalink so
the test passes again.
Suggested-by: Peter Maydell <peter.mayd...@linaro.org>
Fixes: 374a245573b8 ("tests/functional: Add PCI hotplug test for aarch64")
Resolves: #3073 ("PCI hotplug test for aarch64 fails due to broken Debian
installer URL")
Reviewed-by: Alex Bennée <alex.ben...@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <phi...@linaro.org>
Tested-by: Philippe Mathieu-Daudé <phi...@linaro.org>
Reviewed-by: Peter Maydell <peter.mayd...@linaro.org>
Message-ID: <20250811162315.59997-1-stefa...@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com>
Commit: 21901731410305f66e44f3437c5306cd77b93d95
https://github.com/qemu/qemu/commit/21901731410305f66e44f3437c5306cd77b93d95
Author: Stefan Hajnoczi <stefa...@redhat.com>
Date: 2025-08-11 (Mon, 11 Aug 2025)
Changed paths:
M hw/vfio/cpr.c
M hw/vfio/pci.c
M hw/vfio/pci.h
M include/hw/vfio/vfio-cpr.h
Log Message:
-----------
Merge tag 'pull-vfio-20250810' of https://github.com/legoater/qemu into
staging
vfio queue:
* Add documentation for the use-legacy-x86-rom property
* Preserve pending VFIO interrupts during CPR
# -----BEGIN PGP SIGNATURE-----
#
# iQIzBAABCAAdFiEEoPZlSPBIlev+awtgUaNDx8/77KEFAmiYwgkACgkQUaNDx8/7
# 7KH5ew//ThaCgYlT2KwwJFfNUw290uQuvZAZUCB0vx+zhsQzQW5vzAx6KvFO+UQu
# k64BQLk8OV97tDpsEcnZEUoPfLo/05mxlcSKYfG3rTpp+ZxoCXUBhQ9f0ZR9t2gz
# WihHrA+g/r69VlcW9fCdar/n2svvysmY2OzybSAILplmJlk5CsJRB4cbpy09AR70
# t70bWGl+4+voENeVQjdYa35588bjwTdnzpOqy7fbFacs6L17NzaW30lJ8S8AWX8W
# a84nnuJgL2qkR73EvY1wL10EyqqR6gYCsbE39ARf4GoC8UE0cRp7tSXm/xkFd6U1
# I6Wv/7zx9FkKq51b8GB9n8NfW9U3XTTfJSS6QR6GYU77zcukUj06Fr5PNLEg9yOf
# 9dfrPt6pap1vx4xuoq9IqrwOVcKd9e9vi9hARLonlzcLMXZqJnKr3KcelcCcF8El
# Sf994H1izHjr1PqpKCDn7dDJ5Bp7CkvnR9RSCzRssovDzfRBmSI5iC75vpjcEd9z
# zMpKG1auyamlpjyFIBOw3rlMXSkv4vk0wmjv/P5aQxKTlu0Oyyp4dZMPl7C4Grut
# WmXJao6zrcUsxvxf2pi2aELGKzLow240Xh4oceD+dDyLQ6Z25J5aj/4MUWxXbbUT
# YffunKYQ00Bk5+x0gp7tiitNu9s4Z2ezshqebweBxNGHWMiJ5sI=
# =lM1W
# -----END PGP SIGNATURE-----
# gpg: Signature made Sun 10 Aug 2025 12:00:09 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-vfio-20250810' of https://github.com/legoater/qemu:
vfio: Document 'use-legacy-x86-rom' property
vfio/pci: preserve pending interrupts
vfio/pci: augment set_handler
Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com>
Commit: 624d7463043c120facfab2b54985fcfb679d5379
https://github.com/qemu/qemu/commit/624d7463043c120facfab2b54985fcfb679d5379
Author: Stefan Hajnoczi <stefa...@redhat.com>
Date: 2025-08-11 (Mon, 11 Aug 2025)
Changed paths:
M hw/nvme/ctrl.c
Log Message:
-----------
Merge tag 'pull-nvme-20250811' of https://gitlab.com/birkelund/qemu into
staging
nvme queue
# -----BEGIN PGP SIGNATURE-----
#
# iQEzBAABCgAdFiEEUigzqnXi3OaiR2bATeGvMW1PDekFAmiZmYQACgkQTeGvMW1P
# DenI0wf9GPov0a82A2F23UTU+R8NC/NASBovEfPRTz7/J9fGL844ID3G6uT4emFP
# wAilGmMbNuPHKAtII4holCximP/7yosVZJIIdjLsRBBP9AZqpMHkr27VBny9rklZ
# X7TW6zI8INIjdqvRlIBevH5t5By/qLiaDc6GzRWJ3PoeXE6SKACDi0lNBsn75xah
# IbcHi72c96CwYJCEtOHXBs+zECo1yGDhK0OPvs/s7OykuRcOumF21IzuY958bVs/
# 7dJZkTL+oarZHIvKiUrErKK3gWfSrLeaWrR6sW1QNuOhzEeNHk47w86p+CEQ7CrU
# w0ioEaZ9awXk7wnZeY//CpUKFbsmwQ==
# =Qfvu
# -----END PGP SIGNATURE-----
# gpg: Signature made Mon 11 Aug 2025 03:19:32 EDT
# gpg: using RSA key 522833AA75E2DCE6A24766C04DE1AF316D4F0DE9
# gpg: Good signature from "Klaus Jensen <i...@irrelevant.dk>" [unknown]
# gpg: aka "Klaus Jensen <k.jen...@samsung.com>" [unknown]
# gpg: WARNING: This key is not certified with a trusted signature!
# gpg: There is no indication that the signature belongs to the owner.
# Primary key fingerprint: DDCA 4D9C 9EF9 31CC 3468 4272 63D5 6FC5 E55D A838
# Subkey fingerprint: 5228 33AA 75E2 DCE6 A247 66C0 4DE1 AF31 6D4F 0DE9
* tag 'pull-nvme-20250811' of https://gitlab.com/birkelund/qemu:
hw/nvme: cap MDTS value for internal limitation
hw/nvme: revert CMIC behavior
hw/nvme: fix namespace attachment
Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com>
Compare: https://github.com/qemu/qemu/compare/4f50fa9391bb...624d7463043c
To unsubscribe from these emails, change your notification settings at
https://github.com/qemu/qemu/settings/notifications
