virgl_renderer_resource_get_info() returns errno and not -1 on error.
Correct the return-value check.
Reviewed-by: Marc-André Lureau
Signed-off-by: Dmitry Osipenko
---
v2: - Fixed similar incorrect error-checking in vhost-user-gpu
- Added r-b from Marc
contrib/vhost-user-gpu/virgl.c | 6 +
On Mon, Jan 29, 2024 at 01:41:01AM +, Liu, Yuan1 wrote:
> Because this change has an impact on the previous live migration
> With IAA Patch, does the submission of the next version needs
> to be submitted based on this change?
I'd say hold off a little while until we're more certain on the p
On Sun, Jan 28, 2024 at 2:10 AM Dmitry Osipenko
wrote:
>
> virgl_renderer_resource_get_info() returns errno and not -1 on error.
> Correct the return-value check.
>
> Signed-off-by: Dmitry Osipenko
Reviewed-by: Marc-André Lureau
Can you also correct the code in vhost-user-gpu ?
> ---
> hw/di
On Fri, Jan 26, 2024 at 07:19:39PM -0300, Fabiano Rosas wrote:
> +static MultiFDMethods multifd_socket_ops = {
> +.send_setup = multifd_socket_send_setup,
> +.send_cleanup = multifd_socket_send_cleanup,
> +.send_prepare = multifd_socket_send_prepare,
Here it's named with "socket", howe
28.01.2024 23:22, Sven Schnelle :
When the maximum count of SCRIPTS instructions is reached, the code
stops execution and returns, but fails to decrement the reentrancy
counter. This effectively renders the SCSI controller unusable
because on next entry the reentrancy counter is still above the l
28.01.2024 10:15, Akihiko Odaki:
qemu_smbios_type8_opts did not the list terminator and that resulted in
out-of-bound memory access. qemu_smbios_type8_opts also needs to have
an element for the type option.
With the same description fix as in 1/1,
Reviewed-by: Michael Tokarev
/mjt
Thomas Huth writes:
> On 28/01/2024 21.22, Sven Schnelle wrote:
>> When the maximum count of SCRIPTS instructions is reached, the code
>> stops execution and returns, but fails to decrement the reentrancy
>> counter. This effectively renders the SCSI controller unusable
>> because on next entry t
28.01.2024 10:15, Akihiko Odaki:
qemu_smbios_type11_opts did not the list terminator and that resulted in
..did not *have* the list terminator.., here and in 2/2.
out-of-bound memory access. qemu_smbios_type11_opts also needs to have
an element for the type option.
Fixes: 2d6dcbf93fb0 ("smbi
I tested the unit test cases with "make check" and result looks good.
Tested-by: Xiaoling Song
Regards,
Xiaoling
On 1/18/2024 10:48 PM, Zhao Liu wrote:
From: Zhao Liu
Hi list,
Currently, test-smp-parse lacks the following cases:
* The case to cover drawer and book parameters parsing in -sm
The latest version of qemu (v8.2.0-869-g7a1dc45af5) crashes when booting
the mcimx7d-sabre emulation with Linux v5.11 and later.
qemu-system-arm: ../system/memory.c:2750: memory_region_set_alias_offset:
Assertion `mr->alias' failed.
Problem is that the Designware PCIe emulation accepts the full
On Sat, Jan 27, 2024 at 11:11:58AM -0800, Guenter Roeck wrote:
> Hi,
>
> On Mon, Jan 08, 2024 at 02:03:25PM +, Nikita Ostrenkov wrote:
> > Signed-off-by: Nikita Ostrenkov
> > ---
>
> This patch, with the "sabrelite" emulation and the Linux upstream kernel
> (v6.8-rc1, using imx_v6_v7_defconf
Hi Jee Heng,
On Sun, Jan 28, 2024 at 06:14:39PM -0800, Sia Jee Heng wrote:
> RISC-V should also generate the SPCR in a manner similar to ARM.
> Therefore, instead of replicating the code, relocate this function
> to the common AML build.
>
> Signed-off-by: Sia Jee Heng
> ---
> hw/acpi/aml-build
Reviewed-by: Pavel Dovgalyuk
On 25.01.2024 19:08, Nicholas Piggin wrote:
This runs replay-dump.py after recording a trace, and fails the test if
the script fails.
replay-dump.py is modified to exit with non-zero if an error is
encountered while parsing, to support this.
Signed-off-by: Nichola
Reviewed-by: Pavel Dovgalyuk
On 25.01.2024 19:08, Nicholas Piggin wrote:
When replaying a trace, it is possible to go from shutdown to
running with a reverse-debugging step. This can be useful if the
problem being debugged triggers a reset or shutdown.
Signed-off-by: Nicholas Piggin
---
inc
On 26/01/2024 23.04, Philippe Mathieu-Daudé wrote:
Mechanical patch produced running the command documented
in scripts/coccinelle/cpu_env.cocci_template header.
Signed-off-by: Philippe Mathieu-Daudé
---
target/s390x/cpu-dump.c| 3 +--
target/s390x/gdbstub.c | 6 ++
tar
On 26/01/2024 23.03, Philippe Mathieu-Daudé wrote:
Mechanical patch produced running the command documented
in scripts/coccinelle/cpu_env.cocci_template header.
Signed-off-by: Philippe Mathieu-Daudé
---
target/m68k/cpu.c | 30 ++
target/m68k/gdbstub.c | 6
On Sun, Jan 28, 2024 at 05:43:52PM +0200, Avihai Horon wrote:
>
> On 25/01/2024 22:57, Fabiano Rosas wrote:
> > External email: Use caution opening links or attachments
> >
> >
> > Avihai Horon writes:
> >
> > > The commit in the fixes line moved multifd thread creation to a
> > > different lo
On 28/01/2024 21.22, Sven Schnelle wrote:
When the maximum count of SCRIPTS instructions is reached, the code
stops execution and returns, but fails to decrement the reentrancy
counter. This effectively renders the SCSI controller unusable
because on next entry the reentrancy counter is still abo
On Sat, Jan 27, 2024 at 01:08:02PM +, Peter Maydell wrote:
> On Fri, 26 Jan 2024 at 20:49, Markus Armbruster wrote:
> >
> > Peter Maydell writes:
> >
> > > Hi; one of the "bitesized tasks" we have listed is to convert
> > > watchdog timers which directly call qemu_system_reset_request() on
>
I'm not super familiar with how QEMU models PCI controllers, but I'm not
sure this handling of the root port config registers is right. On other
controllers it looks like the root config reads and writes are handled
by setting the PCIDeviceClass::config_read and PCIDevice::config_write
methods.
From: Fabiano Rosas
The migration tests have support for being passed two QEMU binaries to
test migration compatibility.
Add a CI job that builds the lastest release of QEMU and another job
that uses that version plus an already present build of the current
version and run the migration tests wi
From: Peter Xu
When the migration frameworks fetches the exact pending sizes, it means
this check:
remaining_size < s->threshold_size
Must have been done already, actually at migration_iteration_run():
if (must_precopy <= s->threshold_size) {
qemu_savevm_state_pending_exact(&must
From: Peter Xu
RAM_SAVE_FLAG_MEM_SIZE contains the total length of ramblock idstr to know
whether scanning of ramblocks is complete. Drop the trick.
Reviewed-by: Fabiano Rosas
Link: https://lore.kernel.org/r/20240117075848.139045-4-pet...@redhat.com
Signed-off-by: Peter Xu
---
scripts/analyz
From: Paolo Bonzini
There is no need to use the Linux-internal __u64 type, 1ULL is
guaranteed to be wide enough.
Signed-off-by: Paolo Bonzini
Reviewed-by: Philippe Mathieu-Daudé
Link: https://lore.kernel.org/r/20240117160313.175609-1-pbonz...@redhat.com
Signed-off-by: Peter Xu
---
migration/
From: Fabiano Rosas
We're currently allowing the process_incoming_migration_bh bottom-half
to run without holding a reference to the 'current_migration' object,
which leads to a segmentation fault if the BH is still live after
migration_shutdown() has dropped the last reference to
current_migrati
From: Fabiano Rosas
Until 9.0 is out, we need to keep the aarch64 job disabled because the
tests always use the n-1 version of migration-test. That happens to be
broken for aarch64 in 8.2. Once 9.0 is out, it will become the n-1
version and it will bring the fixed tests.
We can revert this patch
From: Het Gala
'uri' argument should be optional, as 'uri' and 'channels'
arguments are mutally exclusive in nature.
Fixes: 074dbce5fcce (migration: New migrate and migrate-incoming argument
'channels')
Signed-off-by: Het Gala
Link: https://lore.kernel.org/r/20240123064219.40514-1-het.g...@nut
From: Fabiano Rosas
We need to hold a reference to the current_migration object around
async calls to avoid it been freed while still in use.
Signed-off-by: Fabiano Rosas
Link: https://lore.kernel.org/r/20240119233922.32588-3-faro...@suse.de
Signed-off-by: Peter Xu
---
migration/migration.c |
From: Fabiano Rosas
We need to hold a reference to the current_migration object around
async calls to avoid it been freed while still in use. Even on this
load-side function, we might still use the MigrationState, e.g to
check for capabilities.
Signed-off-by: Fabiano Rosas
Link: https://lore.ke
From: Fabiano Rosas
Stop using outside knowledge about the io channels when registering
yank functions. Query for features instead.
The yank method for all channels used with migration code currently is
to call the qio_channel_shutdown() function, so query for
QIO_CHANNEL_FEATURE_SHUTDOWN. We co
From: Fabiano Rosas
Wrap qemu_bh_schedule() to ensure we always hold a reference to the
current_migration object.
Signed-off-by: Fabiano Rosas
Link: https://lore.kernel.org/r/20240119233922.32588-5-faro...@suse.de
Signed-off-by: Peter Xu
---
migration/migration.c | 31 ++--
From: Peter Xu
It's always used to compare against another uint64_t. Make it always clear
that it's never a negative.
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Fabiano Rosas
Link: https://lore.kernel.org/r/20240117075848.139045-2-pet...@redhat.com
Signed-off-by: Peter Xu
---
migratio
From: Markus Armbruster
hmp_migrate() leaks @caps when qmp_migrate() fails. Plug the leak
with g_autoptr().
Fixes: 967f2de5c9ec (migration: Implement MigrateChannelList to hmp migration
flow.) v8.2.0-rc0
Fixes: CID 1533125
Signed-off-by: Markus Armbruster
Link: https://lore.kernel.org/r/20240
From: Fabiano Rosas
Now that the migration state reference counting is correct, further
wrap the bottom half dispatch process to avoid future issues.
Move BH creation and scheduling together and wrap the dispatch with an
intermediary function that will ensure we always keep the ref/unref
balance
From: Peter Xu
The following changes since commit 7a1dc45af581d2b643cdbf33c01fd96271616fbd:
Merge tag 'pull-target-arm-20240126' of
https://git.linaro.org/people/pmaydell/qemu-arm into staging (2024-01-26
18:16:35 +)
are available in the Git repository at:
https://gitlab.com/peterx/q
On Fri, Jan 26, 2024 at 11:54:32AM -0300, Fabiano Rosas wrote:
> Peter Maydell writes:
>
> > On Fri, 26 Jan 2024 at 14:36, Fabiano Rosas wrote:
> >>
> >> pet...@redhat.com writes:
> >>
> >> > From: Fabiano Rosas
> >> >
> >> > The 'max' cpu is not expected to be stable in terms of features acros
On 1/26/2024 9:57 PM, David Hildenbrand wrote:
uint8_t memory_region_get_dirty_log_mask(MemoryRegion *mr)
{
uint8_t mask = mr->dirty_log_mask;
diff --git a/system/physmem.c b/system/physmem.c
index c1b22bac77c2..4735b0462ed9 100644
--- a/system/physmem.c
+++ b/system/physmem.c
@@ -1841,
On 1/26/2024 10:58 PM, David Hildenbrand wrote:
On 25.01.24 04:22, Xiaoyao Li wrote:
By default (due to the recent UPM change), restricted memory attribute is
shared. Convert the memory region from shared to private at the memory
slot creation time.
add kvm region registering function to check
Generate Serial Port Console Redirection Table (SPCR) for RISC-V
virtual machine.
Signed-off-by: Sia Jee Heng
Reviewed-by: Daniel Henrique Barboza
---
hw/riscv/virt-acpi-build.c | 39 ++
1 file changed, 39 insertions(+)
diff --git a/hw/riscv/virt-acpi-build.
RISC-V should also generate the SPCR in a manner similar to ARM.
Therefore, instead of replicating the code, relocate this function
to the common AML build.
Signed-off-by: Sia Jee Heng
---
hw/acpi/aml-build.c | 51
hw/arm/virt-acpi-build.c| 68 +++
This series focuses on enabling the Serial Port Console Redirection (SPCR)
table for the RISC-V virt platform. Considering that ARM utilizes the same
function, the initial patch involves migrating the build_spcr function to
common code. This consolidation ensures that RISC-V avoids duplicating the
> -Original Message-
> From: Fabiano Rosas
> Sent: Saturday, January 27, 2024 6:20 AM
> To: qemu-devel@nongnu.org
> Cc: Peter Xu ; Hao Xiang ;
> Liu, Yuan1 ; Bryan Zhang
> Subject: [PATCH 0/5] migration/multifd: Prerequisite cleanups for ongoing
> work
>
> Hi,
>
> Here are two cleanups
When the maximum count of SCRIPTS instructions is reached, the code
stops execution and returns, but fails to decrement the reentrancy
counter. This effectively renders the SCSI controller unusable
because on next entry the reentrancy counter is still above the limit.
This bug was seen on HP-UX 10
From: Ari Sundholm
There is a bug in the blklogwrites driver pertaining to logging "write
zeroes" operations, causing log corruption. This can be easily observed
by setting detect-zeroes to something other than "off" for the driver.
The issue is caused by a concurrency bug pertaining to the fact
From: Max Filippov
r[id]tlb[01], [iw][id]tlb opcodes use TLB way index passed in a register
by the guest. The host uses 3 bits of the index for ITLB indexing and 4
bits for DTLB, but there's only 7 entries in the ITLB array and 10 in
the DTLB array, so a malicious guest may trigger out-of-bound a
From: Max Filippov
r[id]tlb[01], [iw][id]tlb opcodes use TLB way index passed in a register
by the guest. The host uses 3 bits of the index for ITLB indexing and 4
bits for DTLB, but there's only 7 entries in the ITLB array and 10 in
the DTLB array, so a malicious guest may trigger out-of-bound a
From: Peter Maydell
In commit 1b7bc9b5c8bf374dd we changed handle_vec_simd_sqshrn() so
that instead of starting with a 0 value and depositing in each new
element from the narrowing operation, it instead started with the raw
result of the narrowing operation of the first element.
This is fine in
From: Akihiko Odaki
Coroutine may be pooled even after COROUTINE_TERMINATE if
CONFIG_COROUTINE_POOL is enabled and fake stack should be saved in
such a case to keep AddressSanitizerUseAfterReturn working. Even worse,
I'm seeing stack corruption without fake stack being saved.
Signed-off-by: Akih
From: Fiona Ebner
Using fleecing backup like in [0] on a qcow2 image (with metadata
preallocation) can lead to the following assertion failure:
> bdrv_co_do_block_status: Assertion `!(ret & BDRV_BLOCK_ZERO)' failed.
In the reproducer [0], it happens because the BDRV_BLOCK_RECURSE flag
will be s
From: Ari Sundholm
There is a bug in the blklogwrites driver pertaining to logging "write
zeroes" operations, causing log corruption. This can be easily observed
by setting detect-zeroes to something other than "off" for the driver.
The issue is caused by a concurrency bug pertaining to the fact
From: Stefan Hajnoczi
Add a filter function for QMP responses that contain QEMU's
automatically generated node ids. The ids change between runs and must
be masked in the reference output.
The next commit will use this new function.
Signed-off-by: Stefan Hajnoczi
Message-ID: <20240118144823.149
From: Joseph Burt
When tcg_out_qemu_st_{index,direct} were merged, the direct case for
MO_64 was omitted, causing qemu_st_i64 to be encoded as 0x due
to underflow when adding h.base and h.index.
Fixes: 1df6d611bdc2 ("tcg/arm: Introduce HostAddress")
Signed-off-by: Joseph Burt
Message-Id
From: Paolo Bonzini
This is causing regressions that have not been analyzed yet. Revert the
change on stable branches.
Cc: qemu-sta...@nongnu.org
Cc: Michael Tokarev
Related: https://gitlab.com/qemu-project/qemu/-/issues/2092
Signed-off-by: Paolo Bonzini
Signed-off-by: Michael Tokarev
diff
From: Stefan Hajnoczi
monitor_qmp_dispatcher_co() runs in the iohandler AioContext that is not
polled during nested event loops. The coroutine currently reschedules
itself in the main loop's qemu_aio_context AioContext, which is polled
during nested event loops. One known problem is that QMP devi
From: Peter Maydell
A typo in the implementation of isar_feature_aa64_tidcp1() means we
were checking the field in the wrong ID register, so we might have
provided the feature on CPUs that don't have it and not provided
it on CPUs that should have it. Correct this bug.
Cc: qemu-sta...@nongnu.org
From: Joseph Burt
When tcg_out_qemu_st_{index,direct} were merged, the direct case for
MO_64 was omitted, causing qemu_st_i64 to be encoded as 0x due
to underflow when adding h.base and h.index.
Fixes: 1df6d611bdc2 ("tcg/arm: Introduce HostAddress")
Signed-off-by: Joseph Burt
Message-Id
From: Daniel P. Berrangé
On a loaded system with --enable-debug, this test can take longer than
5 minutes. Raising the timeout to 6 minutes gives greater headroom for
such situations.
Signed-off-by: Daniel P. Berrangé
[thuth: Increase the timeout to 6 minutes for very loaded systems]
Signed-off
From: Peter Maydell
In commit 1b7bc9b5c8bf374dd we changed handle_vec_simd_sqshrn() so
that instead of starting with a 0 value and depositing in each new
element from the narrowing operation, it instead started with the raw
result of the narrowing operation of the first element.
This is fine in
From: Daniel P. Berrangé
On a loaded system with --enable-debug, this test can take longer than
5 minutes. Raising the timeout to 6 minutes gives greater headroom for
such situations.
Signed-off-by: Daniel P. Berrangé
[thuth: Increase the timeout to 6 minutes for very loaded systems]
Signed-off
From: Robbin Ehn
Commit f4e1168198 (linux-user: Split out host_sig{segv,bus}_handler)
introduced a bug, when returning from host_sigbus_handler the PC is
never set. Thus cpu_loop_exit_restore is called with a zero PC and
we immediate get a SIGSEGV.
Signed-off-by: Robbin Ehn
Fixes: f4e1168198 ("
From: Jason Wang
When HASH_REPORT is negotiated, the guest_hdr_len might be larger than
the size of the mergeable rx buffer header. Using
virtio_net_hdr_mrg_rxbuf during the header swap might lead a stack
overflow in this case. Fixing this by using virtio_net_hdr_v1_hash
instead.
Reported-by: Xi
From: Fiona Ebner
Using fleecing backup like in [0] on a qcow2 image (with metadata
preallocation) can lead to the following assertion failure:
> bdrv_co_do_block_status: Assertion `!(ret & BDRV_BLOCK_ZERO)' failed.
In the reproducer [0], it happens because the BDRV_BLOCK_RECURSE flag
will be s
The following patches are queued for QEMU stable v8.2.1:
https://gitlab.com/qemu-project/qemu/-/commits/staging-8.2
Patch freeze is 2024-01-27 (frozen), and the release is planned for 2024-01-29:
https://wiki.qemu.org/Planning/8.2
This series includes the edk2 changes (moving edk2 binaries
From: Ani Sinha
By default, the timeout to receive any specified event from the QEMU VM is 60
seconds set by the python avocado test framework. Please see event_wait() and
events_wait() in python/qemu/machine/machine.py. If the matching event is not
triggered within that interval, an asyncio.Time
From: Stefan Hajnoczi
The common.qemu bash functions allow tests to interact with the QMP
monitor of a QEMU process. I spent two days trying to update 141 when
the order of the test output changed, but found it would still fail
occassionally because printf() and QMP events race with synchronous Q
From: Richard Henderson
A typo in sizeof_reg put the registers at the wrong offset.
Simplify the expressions to use positive addresses from the
start of uc_mcontext instead of negative addresses from the
end of uc_mcontext.
Reported-by: Vineet Gupta
Reviewed-by: Philippe Mathieu-Daudé
Reviewe
From: Richard Henderson
While the format names the second vector register 'v3',
it is still in the second position (bits 12-15) and
the argument to RXB must match.
Example error:
- e7 00 00 10 2a 33 verllf %v16,%v0,16
+ e7 00 00 10 2c 33 verllf %v16,%v16,16
Cc: qemu-sta...@n
From: Jason Wang
When HASH_REPORT is negotiated, the guest_hdr_len might be larger than
the size of the mergeable rx buffer header. Using
virtio_net_hdr_mrg_rxbuf during the header swap might lead a stack
overflow in this case. Fixing this by using virtio_net_hdr_v1_hash
instead.
Reported-by: Xi
From: Stefan Hajnoczi
Add a filter function for QMP responses that contain QEMU's
automatically generated node ids. The ids change between runs and must
be masked in the reference output.
The next commit will use this new function.
Signed-off-by: Stefan Hajnoczi
Message-ID: <20240118144823.149
From: Stefan Hajnoczi
The common.qemu bash functions allow tests to interact with the QMP
monitor of a QEMU process. I spent two days trying to update 141 when
the order of the test output changed, but found it would still fail
occassionally because printf() and QMP events race with synchronous Q
From: Alex Bennée
This is now expected by rtd so I've expanded using their example as
22.04 is one of our supported platforms. I tried to work out if there
was an easy way to re-generate a requirements.txt from our
pythondeps.toml but in the end went for the easier solution.
Cc:
Signed-off-by:
From: Stefan Hajnoczi
monitor_qmp_dispatcher_co() runs in the iohandler AioContext that is not
polled during nested event loops. The coroutine currently reschedules
itself in the main loop's qemu_aio_context AioContext, which is polled
during nested event loops. One known problem is that QMP devi
From: Daniel P. Berrangé
On a loaded system with --enable-debug, this test can take longer than
5 minutes. Raising the timeout to 6 minutes gives greater headroom for
such situations.
Signed-off-by: Daniel P. Berrangé
[thuth: Increase the timeout to 6 minutes for very loaded systems]
Signed-off
From: Stefan Hajnoczi
The common.qemu bash functions allow tests to interact with the QMP
monitor of a QEMU process. I spent two days trying to update 141 when
the order of the test output changed, but found it would still fail
occassionally because printf() and QMP events race with synchronous Q
The following patches are queued for QEMU stable v8.1.5:
https://gitlab.com/qemu-project/qemu/-/commits/staging-8.1
Patch freeze is 2024-01-27 (frozen), and the release is planned for 2024-01-29:
https://wiki.qemu.org/Planning/8.1
Please respond here or CC qemu-sta...@nongnu.org on any addi
From: Jason Wang
When HASH_REPORT is negotiated, the guest_hdr_len might be larger than
the size of the mergeable rx buffer header. Using
virtio_net_hdr_mrg_rxbuf during the header swap might lead a stack
overflow in this case. Fixing this by using virtio_net_hdr_v1_hash
instead.
Reported-by: Xi
From: Paolo Bonzini
This is causing regressions that have not been analyzed yet. Revert the
change on stable branches.
Cc: qemu-sta...@nongnu.org
Cc: Michael Tokarev
Related: https://gitlab.com/qemu-project/qemu/-/issues/2092
Signed-off-by: Paolo Bonzini
Signed-off-by: Michael Tokarev
diff
From: Fiona Ebner
Using fleecing backup like in [0] on a qcow2 image (with metadata
preallocation) can lead to the following assertion failure:
> bdrv_co_do_block_status: Assertion `!(ret & BDRV_BLOCK_ZERO)' failed.
In the reproducer [0], it happens because the BDRV_BLOCK_RECURSE flag
will be s
The following patches are queued for QEMU stable v7.2.9:
https://gitlab.com/qemu-project/qemu/-/commits/staging-7.2
Patch freeze is 2024-01-27 (frozen), and the release is planned for 2024-01-29:
https://wiki.qemu.org/Planning/7.2
Please respond here or CC qemu-sta...@nongnu.org on any addi
From: Max Filippov
r[id]tlb[01], [iw][id]tlb opcodes use TLB way index passed in a register
by the guest. The host uses 3 bits of the index for ITLB indexing and 4
bits for DTLB, but there's only 7 entries in the ITLB array and 10 in
the DTLB array, so a malicious guest may trigger out-of-bound a
From: Stefan Hajnoczi
monitor_qmp_dispatcher_co() runs in the iohandler AioContext that is not
polled during nested event loops. The coroutine currently reschedules
itself in the main loop's qemu_aio_context AioContext, which is polled
during nested event loops. One known problem is that QMP devi
From: Paolo Bonzini
This is causing regressions that have not been analyzed yet. Revert the
change on stable branches.
Cc: qemu-sta...@nongnu.org
Cc: Michael Tokarev
Related: https://gitlab.com/qemu-project/qemu/-/issues/2092
Signed-off-by: Paolo Bonzini
Signed-off-by: Michael Tokarev
diff
From: Ari Sundholm
There is a bug in the blklogwrites driver pertaining to logging "write
zeroes" operations, causing log corruption. This can be easily observed
by setting detect-zeroes to something other than "off" for the driver.
The issue is caused by a concurrency bug pertaining to the fact
From: Stefan Hajnoczi
Add a filter function for QMP responses that contain QEMU's
automatically generated node ids. The ids change between runs and must
be masked in the reference output.
The next commit will use this new function.
Signed-off-by: Stefan Hajnoczi
Message-ID: <20240118144823.149
From: Alex Bennée
This is now expected by rtd so I've expanded using their example as
22.04 is one of our supported platforms. I tried to work out if there
was an easy way to re-generate a requirements.txt from our
pythondeps.toml but in the end went for the easier solution.
Cc:
Signed-off-by:
On 28/1/24 17:41, Philippe Mathieu-Daudé wrote:
On 28/1/24 05:41, Richard Henderson wrote:
From: Anton Johansson
Uninlines the target-defined cpu_mmu_index() function by moving its
definition to target/*/cpu.c. This allows for compiling memory access
functions in accel/tcg/cputlb.c without ha
On 28/1/24 05:41, Richard Henderson wrote:
From: Anton Johansson
Uninlines the target-defined cpu_mmu_index() function by moving its
definition to target/*/cpu.c. This allows for compiling memory access
functions in accel/tcg/cputlb.c without having to know target specifics.
Signed-off-by: An
On 28/1/24 05:41, Richard Henderson wrote:
Collect some patch sets, cherry-pick from others, with a few
changes of my own. Patches that lack review:
26-include-qemu-Add-TCGCPUOps-typedef-to-typedefs.h.patch
27-target-loongarch-Constify-loongarch_tcg_ops.patch
28-accel-tcg-Use-CPUState.
On 28/1/24 05:41, Richard Henderson wrote:
From: Anton Johansson
Functions are target independent.
Signed-off-by: Anton Johansson
Message-Id: <20240119144024.14289-17-a...@rev.ng>
Reviewed-by: Richard Henderson
Signed-off-by: Richard Henderson
---
include/exec/cpu-all.h| 25 --
On 28/1/24 05:41, Richard Henderson wrote:
From: Philippe Mathieu-Daudé
Replace the manual rcu_read_(un)lock calls in cpu_exec().
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20240124074201.8239-2-phi...@linaro.org>
[rth: Use RCU_READ_LOCK_GUARD not WITH_RCU_READ_LOCK_GUARD]
Reviewed-
On 28/1/24 05:42, Richard Henderson wrote:
QEMU coding style recommends using structure typedefs.
Signed-off-by: Richard Henderson
---
include/hw/core/cpu.h | 5 +
include/qemu/typedefs.h| 1 +
bsd-user/signal.c | 4 ++--
linux-user/signal.c| 4 ++--
target/a
On 27/1/24 13:21, Zhao Liu wrote:
Hi Philippe,
On Fri, Jan 26, 2024 at 11:03:52PM +0100, Philippe Mathieu-Daudé wrote:
Date: Fri, 26 Jan 2024 23:03:52 +0100
From: Philippe Mathieu-Daudé
Subject: [PATCH v2 10/23] target/i386: Prefer fast cpu_env() over slower
CPU QOM cast macro
X-Mailer: git-
On 25/01/2024 22:57, Fabiano Rosas wrote:
External email: Use caution opening links or attachments
Avihai Horon writes:
The commit in the fixes line moved multifd thread creation to a
different location, but forgot to move the p->running = true assignment
as well. Thus, p->running is set t
On Fri, 2024-01-26 at 17:51 +0100, Thomas Huth wrote:
> On 25/01/2024 01.38, Jason Wang wrote:
> > On Wed, Jan 24, 2024 at 9:14 PM David Woodhouse wrote:
> > >
> > > Hi Jason,
> > >
> > > I think this series probably lives or dies with you. I think it's a
> > > worthwhile cleanup, but I no longe
On 2024/01/24 19:40, Laurent Vivier wrote:
On resume e1000e_vm_state_change() always calls e1000e_autoneg_resume()
that sets link_down to false, and thus activates the link even
if we have disabled it.
The problem can be reproduced starting qemu in paused state (-S) and
then set the link to down
On 2024/01/24 19:29, Laurent Vivier wrote:
On resume igb_vm_state_change() always calls igb_autoneg_resume()
that sets link_down to false, and thus activates the link even
if we have disabled it.
The problem can be reproduced starting qemu in paused state (-S) and
then set the link to down. When
On Fri, Jan 26, 2024 at 11:04:03PM +0100, Philippe Mathieu-Daudé wrote:
> Mechanical patch produced running the command documented
> in scripts/coccinelle/cpu_env.cocci_template header.
>
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> target/tricore/cpu.c | 20
> targ
misa_mxl_max is now a class member and initialized only once for each
class. This also moves the initialization of gdb_core_xml_file which
will be referenced before realization in the future.
Signed-off-by: Akihiko Odaki
Reviewed-by: Alistair Francis
---
target/riscv/cpu.c | 21
misa_mxl_max is common for all instances of a RISC-V CPU class so they
are better put into class.
Signed-off-by: Akihiko Odaki
Reviewed-by: Alistair Francis
---
target/riscv/cpu.h | 4 +-
hw/riscv/boot.c| 3 +-
target/riscv/cpu.c | 162 ---
It is initialized with a simple assignment and there is little room for
error. In fact, the validation is even more complex.
Signed-off-by: Akihiko Odaki
Acked-by: LIU Zhiwei
Reviewed-by: Daniel Henrique Barboza
Acked-by: Alistair Francis
---
target/riscv/tcg/tcg-cpu.c | 15 +++
1
1 - 100 of 101 matches
Mail list logo
