[PATCH 2/6] MAX78000: ICC Implementation

This patch implements the Instruction Cache Controller for the MAX78000 SOC Signed-off-by: Jackson Donaldson --- hw/arm/Kconfig | 1 + hw/arm/max78000_soc.c | 20 ++-- hw/misc/Kconfig| 3 ++ hw/misc/max78000_icc.c | 89 ++

[PATCH 3/6] MAX78000 UART implementation

This patch implements UART support for the MAX78000 SOC Signed-off-by: Jackson Donaldson --- hw/arm/Kconfig | 1 + hw/arm/max78000_soc.c | 27 +++- hw/char/Kconfig | 3 + hw/char/max78000_uart.c | 263 hw/ch

[PATCH 1/6] MAX78000: Add MAX78000FTHR Machine

This patch adds support for the MAX78000FTHR machine. The MAX78000FTHR contains a MAX78000 and a RISC-V core. This patch implements only the MAX78000, which is Cortex-M4 based. Details can be found at: https://www.analog.com/media/en/technical-documentation/user-guides/max78000-user-guide.pdf Sig

[PATCH 0/3] docs: Bump sphinx to 6.2.1

Supersedes: <20250505-sphinx82-v1-0-85f2418b3...@daynix.com> ("[PATCH 0/2] docs: Bump sphinx to 8.2.3") sphinx 5.3.0 fails with Python 3.13.1: ../docs/meson.build:37: WARNING: /home/me/qemu/build/pyvenv/bin/sphinx-build: Extension error: Could not import extension sphinx.builders.epub3 (exception

[PATCH 2/3] docs: Require sphinx>=6.2

This makes docs/sphinx/compat.py unnecessary. The accepted range of the sphinx_rtd_theme version was also changed to >=1.2 for compatibility with sphinx>=6.2. Signed-off-by: Akihiko Odaki --- docs/sphinx/compat.py | 230 - docs/sphinx/qapi_domain.

[PATCH 3/3] MAINTAINERS: Add docs/requirements.txt

Add docs/requirements.txt to "Sphinx documentation configuration and build machinery". Signed-off-by: Akihiko Odaki --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index d54b5578f883..6ae5d2665e16 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -4328,6

[PATCH 1/3] docs: Bump sphinx to 6.2.1

sphinx 5.3.0 fails with Python 3.13.1: ../docs/meson.build:37: WARNING: /home/me/qemu/build/pyvenv/bin/sphinx-build: Extension error: Could not import extension sphinx.builders.epub3 (exception: No module named 'imghdr') ../docs/meson.build:39:6: ERROR: Problem encountered: Install a Python 3 v

Re: [PATCH v1 08/22] hw/misc/aspeed_hace: Support DMA 64 bits dram address.

On 5/9/25 09:04, Jamin Lin wrote: Hi Cédric Subject: Re: [PATCH v1 08/22] hw/misc/aspeed_hace: Support DMA 64 bits dram address. On 3/21/25 10:26, Jamin Lin wrote: According to the AST2700 design, the data source address is 64-bit, with R_HASH_SRC_HI storing bits [63:32] and R_HASH_SRC storin

Re: [PATCH v1 06/22] hw/misc/aspeed_hace: Support accumulative mode for direct access mode

On 5/9/25 08:55, Jamin Lin wrote: Hi Cédric Subject: Re: [PATCH v1 06/22] hw/misc/aspeed_hace: Support accumulative mode for direct access mode On 3/21/25 10:26, Jamin Lin wrote: Enable accumulative mode for direct access mode operations. In direct access mode, only a single source buffer is

Re: [PATCH RFC 00/10] qapi: remove all TARGET_* conditionals from the schema

Daniel P. Berrangé writes: > On Fri, May 09, 2025 at 03:43:30PM +0200, Markus Armbruster wrote: >> Daniel P. Berrangé writes: >> > I think we have to distinguish between what made sense in the context >> > of our original design, from what makes sense for our future design(s) >> > and plans. >>

Re: [PATCH 1/2] docs: Bump sphinx to 8.2.3

On 2025/05/08 3:23, John Snow wrote: On Wed, May 7, 2025 at 1:22 AM Markus Armbruster > wrote: John Snow mailto:js...@redhat.com>> writes: > On Mon, May 5, 2025 at 8:19 AM Akihiko Odaki mailto:akihiko.od...@daynix.com>> > wrote: > >> sphi

Re: [PATCH v2 06/14] contrib/plugins: allow setting of instructions per quantum

On 2025/05/06 21:57, Alex Bennée wrote: The default is we update time every 1/10th of a second or so. However for some cases we might want to update time more frequently. Allow this to be set via the command line through the ipq argument. Signed-off-by: Alex Bennée Reviewed-by: Pierrick Bouvier

Re: [PATCH v2 12/14] ui/gtk-gl-area: Remove extra draw call in refresh

On 2025/05/06 21:57, Alex Bennée wrote: From: Dongwon Kim This partially reverts commit 77bf310084dad38b3a2badf01766c659056f1cf2 which causes some guest display corruption when gtk-gl-area is used for GTK rendering (e.g. Wayland Compositor) possibly due to simulataneous accesses on the guest fr

Re: [PATCH v2 05/14] contrib/plugins: add a scaling factor to the ips arg

On 2025/05/06 21:57, Alex Bennée wrote: It's easy to get lost in zeros while setting the numbers of instructions per second. Add a scaling suffix to make things simpler. Signed-off-by: Alex Bennée Reviewed-by: Pierrick Bouvier --- v2 - normalise the suffix before a full strcmp0 - check

Re: [PATCH v2 04/14] Running with --enable-ubsan leads to a qtest failure

I think the subject should tell what this patch does and perhaps the underlying problem it solves instead of the symptom. It may be nice to have a prefix "tests/qtest/libqos/igb:" to comply the convention. On 2025/05/06 21:57, Alex Bennée wrote: From: Nabih Estefan ../tests/qtest/libqos/i

Re: [PATCH v2 03/14] tests/tcg: make aarch64 boot.S handle different starting modes

On 2025/05/06 21:57, Alex Bennée wrote: Currently the boot.S code assumes everything starts at EL1. This will break things like the memory test which will barf on unaligned memory access when run at a higher level. Adapt the boot code to do some basic verification of the starting mode and the mi

Re: [PATCH v4 12/13] ram-block-attribute: Add priority listener support for PrivateSharedListener

On 4/7/2025 3:49 PM, Chenyi Qiang wrote: In-place page conversion requires operations to follow a specific sequence: unmap-before-conversion-to-private and map-after-conversion-to-shared. Currently, both attribute changes and VFIO DMA map/unmap operations are handled by PrivateSharedListeners, th

[PULL 2/3] tests/qtest/libqos: Avoid double swapping when using modern virtio

From: Thomas Huth The logic in the qvirtio_read/write function is rather a headache, involving byte-swapping when the target is big endian, just to maybe involve another byte-swapping in the qtest_read/write function immediately afterwards (on the QEMU side). Let's do it in a more obvious way he

[PATCH] Add nRF51 RTC timer

Implements the RTC timer for nRF51. Implementation is based on existing nrf51_timer. Event signaling through PPI peripheral is not implemented. Tests added in microbit board. Signed-off-by: Kaido Kert --- hw/arm/nrf51_soc.c | 13 ++ hw/rtc/Kconfig | 3 + hw/rtc/meson.bui

[PATCH] tests/functional: Add PCI hotplug test for aarch64

Add a functional test, aarch64_hotplug_pci, to exercise PCI hotplug and hot-unplug on arm64. Currently, the aarch64 'virt' machine uses the PCIe native controller and does not support ACPI-based hotplugging. However, since support is planned, this test sets 'acpi=force' and specifies an EDK2 firmwa

Re: [PATCH] migration: add FEATURE_SEEKABLE to QIOChannelBlock

On Fri, May 09, 2025 at 11:14:41PM +0200, Marco Cavenati wrote: > On Friday, May 09, 2025 18:21 CEST, Peter Xu wrote: > > > So you don't really need to take sequence of snapshots? Hmm, that sounds > > like a completely different use case that I originally thought. > > Correct > > > Have you t

[PATCH v4 07/13] mirror: Pass full sync mode rather than bool to internals

Out of the five possible values for MirrorSyncMode, INCREMENTAL and BITMAP are already rejected up front in mirror_start, leaving NONE, TOP, and FULL as the remaining values that the code was collapsing into a single bool is_none_mode. Furthermore, mirror_dirty_init() is only reachable for modes T

Re: [PATCH] migration: add FEATURE_SEEKABLE to QIOChannelBlock

On Friday, May 09, 2025 18:21 CEST, Peter Xu wrote: > So you don't really need to take sequence of snapshots? Hmm, that sounds > like a completely different use case that I originally thought. Correct > Have you thought of leveraging ignore-shared and MAP_PRIVATE for the major > chunk of gues

[PULL 1/3] qtest: introduce qtest_init_ext

From: Vladimir Sementsov-Ogievskiy Merge qtest_init_with_env_and_capabilities() and qtest_init_with_env() into one qtest_init_ext(). Reasons: 1. qtest_init_with_env() is just wrong: it gets do_connect parameter but always pass true to qtest_init_with_env_and_capabilities(). Happily, all q

[PULL 0/3] QTest patches for 2025-05-09

The following changes since commit 4b1f5b73e060971c434e70694d571adfee553027: tests/functional: Use -no-shutdown in the hppa_seabios test (2025-05-08 15:38:40 -0400) are available in the Git repository at: https://gitlab.com/farosas/qemu.git tags/qtest-20250509-pull-request for you to

[PULL 3/3] tests/qtest/cpu-plug-test: Add cpu hotplug support for LoongArch

From: Bibo Mao Add cpu hotplug testcase support for LoongArch system, it passes to run with command "make check-qtest-loongarch64" as following: qemu:qtest+qtest-loongarch64 / qtest-loongarch64/cpu-plug-test OK 0.38s 1 subtests passed Signed-off-by: Bibo Mao Reviewed-by: Thomas Huth Message

[PATCH v4 02/13] file-posix, gluster: Handle zero block status hint better

Although the previous patch to change 'bool want_zero' into a bitmask made no semantic change, it is now time to differentiate. When the caller specifically wants to know what parts of the file read as zero, we need to use lseek and actually reporting holes, rather than short-circuiting and advert

[PATCH v4 04/13] block: Add new bdrv_co_is_all_zeroes() function

There are some optimizations that require knowing if an image starts out as reading all zeroes, such as making blockdev-mirror faster by skipping the copying of source zeroes to the destination. The existing bdrv_co_is_zero_fast() is a good building block for answering this question, but it tends

[PULL 21/21] docs/devel/testing/functional: Fix typo

From: Gustavo Romero Fix the duplication of the word 'run'. Signed-off-by: Gustavo Romero Reviewed-by: Peter Maydell Reviewed-by: Michael Tokarev Signed-off-by: Michael Tokarev --- docs/devel/testing/functional.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/dev

Re: [PATCH v9 13/55] i386/tdx: Support user configurable mrconfigid/mrowner/mrownerconfig

On 5/8/2025 11:55 PM, Daniel P. Berrangé wrote: On Thu, May 08, 2025 at 10:59:19AM -0400, Xiaoyao Li wrote: From: Isaku Yamahata Three sha384 hash values, mrconfigid, mrowner and mrownerconfig, of a TD can be provided for TDX attestation. Detailed meaning of them can be found: https://lore.ke

[PATCH v4 11/13] mirror: Skip writing zeroes when target is already zero

When mirroring, the goal is to ensure that the destination reads the same as the source; this goal is met whether the destination is sparse or fully-allocated (except when explicitly punching holes, then merely reading zero is not enough to know if it is sparse, so we still want to punch the hole).

[PULL v3 00/21] Trivial patches for 2025-05-07

The following changes since commit c5e2c4042e3c50b96cc5eaa9683325c5a96913b0: Merge tag 'pull-loongarch-20250506' of https://github.com/bibo-mao/qemu into staging (2025-05-06 11:03:45 -0400) are available in the Git repository at: https://gitlab.com/mjt0k/qemu.git tags/pull-trivial-patches

[PATCH v4 10/13] mirror: Skip pre-zeroing destination if it is already zero

When doing a sync=full mirroring, we can skip pre-zeroing the destination if it already reads as zeroes and we are not also trying to punch holes due to detect-zeroes. With this patch, there are fewer scenarios that have to pass in an explicit target-is-zero, while still resulting in a sparse dest

[PATCH v4 09/13] mirror: Drop redundant zero_target parameter

The two callers to a mirror job (drive-mirror and blockdev-mirror) set zero_target precisely when sync mode == FULL, with the one exception that drive-mirror skips zeroing the target if it was newly created and reads as zero. But given the previous patch, that exception is equally captured by targ

[PATCH v4 06/13] mirror: Minor refactoring

Commit 5791ba52 (v9.2) pre-initialized ret in mirror_dirty_init to silence a false positive compiler warning, even though in all code paths where ret is used, it was guaranteed to be reassigned beforehand. But since the function returns -errno, and -1 is not always the right errno, it's better to

[PATCH v4 03/13] block: Let bdrv_co_is_zero_fast consolidate adjacent extents

Some BDS drivers have a cap on how much block status they can supply in one query (for example, NBD talking to an older server cannot inspect more than 4G per query; and qcow2 tends to cap its answers rather than cross a cluster boundary of an L1 table). Although the existing callers of bdrv_co_is

[PATCH v4 12/13] iotests/common.rc: add disk_usage function

From: Andrey Drobyshev Move the definition from iotests/250 to common.rc. This is used to detect real disk usage of sparse files. In particular, we want to use it for checking subclusters-based discards. Signed-off-by: Andrey Drobyshev Reviewed-by: Alexander Ivanov Reviewed-by: Alberto Garci

[PATCH v4 05/13] iotests: Improve iotest 194 to mirror data

Mirroring a completely sparse image to a sparse destination should be practically instantaneous. It isn't yet, but the test will be more realistic if it has some non-zero to mirror as well as the holes. Signed-off-by: Eric Blake Reviewed-by: Stefan Hajnoczi --- tests/qemu-iotests/194 | 1 + 1

[PATCH v4 13/13] tests: Add iotest mirror-sparse for recent patches

Prove that blockdev-mirror can now result in sparse raw destination files, regardless of whether the source is raw or qcow2. By making this a separate test, it was possible to test effects of individual patches for the various pieces that all have to work together for a sparse mirror to be success

[PATCH v4 01/13] block: Expand block status mode from bool to flags

This patch is purely mechanical, changing bool want_zero into an unsigned int for bitwise-or of flags. As of this patch, all implementations are unchanged (the old want_zero==true is now mode==BDRV_WANT_PRECISE which is a superset of BDRV_WANT_ZERO); but the callers in io.c that used to pass want_

[PATCH v4 00/13] Make blockdev-mirror dest sparse in more cases

v3 was here: https://lists.gnu.org/archive/html/qemu-devel/2025-04/msg04525.html In v4: - Rearrange series a bit to try and simplify logic for how zero bitmap is populated, when pre-zeroing is attempted, and how detect-zeroes=unmap interacts [Sunny] - Add a couple new patches to make this

[PATCH v4 08/13] mirror: Allow QMP override to declare target already zero

QEMU has an optimization for a just-created drive-mirror destination that is not possible for blockdev-mirror (which can't create the destination) - any time we know the destination starts life as all zeroes, we can skip a pre-zeroing pass on the destination. Recent patches have added an improved

[RFC PATCH v8 4/6] hw/vfio/ap: store object indicating AP config changed in a queue

Creates an object indicating that an AP configuration change event has been received and stores it in a queue. These objects will later be used to store event information for an AP configuration change when the CHSC instruction is intercepted. Signed-off-by: Rorie Reyes --- hw/vfio/ap.c | 12 +++

Re: [PATCH RFC 00/10] qapi: remove all TARGET_* conditionals from the schema

Daniel P. Berrangé writes: > On Thu, May 08, 2025 at 02:09:37PM -0700, Pierrick Bouvier wrote: >> On 5/8/25 6:58 AM, Daniel P. Berrangé wrote: >> > Pierrick has proposed a series that introduces a concept of runtime >> > conditionals to the QAPI schema, in order to adapt the TARGET_* >> > conditi

Re: [PATCH] s390x: Fix leak in machine_set_loadparm

On 09/05/2025 19.49, Fabiano Rosas wrote: ASAN spotted a leaking string in machine_set_loadparm(): Direct leak of 9 byte(s) in 1 object(s) allocated from: #0 0x560ffb5bb379 in malloc ../projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:69:3 #1 0x7f1aca926518 in g_malloc ../glib/gmem

Re: [PATCH v1] Implement RTC timer for nRF51

On Sun, 4 May 2025 at 11:36, Kaido Kert wrote: > > Implements the RTC timer. Implementation is based on > existing nrf51_timer and other RTCs. > Event signaling through PPI peripheral is not implemented. > Tests added in microbit board. > > Signed-off-by: Kaido Kert Hi; thanks for this patch; ge

Re: [PATCH] migration: add FEATURE_SEEKABLE to QIOChannelBlock

On Fri, May 09, 2025 at 02:51:47PM +0200, Marco Cavenati wrote: > Hello Peter, > > On Thursday, May 08, 2025 22:23 CEST, Peter Xu wrote: > > > > The scenarios where zeroing is not required (incoming migration and > > > -loadvm) share a common characteristic: the VM has not yet run in the > > > c

Re: [PATCH v3 0/5] docs: automated info about machine deprecation/removal info

On Tue, May 06, 2025 at 05:00:19PM +0100, Daniel P. Berrangé wrote: > Since we deprecate and remove versioned machine types on a fixed > schedule, we can automatically ensure that the docs reflect the > latest version info, rather than requiring manual updates on each > dev cycle. > > The first pa

[PATCH] tests/qtest/ast2700-smc-test: Fix leak

ASAN spotted a leak of the memory used to hold the tmp_path: Direct leak of 35 byte(s) in 1 object(s) allocated from: #0 0x55e29aa96da9 in malloc ../projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:69:3 #1 0x7fe0cfb26518 in g_malloc ../glib/gmem.c:106 #2 0x7fe0cfb4146e in g_strconc

Re: [PATCH] tests/functional: Use -no-shutdown in the hppa_seabios test

On 8/5/25 20:09, Thomas Huth wrote: From: Thomas Huth qemu-system-hppa shuts down automatically when the BIOS is unable to boot from any device. So this test currently fails occasionally when QEMU already quit, but the test still expected it to be around (e.g. to shut it down cleanly). Adding a

[PATCH] s390x: Fix leak in machine_set_loadparm

ASAN spotted a leaking string in machine_set_loadparm(): Direct leak of 9 byte(s) in 1 object(s) allocated from: #0 0x560ffb5bb379 in malloc ../projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:69:3 #1 0x7f1aca926518 in g_malloc ../glib/gmem.c:106 #2 0x7f1aca94113e in g_strdup ../gl

[PATCH 1/7] hw/cxl/events: Update for rev3.2 common event record format

From: Shiju Jose CXL spec 3.2 section 8.2.9.2.1 Table 8-55, Common Event Record format has updated with Maintenance Operation Subclass, LD ID and ID of the device head information. Add updates for the above spec changes in the related CXL events reporting and QMP command to inject CXL events. S

[RFC PATCH] hw/s390x: add vhost-user-device-ccw stub (!WIP)

This Friday hack was driven by wanting to review some virtiofsd changes. However I discovered that while virtiofsd support VHOST_USER_PROTOCOL_F_CONFIG the current virtiofs stubs still assume QEMU controls the config space. Ahh I thought, but we have vhost-user-base which both supports this and pr

[PATCH 5/7] hw/cxl/cxl-mailbox-utils: Move declaration of scrub and ECS feature attributes in cmd_features_set_feature()

From: Shiju Jose Move the declaration of scrub and ECS feature attributes in cmd_features_set_feature() to the local scope where they are used. Signed-off-by: Shiju Jose --- hw/cxl/cxl-mailbox-utils.c | 13 + 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/hw/cxl/cxl

[PATCH 3/7] hw/cxl/events: Updates for rev3.2 DRAM event record

From: Shiju Jose CXL spec rev3.2 section 8.2.10.2.1.2 Table 8-58, DRAM event record has updated with following new fields. 1. Component Identifier 2. Sub-channel of the memory event location 3. Advanced Programmable Corrected Memory Error Threshold Event Flags 4. Corrected Volatile Memory Error C

[PATCH 6/7] hw/cxl: Add Maintenance support

From: Davidlohr Bueso This adds initial support for the Maintenance command, specifically the soft and hard PPR operations on a dpa. The implementation allows to be executed at runtime, therefore semantically, data is retained and CXL.mem requests are correctly processed. Keep track of the reque

[PATCH 4/7] hw/cxl/events: Updates for rev3.2 memory module event record

From: Shiju Jose CXL spec rev3.2 section 8.2.10.2.1.3 Table 8-50, memory module event record has updated with following new fields. 1. Validity Flags 2. Component Identifier 3. Device Event Sub-Type Add updates for the above spec changes in the CXL memory module event reporting and QMP command t

[PATCH 7/7] hw/cxl: Add emulation for memory sparing control feature

From: Shiju Jose Memory sparing is defined as a repair function that replaces a portion of memory with a portion of functional memory at that same DPA. The subclasses for this operation vary in terms of the scope of the sparing being performed. The Cacheline sparing subclass refers to a sparing a

[PATCH 0/7] hw/cxl: Update CXL events to rev3.2 and add maintenance support for memory repair features

From: Shiju Jose Add updates for the CXL spec rev3.2 changes, in the CXL events reporting and QMP command to inject CXL events. Add maintenance support and emulation support for memory Post Package Repair(PPR) and memory sparing control features. Davidlohr Bueso (1): hw/cxl: Add Maintenance s

[PATCH 2/7] hw/cxl/events: Updates for rev3.2 general media event record

From: Shiju Jose CXL spec rev3.2 section 8.2.10.2.1.1 Table 8-57, general media event table has updated with following new fields. 1. Advanced Programmable Corrected Memory Error Threshold Event Flags 2. Corrected Memory Error Count at Event 3. Memory Event Sub-Type Add updates for the above spe

Re: [PATCH v3 00/15] vfio: preparation for vfio-user

On 5/9/25 12:24, Cédric Le Goater wrote: On 5/7/25 17:20, John Levon wrote: Hi, this series is against the vfio-next tree: https://github.com/legoater/qemu/commits/vfio-next The series contains patches to vfio to prepare for the vfio-user implementation. A previous version of these patches can

Re: [PULL v2 00/21] Trivial patches for 2025-05-07

On Wed, May 7, 2025 at 2:08 PM Michael Tokarev wrote: > > The following changes since commit c5e2c4042e3c50b96cc5eaa9683325c5a96913b0: > > Merge tag 'pull-loongarch-20250506' of https://github.com/bibo-mao/qemu > into staging (2025-05-06 11:03:45 -0400) > > are available in the Git repository a

Re: [PATCH v2] hw/arm: Replace TABs for spaces

On Mon, 5 May 2025 at 14:11, Santiago Monserrat Campanello wrote: > > replaced all TABs for spaces for arm code > > Signed-off-by: Santiago Monserrat Campanello > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/373 > > --- > replaced all tabs with spaces using vim :retab > used 4 spaces e

Re: [PATCH v4 15/27] hw/core/machine: Remove hw_compat_2_6[] array

On Thu, May 08, 2025 at 03:35:38PM +0200, Philippe Mathieu-Daudé wrote: > Date: Thu, 8 May 2025 15:35:38 +0200 > From: Philippe Mathieu-Daudé > Subject: [PATCH v4 15/27] hw/core/machine: Remove hw_compat_2_6[] array > X-Mailer: git-send-email 2.47.1 > > The hw_compat_2_6[] array was only used by

Re: Out-of-bounds access in rx_fifo_push()

On Sun, 4 May 2025 at 21:53, Chuhong Yuan wrote: > > Hello, > > This is a bug I reported to qemu-security, while I was suggested to > forward it here > because it doesn't align with the virtualization use case. > > Thanks, > Chuhong > > -- Forwarded message - > From: Chuhong Yuan

Re: [PATCH v2 2/2] semihosting/uaccess: Compile once

Hi Philippe, On 5/9/25 4:07 AM, Philippe Mathieu-Daudé wrote: Signed-off-by: Philippe Mathieu-Daudé --- semihosting/meson.build | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/semihosting/meson.build b/semihosting/meson.build index f3d38dda91d..d0819891bc3 100644 --- a

Re: [PATCH 1/1] vhost: do not reset used_memslots when destroying vhost dev

On Mon, Mar 03, 2025 at 01:02:17PM -0500, yuanminghao wrote: > > > Global used_memslots or used_shared_memslots is updated to 0 unexpectly > > > > it shouldn't be 0 in practice, as it comes from number of RAM regions VM > > has. > > It's likely a bug somewhere else. > > > > Please describe a way

[RFC PATCH v8 1/6] linux-header: update-linux-header script changes

Kernel commit 8a141be3233a changed from using ASSEMBLY to ASSEMBLER Updated the update-linux-header script to match Signed-off-by: Rorie Reyes --- scripts/update-linux-headers.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/update-linux-headers.sh b/scripts/update-

[RFC PATCH v8 2/6] linux-headers: Update to Linux v6.15-rc3

Update headers to retrieve uapi information for vfio-ap Signed-off-by: Rorie Reyes --- include/standard-headers/asm-x86/setup_data.h | 4 +- include/standard-headers/drm/drm_fourcc.h | 41 ++ include/standard-headers/linux/const.h| 2 +- include/standard-headers/linux/ethtoo

[RFC PATCH v8 0/6] Report vfio-ap configuration changes

Changelog: v8: - fixed windows cross-compile build - moved /hw/vfio/ap-stub.c to /hw/s390x/ap-stub.c - updated the use of stub file to MAINTAINERS to reflect new location - removed if_false for 'CONFIG_VFIO_AP' statement from /hw/vfio/meson.build - added if_false for 'CONFIG_VFIO_AP' to use ap-stub

[RFC PATCH v8 3/6] hw/vfio/ap: notification handler for AP config changed event

Register an event notifier handler to process AP configuration change events by queuing the event and generating a CRW to let the guest know its AP configuration has changed Signed-off-by: Rorie Reyes Reviewed-by: Anthony Krowiak --- hw/vfio/ap.c | 31 +++ 1 file cha

[RFC PATCH v8 5/6] hw/vfio/ap: Storing event information for an AP configuration change event

These functions can be invoked by the function that handles interception of the CHSC SEI instruction for requests indicating the accessibility of one or more adjunct processors has changed. Signed-off-by: Rorie Reyes --- hw/vfio/ap.c | 39 inc

[RFC PATCH v8 6/6] s390: implementing CHSC SEI for AP config change

Handle interception of the CHSC SEI instruction for requests indicating the guest's AP configuration has changed. If configuring --without-default-devices, hw/s390x/ap-stub.c was created to handle such circumstance. Also added the following to hw/s390x/meson.build if CONFIG_VFIO_AP is false, it wi

Re: [PATCH] virtio-gpu-gl: Add 'serverfd' property

On 5/8/25 8:00 PM, Alex Bennée wrote: Jiang XueQian writes: This property passes socket of a externally started virgl_render_server to virglrenderer, so that it won't try to spawn new process and get killed by seccomp, allowing virtio-gpu-gl venus and sandbox to enable at the same time. D

Re: [PATCH v3 10/11] tests: Add iotest mirror-sparse for recent patches

On Thu, Apr 24, 2025 at 07:52:10PM -0500, Eric Blake wrote: > Prove that blockdev-mirror can now result in sparse raw destination > files, regardless of whether the source is raw or qcow2. By making > this a separate test, it was possible to test effects of individual > patches for the various pie

Re: [PULL v2, part1 00/15] Rust changes for 2025-05-06

On Fri, May 9, 2025 at 10:55 AM Paolo Bonzini wrote: > Il ven 9 mag 2025, 16:13 Stefan Hajnoczi ha scritto: >> >> Hi Paolo, >> v1 is already merged. I'm not sure what the purpose of v2 is. It looks >> like you dropped the wasm patches but the reason is unclear to me? > > > Sorry about the confusi

Re: [PATCH v4 10/27] hw/i386/pc: Remove linuxboot.bin

On Thu, 8 May 2025 15:35:33 +0200 Philippe Mathieu-Daudé wrote: > All PC machines now use the linuxboot_dma.bin binary, > we can remove the non-DMA version (linuxboot.bin). > > Suggested-by: Thomas Huth > Signed-off-by: Philippe Mathieu-Daudé > --- > hw/i386/pc.c | 3 +-

Re: [PATCH v4 09/27] hw/nvram/fw_cfg: Remove fw_cfg_io_properties::dma_enabled

On Thu, 8 May 2025 15:35:32 +0200 Philippe Mathieu-Daudé wrote: > Now than all calls to fw_cfg_init_io_dma() pass DMA arguments, > the 'dma_enabled' of the TYPE_FW_CFG_IO type is not used anymore. > Remove it, simplifying fw_cfg_init_io_dma() and fw_cfg_io_realize(). > > Note, we can not remove

Re: [PATCH v4 24/27] hw/intc/ioapic: Remove IOAPICCommonState::version field

On Thu, May 08, 2025 at 03:35:47PM +0200, Philippe Mathieu-Daudé wrote: > Date: Thu, 8 May 2025 15:35:47 +0200 > From: Philippe Mathieu-Daudé > Subject: [PATCH v4 24/27] hw/intc/ioapic: Remove IOAPICCommonState::version > field > X-Mailer: git-send-email 2.47.1 > > The IOAPICCommonState::versio

Re: [PATCH] net/af-xdp: Support pinned map path for AF_XDP sockets

Hi Ilya, On 5/9/25 12:53 AM, Ilya Maximets wrote: On 5/8/25 2:34 PM, Daniel Borkmann wrote: Extend inhibit=on setting with the option to specify a pinned XSK map path along with a starting index (default 0) to push the created XSK sockets into. Example usage: # ./build/qemu-system-x86_64 [.

Re: [PATCH v4 05/27] hw/nvram/fw_cfg: Factor fw_cfg_init_mem_internal() out

On Thu, 8 May 2025 15:35:28 +0200 Philippe Mathieu-Daudé wrote: > Factor fw_cfg_init_mem_internal() out of fw_cfg_init_mem_wide(). > In fw_cfg_init_mem_wide(), assert DMA arguments are provided. > Callers without DMA have to use the fw_cfg_init_mem() helper. > > Signed-off-by: Philippe Mathieu-

Re: [PATCH v4 07/27] hw/i386/x86: Remove X86MachineClass::fwcfg_dma_enabled field

On Fri, 9 May 2025 17:41:25 +0200 Igor Mammedov wrote: > On Thu, 8 May 2025 15:35:30 +0200 > Philippe Mathieu-Daudé wrote: > > > The X86MachineClass::fwcfg_dma_enabled boolean was only used > > by the pc-q35-2.6 and pc-i440fx-2.6 machines, which got > > removed. Remove it and simplify. > > >

Re: [PATCH] migration: Fix migration failure when aia is configured as 'aplic-imsic'

On Fri, May 09, 2025 at 10:08:26AM +0800, liu.xuem...@zte.com.cn wrote: > From: Xuemei Liu > > Address an error in migration by discarding 'riscv_aplic' and 'riscv_imsic' > in vmstate_register_with_alias_id() when aia is configured as > 'aplic-imsic' in riscv kvm vm. > > Previously, the fields i

Re: [PATCH v4 07/27] hw/i386/x86: Remove X86MachineClass::fwcfg_dma_enabled field

On Thu, 8 May 2025 15:35:30 +0200 Philippe Mathieu-Daudé wrote: > The X86MachineClass::fwcfg_dma_enabled boolean was only used > by the pc-q35-2.6 and pc-i440fx-2.6 machines, which got > removed. Remove it and simplify. > > 'multiboot.bin' isn't used anymore, we'll remove it in the > next commi

Re: [PATCH v4 06/27] hw/nvram/fw_cfg: Rename fw_cfg_init_mem_wide() -> fw_cfg_init_mem_dma()

On Fri, 9 May 2025 14:51:07 +0800 Zhao Liu wrote: > On Thu, May 08, 2025 at 03:35:29PM +0200, Philippe Mathieu-Daudé wrote: > > Date: Thu, 8 May 2025 15:35:29 +0200 > > From: Philippe Mathieu-Daudé > > Subject: [PATCH v4 06/27] hw/nvram/fw_cfg: Rename fw_cfg_init_mem_wide() -> > > fw_cfg_init_

Re: [PATCH v4 04/27] hw/mips/loongson3_virt: Prefer using fw_cfg_init_mem_nodma()

On Thu, 8 May 2025 15:35:27 +0200 Philippe Mathieu-Daudé wrote: > fw_cfg_init_mem_wide() is prefered to initialize fw_cfg > with DMA support. Without DMA, use fw_cfg_init_mem_nodma(). > > Signed-off-by: Philippe Mathieu-Daudé Reviewed-by: Igor Mammedov > --- > hw/mips/loongson3_virt.c | 2

Re: [PATCH v4 03/27] hw/nvram/fw_cfg: Rename fw_cfg_init_mem() with '_nodma' suffix

On Thu, 8 May 2025 15:35:26 +0200 Philippe Mathieu-Daudé wrote: > Rename fw_cfg_init_mem() as fw_cfg_init_mem_nodma() > to distinct with the DMA version (currently named > fw_cfg_init_mem_wide). > > Suggested-by: Zhao Liu > Signed-off-by: Philippe Mathieu-Daudé Reviewed-by: Igor Mammedov >

Re: [PATCH v2 1/2] qtest/migration/rdma: Enforce RLIMIT_MEMLOCK >= 128MB requirement

On Fri, May 09, 2025 at 09:42:10AM +0800, Li Zhijian wrote: > Ensure successful migration over RDMA by verifying that RLIMIT_MEMLOCK is > set to at least 128MB. This allocation is necessary due to the requirement > to pin significant portions of guest memory, typically exceeding 100MB > in this tes

Re: [PATCH v2 2/2] qtest/migration/rdma: Add test for rdma migration with ipv6

On Fri, May 09, 2025 at 09:42:11AM +0800, Li Zhijian wrote: > Recently, we removed ipv6 restriction[0] from RDMA migration, add a > test for it. > > [0] > https://lore.kernel.org/qemu-devel/20250326095224.9918-1-jinpu.w...@ionos.com/ > > Cc: Jack Wang > Cc: Michael R. Galaxy > Cc: Peter Xu >

Re: [PATCH] docs/devel/testing/functional: Fix typo

On Fri, 9 May 2025 at 16:22, Gustavo Romero wrote: > > Fix the duplication of the word 'run'. > > Signed-off-by: Gustavo Romero > --- > docs/devel/testing/functional.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/docs/devel/testing/functional.rst > b/docs/devel/tes

Re: [PULL 22/23] tests/function/aspeed: Add functional test for ast2700fc

On Fri, 9 May 2025 at 15:32, Cédric Le Goater wrote: > In the ast2700fc machine and the fby35, each SoC has its own memory > region and, since there is no need for the global system memory > region, it's empty. But in some places, like > rom_check_and_register_reset(), it's a problem for the flatt

Re: [PATCH v4 01/27] hw/i386/pc: Remove deprecated pc-q35-2.6 and pc-i440fx-2.6 machines

On Thu, 8 May 2025 15:35:24 +0200 Philippe Mathieu-Daudé wrote: > These machines has been supported for a period of more than 6 years. > According to our versioned machine support policy (see commit > ce80c4fa6ff "docs: document special exception for machine type > deprecation & removal") they c

Re: [PATCH] system/physmem: Fix UBSan finding in address_space_write_rom_internal

On Tue, May 06, 2025 at 02:21:08PM +0100, Peter Maydell wrote: > On Mon, 5 May 2025 at 23:23, Joe Komlodi wrote: > > > > address_space_write_rom_internal can take in a NULL pointer for ptr if > > it's only doing cache flushes instead of populating the ROM. > > > > However, if building with --enabl

[PATCH] docs/devel/testing/functional: Fix typo

Fix the duplication of the word 'run'. Signed-off-by: Gustavo Romero --- docs/devel/testing/functional.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/devel/testing/functional.rst b/docs/devel/testing/functional.rst index 8030cb4299..9e56dd1b11 100644 --- a/docs/dev

Re: [PATCH v10 3/3] migration: write zero pages when postcopy enabled

On Fri, May 09, 2025 at 11:34:06AM +0530, Prasad Pandit wrote: > > > This patch should come before 1/3, otherwise it'll break bisect. > > We could squash the two together, IMHO. > > * It is adjusting the specific optimisation behaviour for the use case > of when Multifd and Postcopy are enabled to

Re: [PATCH v4 02/27] hw/i386/pc: Remove PCMachineClass::legacy_cpu_hotplug field

On Thu, 8 May 2025 15:35:25 +0200 Philippe Mathieu-Daudé wrote: > The PCMachineClass::legacy_cpu_hotplug boolean was only used > by the pc-q35-2.6 and pc-i440fx-2.6 machines, which got > removed. Remove it and simplify build_dsdt(), removing > build_legacy_cpu_hotplug_aml() altogether. > > Note

Re: [PULL v2, part1 00/15] Rust changes for 2025-05-06

Il ven 9 mag 2025, 16:13 Stefan Hajnoczi ha scritto: > Hi Paolo, > v1 is already merged. I'm not sure what the purpose of v2 is. It looks > like you dropped the wasm patches but the reason is unclear to me? > Sorry about the confusion, I sent this before I found a reproducer for the bug (as a ki

[PATCH v2 0/2] semihosting/uaccess: Compile once

Replace target_ulong -> vaddr/size_t to compile once. since v1: - fixed build error when TCG disabled (Pierrick) Philippe Mathieu-Daudé (2): semihosting/uaccess: Remove uses of target_ulong type semihosting/uaccess: Compile once include/semihosting/uaccess.h | 12 ++-- semihosting/u

Re: [PATCH for-10.1 06/10] ui/vdagent: replace Buffer with GByteArray

Hi On Fri, May 9, 2025 at 3:31 PM Daniel P. Berrangé wrote: > > On Tue, Mar 11, 2025 at 07:59:28PM +0400, marcandre.lur...@redhat.com wrote: > > From: Marc-André Lureau > > > > Buffer is slightly more advanced than GByteArray, since it has a > > cursor/position. But vdagent code doesn't need it.

Re: [PULL 22/23] tests/function/aspeed: Add functional test for ast2700fc

On 5/6/25 16:22, Peter Maydell wrote: On Mon, 5 May 2025 at 10:12, Cédric Le Goater wrote: From: Steven Lee 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 Change-Id: I3855f55c9f6e5cca

  1   2   3   >