Branch: refs/heads/master
Home: https://github.com/qemu/qemu
Commit: 6f9a1a01433738811c9795dcf29f299c60835558
https://github.com/qemu/qemu/commit/6f9a1a01433738811c9795dcf29f299c60835558
Author: Thomas Huth <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M docs/about/deprecated.rst
M docs/about/removed-features.rst
Log Message:
-----------
docs/about: Change notes on x86 machine type deprecation into a general one
We now have a general note about versioned machine types getting
deprecated and removed at the beginning of the deprecated.rst file,
so we should also have a general note about this in removed-features.rst
(which will also apply to versioned non-x86 machine types) instead of
listing individual old machine types in the document.
Signed-off-by: Thomas Huth <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Zhao Liu <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: bc82af6b0dcb0933e72640851fdd2594f822b23e
https://github.com/qemu/qemu/commit/bc82af6b0dcb0933e72640851fdd2594f822b23e
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M hw/net/virtio-net.c
Log Message:
-----------
hw/net: Fix NULL dereference with software RSS
When an eBPF program cannot be attached, virtio_net_load_ebpf() returns
false, and virtio_net_device_realize() enters the code path to handle
errors because of this, but it causes NULL dereference because no error
is generated.
Change virtio_net_load_ebpf() to return false only when a fatal error
occurred.
Fixes: b5900dff14e5 ("hw/net: report errors from failing to use eBPF RSS FDs")
Signed-off-by: Akihiko Odaki <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 5731b005246297ab5b91975f52fcd525e08507cd
https://github.com/qemu/qemu/commit/5731b005246297ab5b91975f52fcd525e08507cd
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M hw/ppc/spapr_pci.c
Log Message:
-----------
hw/ppc/spapr_pci: Do not create DT for disabled PCI device
Disabled means it is a disabled SR-IOV VF and hidden from the guest.
Do not create DT when starting the system and also keep the disabled PCI
device not linked to DRC, which generates DT in case of hotplug.
Signed-off-by: Akihiko Odaki <[email protected]>
Reviewed-by: Shivaprasad G Bhat<[email protected]>
Tested-by: Shivaprasad G Bhat<[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 3bc31441ba31c94f12b7b96b1960abb4c1f21ee8
https://github.com/qemu/qemu/commit/3bc31441ba31c94f12b7b96b1960abb4c1f21ee8
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M hw/ppc/spapr_pci.c
Log Message:
-----------
hw/ppc/spapr_pci: Do not reject VFs created after a PF
A PF may automatically create VFs and the PF may be function 0.
Signed-off-by: Akihiko Odaki <[email protected]>
Reviewed-by: Shivaprasad G Bhat <[email protected]>
Tested-by: Shivaprasad G Bhat <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: b77a2778d9bbefc6119331ce3083d85d69d7a0c1
https://github.com/qemu/qemu/commit/b77a2778d9bbefc6119331ce3083d85d69d7a0c1
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M hw/s390x/s390-pci-bus.c
Log Message:
-----------
s390x/pci: Avoid creating zpci for VFs
VFs are automatically created by PF, and creating zpci for them will
result in unexpected usage of fids. Currently QEMU does not support
multifunction for s390x so we don't need zpci for VFs anyway.
Signed-off-by: Akihiko Odaki <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: d966250e93c1194c0a4c775e08a8e23f2ef66cf8
https://github.com/qemu/qemu/commit/d966250e93c1194c0a4c775e08a8e23f2ef66cf8
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M hw/s390x/s390-pci-bus.c
Log Message:
-----------
s390x/pci: Allow plugging SR-IOV devices
The guest cannot use VFs due to the lack of multifunction support but
can use PFs.
Signed-off-by: Akihiko Odaki <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 2c968f465392316d09e44f4a9f7e378999e5c011
https://github.com/qemu/qemu/commit/2c968f465392316d09e44f4a9f7e378999e5c011
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M hw/s390x/s390-pci-bus.c
Log Message:
-----------
s390x/pci: Check for multifunction after device realization
The SR-IOV PFs set the multifunction bit during device realization so
check them after that. There is no functional change because we
explicitly ignore the multifunction bit for SR-IOV devices.
Signed-off-by: Akihiko Odaki <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: e8b827ce7c4bf9a334c46282779f234d1a011cd1
https://github.com/qemu/qemu/commit/e8b827ce7c4bf9a334c46282779f234d1a011cd1
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M hw/pci/pcie_sriov.c
Log Message:
-----------
pcie_sriov: Do not manually unrealize
A device gets automatically unrealized when being unparented.
Signed-off-by: Akihiko Odaki <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Commit: 3391d68e906114c364c173c7f3f7389d47d15a11
https://github.com/qemu/qemu/commit/3391d68e906114c364c173c7f3f7389d47d15a11
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M docs/pcie_sriov.txt
M hw/net/igb.c
M hw/nvme/ctrl.c
M hw/pci/pcie_sriov.c
M include/hw/pci/pcie_sriov.h
Log Message:
-----------
pcie_sriov: Ensure VF addr does not overflow
pci_new() aborts when creating a VF with addr >= PCI_DEVFN_MAX.
Signed-off-by: Akihiko Odaki <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: cab1398a60eb0cb2d2d1998c9b46aaa5e0bf3ee8
https://github.com/qemu/qemu/commit/cab1398a60eb0cb2d2d1998c9b46aaa5e0bf3ee8
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M hw/pci/pci.c
M hw/pci/pcie_sriov.c
M include/hw/pci/pcie_sriov.h
Log Message:
-----------
pcie_sriov: Reuse SR-IOV VF device instances
Disable SR-IOV VF devices by reusing code to power down PCI devices
instead of removing them when the guest requests to disable VFs. This
allows to realize devices and report VF realization errors at PF
realization time.
Signed-off-by: Akihiko Odaki <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: b85901e728d048c931d110bfd5ff8f119cc97df7
https://github.com/qemu/qemu/commit/b85901e728d048c931d110bfd5ff8f119cc97df7
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M hw/pci/pcie_sriov.c
Log Message:
-----------
pcie_sriov: Release VFs failed to realize
Release VFs failed to realize just as we do in unregister_vfs().
Fixes: 7c0fa8dff811 ("pcie: Add support for Single Root I/O Virtualization
(SR/IOV)")
Signed-off-by: Akihiko Odaki <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 5e7dd17e43486f41d4f88dbefd7219f0524f424c
https://github.com/qemu/qemu/commit/5e7dd17e43486f41d4f88dbefd7219f0524f424c
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M hw/pci/pcie_sriov.c
M hw/pci/trace-events
M include/hw/pci/pcie_sriov.h
Log Message:
-----------
pcie_sriov: Remove num_vfs from PCIESriovPF
num_vfs is not migrated so use PCI_SRIOV_CTRL_VFE and PCI_SRIOV_NUM_VF
instead.
Signed-off-by: Akihiko Odaki <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: f9efcd47110de43dd841ada5bd1a40ec169eabca
https://github.com/qemu/qemu/commit/f9efcd47110de43dd841ada5bd1a40ec169eabca
Author: Akihiko Odaki <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M hw/pci/pci.c
M hw/pci/pcie_sriov.c
M include/hw/pci/pcie_sriov.h
Log Message:
-----------
pcie_sriov: Register VFs after migration
pcie_sriov doesn't have code to restore its state after migration, but
igb, which uses pcie_sriov, naively claimed its migration capability.
Add code to register VFs after migration and fix igb migration.
Fixes: 3a977deebe6b ("Intrdocue igb device emulation")
Signed-off-by: Akihiko Odaki <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 9e837c961a883392f8c4707a8d3d2e6c6aa793b6
https://github.com/qemu/qemu/commit/9e837c961a883392f8c4707a8d3d2e6c6aa793b6
Author: Nicholas Piggin <[email protected]>
Date: 2025-02-20 (Thu, 20 Feb 2025)
Changed paths:
M tests/qtest/libqos/pci.c
Log Message:
-----------
qtest/libqos/pci: Do not write to PBA memory
The PCI Local Bus Specification says the result of writes to MSI-X
PBA memory is undefined. QEMU implements them as no-ops, so remove
the pointless write from qpci_msix_pending().
Signed-off-by: Nicholas Piggin <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Akihiko Odaki <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 44ed44aefec571041fe3b3a8b6849613a74b520a
https://github.com/qemu/qemu/commit/44ed44aefec571041fe3b3a8b6849613a74b520a
Author: Nicholas Piggin <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/pci/msix.c
Log Message:
-----------
hw/pci/msix: Warn on PBA writes
Of the MSI-X PBA pending bits, the PCI Local Bus Specification says:
Software should never write, and should only read
Pending Bits. If software writes to Pending Bits, the
result is undefined.
Log a GUEST_ERROR message if the PBA is written to by software.
Cc: Marcel Apfelbaum <[email protected]>
Cc: Dmitry Fleytman <[email protected]>
Cc: Sriram Yagnaraman <[email protected]>
Signed-off-by: Nicholas Piggin <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Phil Dennis-Jordan <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Reviewed-by: Akihiko Odaki <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: f6fc01c7866639649b9af58ad50a7367b2d18eae
https://github.com/qemu/qemu/commit/f6fc01c7866639649b9af58ad50a7367b2d18eae
Author: Nicholas Piggin <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/pci/pci.c
Log Message:
-----------
hw/pci: Assert a bar is not registered multiple times
Nothing should be doing this, but it doesn't get caught by
pci_register_bar(). Add an assertion to prevent misuse.
Signed-off-by: Nicholas Piggin <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Phil Dennis-Jordan <[email protected]>
Signed-off-by: Nicholas Piggin <[email protected]>
Reviewed-by: Phil Dennis-Jordan <[email protected]>
Reviewed-by: Akihiko Odaki <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: de538288e4dac21332cc94ba9727ed8ec8fe5ea1
https://github.com/qemu/qemu/commit/de538288e4dac21332cc94ba9727ed8ec8fe5ea1
Author: Thomas Huth <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/i386/pc.c
Log Message:
-----------
hw/i386/pc: Fix crash that occurs when introspecting TYPE_PC_MACHINE machines
QEMU currently crashes when you try to inspect the machines based on
TYPE_PC_MACHINE for their properties:
$ echo '{ "execute": "qmp_capabilities" }
{ "execute": "qom-list-properties","arguments":
{ "typename": "pc-q35-10.0-machine"}}' \
| ./qemu-system-x86_64 -M pc -qmp stdio
{"QMP": {"version": {"qemu": {"micro": 50, "minor": 2, "major": 9},
"package": "v9.2.0-1070-g87e115c122-dirty"}, "capabilities": ["oob"]}}
{"return": {}}
Segmentation fault (core dumped)
This happens because TYPE_PC_MACHINE machines add a machine_init-
done_notifier in their instance_init function - but instance_init
of machines are not only called for machines that are realized,
but also for machines that are introspected, so in this case the
listener is added for a q35 machine that is never realized. But
since there is already a running pc machine, the listener function
is triggered immediately, causing a crash since it was not for the
right machine it was meant for.
Such listener functions must never be installed from an instance_init
function. Let's do it from pc_basic_device_init() instead - this
function is called from the MachineClass->init() function instead,
i.e. guaranteed to be only called once in the lifetime of a QEMU
process.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2779
Signed-off-by: Thomas Huth <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Akihiko Odaki <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 38ef383073b8ee59d598643160f206a19a46237f
https://github.com/qemu/qemu/commit/38ef383073b8ee59d598643160f206a19a46237f
Author: Thomas Huth <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/i386/microvm.c
Log Message:
-----------
hw/i386/microvm: Fix crash that occurs when introspecting the microvm machine
QEMU currently crashes when you try to inspect the properties of the
microvm machine:
$ echo '{ "execute": "qmp_capabilities" }
{ "execute": "qom-list-properties","arguments":
{ "typename": "microvm-machine"}}' | \
./qemu-system-x86_64 -qmp stdio
{"QMP": {"version": {"qemu": {"micro": 50, "minor": 2, "major": 9},
"package": "v9.2.0-1072-g60af367187-dirty"}, "capabilities": ["oob"]}}
{"return": {}}
qemu-system-x86_64: ../qemu/hw/i386/acpi-microvm.c:250:
void acpi_setup_microvm(MicrovmMachineState *):
Assertion `x86ms->fw_cfg' failed.
Aborted (core dumped)
This happens because the microvm machine adds a machine_done (and a
powerdown_req) notifier in their instance_init function - however, the
instance_init of machines are not only called for machines that are
realized, but also for machines that are introspected, so in this case
the listener is added for a microvm machine that is never realized. And
since there is already a running machine, the listener function is
triggered immediately, causing a crash since it was not for the right
machine it was meant for.
Such listener functions must never be installed from an instance_init
function. Let's do it from microvm_machine_state_init() instead - this
function is the MachineClass->init() function instead, i.e. guaranteed
to be only called once in the lifetime of a QEMU process.
Since the microvm_machine_done() and microvm_powerdown_req() were
defined quite late in the microvm.c file, we have to move them now
also earlier, so that we can get their function pointers from
microvm_machine_state_init() without having to introduce a separate
prototype for those functions earlier.
Reviewed-by: Sergio Lopez <[email protected]>
Signed-off-by: Thomas Huth <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Akihiko Odaki <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 14998e50c3638b07946ebe5972a327cc26e9f03c
https://github.com/qemu/qemu/commit/14998e50c3638b07946ebe5972a327cc26e9f03c
Author: Thomas Huth <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M tests/qtest/vhost-user-test.c
Log Message:
-----------
tests/qtest/vhost-user-test: Use modern virtio for vhost-user tests
All other vhost-user tests here use modern virtio, too, so let's
adjust the vhost-user-net test accordingly.
Signed-off-by: Thomas Huth <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Reviewed-by: Stefano Garzarella <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 8f90a54cfafe8c93a71930a96a63ccbd074f4142
https://github.com/qemu/qemu/commit/8f90a54cfafe8c93a71930a96a63ccbd074f4142
Author: Li Zhijian <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/cxl/cxl-device-utils.c
M hw/cxl/switch-mailbox-cci.c
M hw/mem/cxl_type3.c
M include/hw/cxl/cxl_device.h
Log Message:
-----------
hw/cxl: Introduce CXL_T3_MSIX_VECTOR enumeration
Introduce the `CXL_T3_MSIX_VECTOR` enumeration to specify MSIX vector
assignments specific to the Type 3 (T3) CXL device.
The primary goal of this change is to encapsulate the MSIX vector uses
that are unique to the T3 device within an enumeration, improving code
readability and maintenance by avoiding magic numbers. This organizational
change allows for more explicit references to each vector’s role, thereby
reducing the potential for misconfiguration.
It also modified `mailbox_reg_init_common` to accept the `msi_n` parameter,
reflecting the new MSIX vector setup.
This pertains to the T3 device privately; other endpoints should refrain from
using it, despite its public accessibility to all of them.
Signed-off-by: Li Zhijian <[email protected]>
Signed-off-by: Jonathan Cameron <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 0401c4328f4d18be540fd432c2bbacce4531d14f
https://github.com/qemu/qemu/commit/0401c4328f4d18be540fd432c2bbacce4531d14f
Author: Li Zhijian <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/mem/cxl_type3.c
Log Message:
-----------
hw/mem/cxl_type3: Add paired msix_uninit_exclusive_bar() call
msix_uninit_exclusive_bar() should be paired with msix_init_exclusive_bar()
Ensure proper resource cleanup by adding the missing
`msix_uninit_exclusive_bar()` call for the Type3 CXL device.
Signed-off-by: Li Zhijian <[email protected]>
Signed-off-by: Jonathan Cameron <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 06953e7e5ea5e8fa0b7b704bdb66ab1e62f1f378
https://github.com/qemu/qemu/commit/06953e7e5ea5e8fa0b7b704bdb66ab1e62f1f378
Author: Li Zhijian <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/mem/cxl_type3.c
Log Message:
-----------
hw/mem/cxl_type3: Fix special_ops memory leak on msix_init_exclusive_bar()
failure
Address a memory leak issue by ensuring `regs->special_ops` is freed when
`msix_init_exclusive_bar()` encounters an error during CXL Type3 device
initialization.
Additionally, this patch renames err_address_space_free to err_msix_uninit
for better clarity and logical flow
Signed-off-by: Li Zhijian <[email protected]>
Signed-off-by: Jonathan Cameron <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: d3c92cf6dcab028d05f306d4d50511aa805d2385
https://github.com/qemu/qemu/commit/d3c92cf6dcab028d05f306d4d50511aa805d2385
Author: Li Zhijian <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/mem/cxl_type3.c
Log Message:
-----------
hw/mem/cxl_type3: Ensure errp is set on realization failure
Simply pass the errp to its callee which will set errp if needed, to
enhance error reporting for CXL Type 3 device initialization by setting
the errp when realization functions fail.
Previously, failing to set `errp` could result in errors being overlooked,
causing the system to mistakenly treat failure scenarios as successful and
potentially leading to redundant cleanup operations in ct3_exit().
Signed-off-by: Li Zhijian <[email protected]>
Signed-off-by: Jonathan Cameron <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 9ac2c42f43a536f53b3d4cad8a601ccb8640cbd8
https://github.com/qemu/qemu/commit/9ac2c42f43a536f53b3d4cad8a601ccb8640cbd8
Author: Yao Xingtao <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/cxl/cxl-component-utils.c
M hw/mem/cxl_type3.c
Log Message:
-----------
mem/cxl_type3: support 3, 6, 12 and 16 interleave ways
Since the kernel does not check the interleave capability, a
3-way, 6-way, 12-way or 16-way region can be create normally.
Applications can access the memory of 16-way region normally because
qemu can convert hpa to dpa correctly for the power of 2 interleave
ways, after kernel implementing the check, this kind of region will
not be created any more.
For non power of 2 interleave ways, applications could not access the
memory normally and may occur some unexpected behaviors, such as
segmentation fault.
So implements this feature is needed.
Link:
https://lore.kernel.org/linux-cxl/[email protected]/
Signed-off-by: Yao Xingtao <[email protected]>
Signed-off-by: Jonathan Cameron <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 1456e90653c46aceb3dd83a7b9889a32aad7700d
https://github.com/qemu/qemu/commit/1456e90653c46aceb3dd83a7b9889a32aad7700d
Author: Daniel P. Berrangé <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M MAINTAINERS
M hw/virtio/virtio-balloon.c
M include/hw/virtio/virtio-balloon.h
M tests/functional/meson.build
A tests/functional/test_virtio_balloon.py
Log Message:
-----------
hw/virtio: reset virtio balloon stats on machine reset
When a machine is first booted, all virtio balloon stats are initialized
to their default value -1 (18446744073709551615 when represented as
unsigned).
They remain that way while the firmware is loading, and early phase of
guest OS boot, until the virtio-balloon driver is activated. Thereafter
the reported stats reflect the guest OS activity.
When a machine reset is performed, however, the virtio-balloon stats are
left unchanged by QEMU, despite the guest OS no longer updating them,
nor indeed even still existing.
IOW, the mgmt app keeps getting stale stats until the guest OS starts
once more and loads the virtio-balloon driver (if ever). At that point
the app will see a discontinuity in the reported values as they sudden
jump from the stale value to the new value. This jump is indigituishable
from a valid data update.
While there is an "last-updated" field to report on the freshness of
the stats, that does not unambiguously tell the mgmt app whether the
stats are still conceptually relevant to the current running workload.
It is more conceptually useful to reset the stats to their default
values on machine reset, given that the previous guest workload the
stats reflect no longer exists. The mgmt app can now clearly identify
that there are is no stats information available from the current
executing workload.
The 'last-updated' time is also reset back to 0.
IOW, on every machine reset, the virtio stats are in the same clean
state they were when the macine first powered on.
A functional test is added to validate this behaviour with a real
world guest OS.
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Acked-by: David Hildenbrand <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 63dc0b8647391b372f3bb38ff1066f6b4a5e6ea1
https://github.com/qemu/qemu/commit/63dc0b8647391b372f3bb38ff1066f6b4a5e6ea1
Author: Sairaj Kodilkar <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/i386/amd_iommu.c
Log Message:
-----------
amd_iommu: Use correct DTE field for interrupt passthrough
Interrupt passthrough is determine by the bits 191,190,187-184.
These bits are part of the 3rd quad word (i.e. index 2) in DTE. Hence
replace dte[3] by dte[2].
Fixes: b44159fe0 ("x86_iommu/amd: Add interrupt remap support when VAPIC is not
enabled")
Signed-off-by: Sairaj Kodilkar <[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]>
Commit: 3684717b7407cc395dc9bf522e193dbc85293dee
https://github.com/qemu/qemu/commit/3684717b7407cc395dc9bf522e193dbc85293dee
Author: Sairaj Kodilkar <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/i386/amd_iommu.c
M hw/i386/amd_iommu.h
Log Message:
-----------
amd_iommu: Use correct bitmask to set capability BAR
AMD IOMMU provides the base address of control registers through
IVRS table and PCI capability. Since this base address is of 64 bit,
use 32 bits mask (instead of 16 bits) to set BAR low and high.
Fixes: d29a09ca68 ("hw/i386: Introduce AMD IOMMU")
Signed-off-by: Sairaj Kodilkar <[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]>
Commit: 92cf61e70838c20adc82daa3170fdbb9d174b508
https://github.com/qemu/qemu/commit/92cf61e70838c20adc82daa3170fdbb9d174b508
Author: Jonah Palmer <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/virtio/vhost-iova-tree.c
M hw/virtio/vhost-iova-tree.h
M hw/virtio/vhost-vdpa.c
M net/vhost-vdpa.c
Log Message:
-----------
vhost-iova-tree: Implement an IOVA-only tree
Creates and supports an IOVA-only tree to support a SVQ IOVA->HVA and
GPA->IOVA tree for host-only and guest-backed memory, respectively, in
the next patch.
The IOVA allocator still allocates an IOVA range but now adds this range
to the IOVA-only tree as well as to the full IOVA->HVA tree.
In the next patch, the full IOVA->HVA tree will be split into a partial
SVQ IOVA->HVA tree and a GPA->IOVA tree. The motivation behind having an
IOVA-only tree was to have a single tree that would keep track of all
allocated IOVA ranges between the partial SVQ IOVA->HVA and GPA->IOVA
trees.
Signed-off-by: Jonah Palmer <[email protected]>
Acked-by: Eugenio Pérez <[email protected]>
Tested-by: Lei Yang <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 05063f55841babae7216d36105440ed8ba632938
https://github.com/qemu/qemu/commit/05063f55841babae7216d36105440ed8ba632938
Author: Jonah Palmer <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/virtio/vhost-iova-tree.c
M hw/virtio/vhost-iova-tree.h
M hw/virtio/vhost-shadow-virtqueue.c
M hw/virtio/vhost-shadow-virtqueue.h
M hw/virtio/vhost-vdpa.c
M include/qemu/iova-tree.h
M net/vhost-vdpa.c
M util/iova-tree.c
Log Message:
-----------
vhost-iova-tree, svq: Implement GPA->IOVA & partial IOVA->HVA trees
Creates and supports a GPA->IOVA tree and a partial IOVA->HVA tree by
splitting up guest-backed memory maps and host-only memory maps from the
full IOVA->HVA tree. That is, any guest-backed memory maps are now
stored in the GPA->IOVA tree and host-only memory maps stay in the
IOVA->HVA tree.
Also propagates the GPAs (in_addr/out_addr) of a VirtQueueElement to
vhost_svq_translate_addr() to translate GPAs to IOVAs via the GPA->IOVA
tree (when descriptors are backed by guest memory). For descriptors
backed by host-only memory, the existing partial SVQ IOVA->HVA tree is
used.
GPAs are unique in the guest's address space, ensuring unambiguous IOVA
translations. This avoids the issue where different GPAs map to the same
HVA, causing the original HVA->IOVA translation to potentially return an
IOVA associated with the wrong intended GPA.
Signed-off-by: Jonah Palmer <[email protected]>
Acked-by: Eugenio Pérez <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 332859dd597b78f7d1ebfaefd6195e3a2b3e5906
https://github.com/qemu/qemu/commit/332859dd597b78f7d1ebfaefd6195e3a2b3e5906
Author: Jonah Palmer <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/virtio/vhost-iova-tree.c
Log Message:
-----------
vhost-iova-tree: Update documentation
Minor update to some of the documentation / comments in
hw/virtio/vhost-iova-tree.c.
Signed-off-by: Jonah Palmer <[email protected]>
Reviewed-by: Eugenio Pérez <[email protected]>
Tested-by: Lei Yang <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 83cb18ac4500f3a14067b19408705068647cb0c5
https://github.com/qemu/qemu/commit/83cb18ac4500f3a14067b19408705068647cb0c5
Author: Stefano Garzarella <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M backends/cryptodev-vhost.c
Log Message:
-----------
cryptodev/vhost: allocate CryptoDevBackendVhost using g_mem0()
The function `vhost_dev_init()` expects the `struct vhost_dev`
(passed as a parameter) to be fully initialized. This is important
because some parts of the code check whether `vhost_dev->config_ops`
is NULL to determine if it has been set (e.g. later via
`vhost_dev_set_config_notifier`).
To ensure this initialization, it’s better to allocate the entire
`CryptoDevBackendVhost` structure (which includes `vhost_dev`) using
`g_mem0()`, following the same approach used for other vhost devices,
such as in `vhost_net_init()`.
Fixes: 042cea274c ("cryptodev: add vhost-user as a new cryptodev backend")
Cc: [email protected]
Reported-by: [email protected]
Signed-off-by: Stefano Garzarella <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 590de17b829d2ccd8067f19c71a53e31bec7bf00
https://github.com/qemu/qemu/commit/590de17b829d2ccd8067f19c71a53e31bec7bf00
Author: Stefano Garzarella <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M MAINTAINERS
Log Message:
-----------
MAINTAINERS: add more files to `vhost`
While sending a patch for backends/cryptodev-vhost.c I noticed that
Michael wasn`t in CC so I took a look at the files listed under `vhost`
and tried to fix it increasing the coverage by adding new files.
Signed-off-by: Stefano Garzarella <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 50e9754149066dc91f58405d3378b589098cb408
https://github.com/qemu/qemu/commit/50e9754149066dc91f58405d3378b589098cb408
Author: Konstantin Shkolnyy <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/virtio/vhost-shadow-virtqueue.c
Log Message:
-----------
vdpa: Fix endian bugs in shadow virtqueue
VDPA didn't work on a big-endian machine due to missing/incorrect
CPU<->LE data format conversions.
Signed-off-by: Konstantin Shkolnyy <[email protected]>
Message-Id: <[email protected]>
Fixes: 10857ec0ad ("vhost: Add VhostShadowVirtqueue")
Acked-by: Eugenio Pérez <[email protected]>
Tested-by: Lei Yang <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 131fe64e63c88ec52c45a5946a478c0edeb31b78
https://github.com/qemu/qemu/commit/131fe64e63c88ec52c45a5946a478c0edeb31b78
Author: Alexander Graf <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/virtio/virtio-nsm.c
Log Message:
-----------
hw/virtio/virtio-nsm: Respond with correct length
When we return a response packet from NSM, we need to indicate its
length according to the content of the response. Prior to this patch, we
returned the length of the source buffer, which may confuse guest code
that relies on the response size.
Fix it by returning the response payload size instead.
Fixes: bb154e3e0cc715 ("device/virtio-nsm: Support for Nitro Secure Module
device")
Reported-by: Vikrant Garg <[email protected]>
Signed-off-by: Alexander Graf <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Dorjoy Chowdhury <[email protected]>
Fixes: bb154e3e0cc715 ("device/virtio-nsm: Support for Nitro Secure Module
device")<br>
Reported-by: Vikrant Garg <[email protected]>
Signed-off-by: Alexander Graf <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Tested-by: Vikrant Garg <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 02fd9f8aeeb184276b283ae2f404bc3acf1e7b7a
https://github.com/qemu/qemu/commit/02fd9f8aeeb184276b283ae2f404bc3acf1e7b7a
Author: Laurent Vivier <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M net/vhost-user.c
M qapi/net.json
Log Message:
-----------
net: vhost-user: add QAPI events to report connection state
The netdev reports NETDEV_VHOST_USER_CONNECTED event when
the chardev is connected, and NETDEV_VHOST_USER_DISCONNECTED
when it is disconnected.
The NETDEV_VHOST_USER_CONNECTED event includes the chardev id.
This allows a system manager like libvirt to detect when the server
fails.
For instance with passt:
{ 'execute': 'qmp_capabilities' }
{ "return": { } }
[killing passt here]
{ "timestamp": { "seconds": 1739538634, "microseconds": 920450 },
"event": "NETDEV_VHOST_USER_DISCONNECTED",
"data": { "netdev-id": "netdev0" } }
[automatic reconnection with reconnect-ms]
{ "timestamp": { "seconds": 1739538638, "microseconds": 354181 },
"event": "NETDEV_VHOST_USER_CONNECTED",
"data": { "netdev-id": "netdev0", "chardev-id": "chr0" } }
Tested-by: Stefano Brivio <[email protected]>
Signed-off-by: Laurent Vivier <[email protected]>
Message-Id: <[email protected]>
Acked-by: Markus Armbruster <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: e87b6efb11be9f5ff213461f5ecdbae47d9402b9
https://github.com/qemu/qemu/commit/e87b6efb11be9f5ff213461f5ecdbae47d9402b9
Author: Matias Ezequiel Vara Larsen <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/virtio/vhost-user-snd.c
Log Message:
-----------
vhost-user-snd: correct the calculation of config_size
Use virtio_get_config_size() rather than sizeof(struct
virtio_snd_config) for the config_size in the vhost-user-snd frontend.
The frontend shall rely on device features for the size of the device
configuration space. The presence of `controls` in the config space
depends on VIRTIO_SND_F_CTLS according to the specification (v1.3):
`
5.14.4 Device Configuration Layout
...
controls
(driver-read-only) indicates a total number of all available control
elements if VIRTIO_SND_F_CTLS has been negotiated.
`
This fixes an issue introduced by commit ab0c7fb2 ("linux-headers:
update to current kvm/next") in which the optional field `controls` is
added to the virtio_snd_config structure. This breaks vhost-user-device
backends that do not implement the `controls` field.
Fixes: ab0c7fb22b ("linux-headers: update to current kvm/next")
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2805
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Suggested-by: Stefano Garzarella <[email protected]>
Signed-off-by: Matias Ezequiel Vara Larsen <[email protected]>
Message-Id: <[email protected]>
Cc: [email protected]
Reviewed-by: Stefano Garzarella <[email protected]>
Reviewed-by: Dorinda Bassey <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: d261b84d354a41a38336af813f92f636d3fb3f78
https://github.com/qemu/qemu/commit/d261b84d354a41a38336af813f92f636d3fb3f78
Author: Eric Auger <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/virtio/trace-events
M hw/virtio/virtio-iommu.c
Log Message:
-----------
hw/virtio/virtio-iommu: Migrate to 3-phase reset
Currently the iommu may be reset before the devices
it protects. For example this happens with virtio-net.
Let's use 3-phase reset mechanism and reset the IOMMU on
exit phase after all DMA capable devices have been
reset during the 'enter' or 'hold' phase.
Signed-off-by: Eric Auger <[email protected]>
Acked-by: Michael S. Tsirkin <[email protected]>
Reviewed-by: Zhenzhong Duan <[email protected]>
Acked-by: Jason Wang <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: 2aaf48bcf27d8b3da5b30af6c1ced464d3df30f7
https://github.com/qemu/qemu/commit/2aaf48bcf27d8b3da5b30af6c1ced464d3df30f7
Author: Eric Auger <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/i386/intel_iommu.c
M hw/i386/trace-events
Log Message:
-----------
hw/i386/intel-iommu: Migrate to 3-phase reset
Currently the IOMMU may be reset before the devices
it protects. For example this happens with virtio devices
but also with VFIO devices. In this latter case this
produces spurious translation faults on host.
Let's use 3-phase reset mechanism and reset the IOMMU on
exit phase after all DMA capable devices have been reset
on 'enter' or 'hold' phase.
Signed-off-by: Eric Auger <[email protected]>
Acked-by: Michael S. Tsirkin <[email protected]>
Acked-by: Jason Wang <[email protected]>
Zhenzhong Duan <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: e39e3f8b8dea856f141e9945167d2b18021ef445
https://github.com/qemu/qemu/commit/e39e3f8b8dea856f141e9945167d2b18021ef445
Author: Eric Auger <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/arm/smmu-common.c
M hw/arm/smmuv3.c
M hw/arm/trace-events
Log Message:
-----------
hw/arm/smmuv3: Move reset to exit phase
Currently the iommu may be reset before the devices
it protects. For example this happens with virtio-scsi-pci.
when system_reset is issued from qmp monitor: spurious
"virtio: zero sized buffers are not allowed" warnings can
be observed. This happens because outstanding DMA requests
are still happening while the SMMU gets reset.
This can also happen with VFIO devices. In that case
spurious DMA translation faults can be observed on host.
Make sure the SMMU is reset in the 'exit' phase after
all DMA capable devices have been reset during the 'enter'
or 'hold' phase.
Signed-off-by: Eric Auger <[email protected]>
Reviewed-by: Zhenzhong Duan <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: d410e709526d1cd4aa9085c6e254a622594a02a5
https://github.com/qemu/qemu/commit/d410e709526d1cd4aa9085c6e254a622594a02a5
Author: Eric Auger <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M hw/vfio/common.c
M hw/vfio/trace-events
Log Message:
-----------
hw/vfio/common: Add a trace point in vfio_reset_handler
To ease the debug of reset sequence, let's add a trace point
in vfio_reset_handler()
Signed-off-by: Eric Auger <[email protected]>
Reviewed-by: Cédric Le Goater <[email protected]>
Acked-by: Michael S. Tsirkin <[email protected]>
Reviewed-by: Zhenzhong Duan <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: dd6d545e8f2d9a0e8a8c287ec16469f03ef5c198
https://github.com/qemu/qemu/commit/dd6d545e8f2d9a0e8a8c287ec16469f03ef5c198
Author: Eric Auger <[email protected]>
Date: 2025-02-21 (Fri, 21 Feb 2025)
Changed paths:
M docs/devel/reset.rst
Log Message:
-----------
docs/devel/reset: Document reset expectations for DMA and IOMMU
To avoid any translation faults, the IOMMUs are expected to be
reset after the devices they protect. Document that we expect
DMA requests to be stopped during the 'enter' or 'hold' phase
while IOMMUs should be reset during the 'exit' phase.
Signed-off-by: Eric Auger <[email protected]>
Reviewed-by: Zhenzhong Duan <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Reviewed-by: Michael S. Tsirkin <[email protected]>
Signed-off-by: Michael S. Tsirkin <[email protected]>
Commit: b69801dd6b1eb4d107f7c2f643adf0a4e3ec9124
https://github.com/qemu/qemu/commit/b69801dd6b1eb4d107f7c2f643adf0a4e3ec9124
Author: Stefan Hajnoczi <[email protected]>
Date: 2025-02-22 (Sat, 22 Feb 2025)
Changed paths:
M MAINTAINERS
M backends/cryptodev-vhost.c
M docs/about/deprecated.rst
M docs/about/removed-features.rst
M docs/devel/reset.rst
M docs/pcie_sriov.txt
M hw/arm/smmu-common.c
M hw/arm/smmuv3.c
M hw/arm/trace-events
M hw/cxl/cxl-component-utils.c
M hw/cxl/cxl-device-utils.c
M hw/cxl/switch-mailbox-cci.c
M hw/i386/amd_iommu.c
M hw/i386/amd_iommu.h
M hw/i386/intel_iommu.c
M hw/i386/microvm.c
M hw/i386/pc.c
M hw/i386/trace-events
M hw/mem/cxl_type3.c
M hw/net/igb.c
M hw/net/virtio-net.c
M hw/nvme/ctrl.c
M hw/pci/msix.c
M hw/pci/pci.c
M hw/pci/pcie_sriov.c
M hw/pci/trace-events
M hw/ppc/spapr_pci.c
M hw/s390x/s390-pci-bus.c
M hw/vfio/common.c
M hw/vfio/trace-events
M hw/virtio/trace-events
M hw/virtio/vhost-iova-tree.c
M hw/virtio/vhost-iova-tree.h
M hw/virtio/vhost-shadow-virtqueue.c
M hw/virtio/vhost-shadow-virtqueue.h
M hw/virtio/vhost-user-snd.c
M hw/virtio/vhost-vdpa.c
M hw/virtio/virtio-balloon.c
M hw/virtio/virtio-iommu.c
M hw/virtio/virtio-nsm.c
M include/hw/cxl/cxl_device.h
M include/hw/pci/pcie_sriov.h
M include/hw/virtio/virtio-balloon.h
M include/qemu/iova-tree.h
M net/vhost-user.c
M net/vhost-vdpa.c
M qapi/net.json
M tests/functional/meson.build
A tests/functional/test_virtio_balloon.py
M tests/qtest/libqos/pci.c
M util/iova-tree.c
Log Message:
-----------
Merge tag 'for_upstream' of https://git.kernel.org/pub/scm/virt/kvm/mst/qemu
into staging
virtio,pc,pci: features, fixes, cleanups
Features:
SR-IOV emulation for pci
virtio-mem-pci support for s390
interleave support for cxl
big endian support for vdpa svq
new QAPI events for vhost-user
Also vIOMMU reset order fixups are in.
Fixes, cleanups all over the place.
Signed-off-by: Michael S. Tsirkin <[email protected]>
# -----BEGIN PGP SIGNATURE-----
#
# iQFDBAABCAAtFiEEXQn9CHHI+FuUyooNKB8NuNKNVGkFAme4b8sPHG1zdEByZWRo
# YXQuY29tAAoJECgfDbjSjVRpHKcIAKPJsVqPdda2dJ7b7FdyRT0Q+uwezXqaGHd4
# 7Lzih1wsxYNkwIAyPtEb76/21qiS7BluqlUCfCB66R9xWjP5/KfvAFj4/r4AEduE
# fxAgYzotNpv55zcRbcflMyvQ42WGiZZHC+o5Lp7vDXUP3pIyHrl0Ydh5WmcD+hwS
# BjXvda58TirQpPJ7rUL+sSfLih17zQkkDcfv5/AgorDy1wK09RBKwMx/gq7wG8yJ
# twy8eBY2CmfmFD7eTM+EKqBD2T0kwLEeLfS/F/tl5Fyg6lAiYgYtCbGLpAmWErsg
# XZvfZmwqL7CNzWexGvPFnnLyqwC33WUP0k0kT88Y5wh3/h98blw=
# =tej8
# -----END PGP SIGNATURE-----
# gpg: Signature made Fri 21 Feb 2025 20:21:31 HKT
# gpg: using RSA key 5D09FD0871C8F85B94CA8A0D281F0DB8D28D5469
# gpg: issuer "[email protected]"
# gpg: Good signature from "Michael S. Tsirkin <[email protected]>" [full]
# gpg: aka "Michael S. Tsirkin <[email protected]>" [full]
# Primary key fingerprint: 0270 606B 6F3C DF3D 0B17 0970 C350 3912 AFBE 8E67
# Subkey fingerprint: 5D09 FD08 71C8 F85B 94CA 8A0D 281F 0DB8 D28D 5469
* tag 'for_upstream' of https://git.kernel.org/pub/scm/virt/kvm/mst/qemu: (41
commits)
docs/devel/reset: Document reset expectations for DMA and IOMMU
hw/vfio/common: Add a trace point in vfio_reset_handler
hw/arm/smmuv3: Move reset to exit phase
hw/i386/intel-iommu: Migrate to 3-phase reset
hw/virtio/virtio-iommu: Migrate to 3-phase reset
vhost-user-snd: correct the calculation of config_size
net: vhost-user: add QAPI events to report connection state
hw/virtio/virtio-nsm: Respond with correct length
vdpa: Fix endian bugs in shadow virtqueue
MAINTAINERS: add more files to `vhost`
cryptodev/vhost: allocate CryptoDevBackendVhost using g_mem0()
vhost-iova-tree: Update documentation
vhost-iova-tree, svq: Implement GPA->IOVA & partial IOVA->HVA trees
vhost-iova-tree: Implement an IOVA-only tree
amd_iommu: Use correct bitmask to set capability BAR
amd_iommu: Use correct DTE field for interrupt passthrough
hw/virtio: reset virtio balloon stats on machine reset
mem/cxl_type3: support 3, 6, 12 and 16 interleave ways
hw/mem/cxl_type3: Ensure errp is set on realization failure
hw/mem/cxl_type3: Fix special_ops memory leak on msix_init_exclusive_bar()
failure
...
Signed-off-by: Stefan Hajnoczi <[email protected]>
Compare: https://github.com/qemu/qemu/compare/f41af4c5857b...b69801dd6b1e
To unsubscribe from these emails, change your notification settings at
https://github.com/qemu/qemu/settings/notifications
