When only use PS/2 mouse without usb-tablet, the mouse pointer of the
guest on the VNC will work badly that the cursor of VNC is inconsistent
with the mouse pointer of guest.
The reason is the PS/2 mouse use relative coordinates and we can't know
the initial position of the guest mouse pointer.
Am 10. Juli 2023 16:01:46 UTC schrieb Bernhard Beschow :
>
>
>Am 10. Juli 2023 10:16:35 UTC schrieb "Philippe Mathieu-Daudé"
>:
>>On 9/7/23 10:09, Bernhard Beschow wrote:
>>> Since commit c0a55a0c9da2 "hw/sd/sdhci: Support big endian SD host
>>> controller
>>> interfaces"
15.07.2023 16:52, Richard Henderson wrote:
From: Andreas Schwab
Fixes: 86f04735ac ("linux-user: Fix brk() to release pages")
Signed-off-by: Andreas Schwab
Message-Id:
Reviewed-by: Richard Henderson
Signed-off-by: Richard Henderson
This smells like a stable-8.0 material. Please let me
15.07.2023 16:53, Richard Henderson wrote:
From: Philippe Mathieu-Daudé
Since commit fbd3c4cff6 ("linux-user/arm: Mark the commpage
executable") executing bare-metal (linked with rdimon.specs)
cortex-M code fails as:
$ qemu-arm -cpu cortex-m3 ~/hello.exe.m3
qemu-arm:
On Fri, 14 Jul 2023 at 18:52, Philippe Mathieu-Daudé wrote:
>
> Hi Peter,
>
> On 14/7/23 19:26, Peter Maydell wrote:
> > In CPUSparcState we define the fprs field as uint64_t. However we
> > then refer to it in translate.c via a TCGv_i32 which we set up with
> > tcg_global_mem_new_ptr(). This
Cc'ing more contributors involved with audio in general.
On 13/7/23 13:00, Manos Pitsidianakis wrote:
Ping
Patch series on patchew:
https://patchew.org/QEMU/cover.1686238728.git.manos.pitsidiana...@linaro.org/
Patch series on lore:
On 7/14/23 18:26, Peter Maydell wrote:
+++ b/target/sparc/gdbstub.c
@@ -96,7 +96,10 @@ int sparc_cpu_gdb_read_register(CPUState *cs, GByteArray
*mem_buf, int n)
case 83:
return gdb_get_regl(mem_buf, env->fsr);
case 84:
-return gdb_get_regl(mem_buf, env->fprs);
+
For user-only, the probe for page writability may race with another
thread's mprotect. Take the mmap_lock around the operation. This
is still faster than the start/end_exclusive fallback.
Remove the write probe in load_atomic8_or_exit. There we don't have
the same machinery for testing the
On 7/15/23 14:52, Richard Henderson wrote:
The following changes since commit 4633c1e2c576fbabfe5c8c93f4b842504b69c096:
Merge tag 'for-upstream' ofhttps://gitlab.com/bonzini/qemu into staging
(2023-07-14 16:39:46 +0100)
are available in the Git repository at:
On 7/14/23 16:40, Stefan Berger wrote:
Hello!
This PR removes the 'ppi' boolean property from the tpm tis sysbus
device. It could never be activated since it was leading to a segfault
immediatley.
Stefan
The following changes since commit 3dd9e54703e6ae4f9ab3767f5cecc99edf08:
On 16/7/23 17:35, Thomas Huth wrote:
The firmware of the m68k next-cube machine uses the loopback mode
for self-testing the hardware and currently fails during this step.
By implementing the loopback mode, we can make the firmware pass
to the next step.
Signed-off-by: Thomas Huth
---
On 16/7/23 13:57, Michael Tokarev wrote:
The following changes since commit 7d07a21ec003724475566073404c5893e36de5e5:
tree-wide spelling fixes in comments and some messages: hw/9pfs (2023-07-16
13:59:17 +0300)
are available in the Git repository at:
https://gitlab.com/mjt0k/qemu.git/
When running kvm-unit-tests[1] on current APIC[2], we get a failed test
case related to APIC timer
env QEMU=build/qemu-system-x86_64 ACCEL=tcg ./run_tests.sh -g apic
FAIL: TMCCT should stay at zero
The test case sets the timer mode to oneshot and sets the intial count, it
waits
The firmware of the m68k next-cube machine uses the loopback mode
for self-testing the hardware and currently fails during this step.
By implementing the loopback mode, we can make the firmware pass
to the next step.
Signed-off-by: Thomas Huth
---
hw/char/escc.c | 4 +++-
1 file changed, 3
16.07.2023 14:57, Michael Tokarev пишет:
The following changes since commit 7d07a21ec003724475566073404c5893e36de5e5:
tree-wide spelling fixes in comments and some messages: hw/9pfs (2023-07-16
13:59:17 +0300)
are available in the Git repository at:
https://gitlab.com/mjt0k/qemu.git/
The following changes since commit 7d07a21ec003724475566073404c5893e36de5e5:
tree-wide spelling fixes in comments and some messages: hw/9pfs (2023-07-16
13:59:17 +0300)
are available in the Git repository at:
https://gitlab.com/mjt0k/qemu.git/ tags/trivial-patches-pull
for you to fetch
From: Daniel Henrique Barboza
This is how the content of the "RISC-V CPU firmware" section is
displayed after the html is generated:
"When using the sifive_u or virt machine there are three different
firmware boot options: 1. -bios default - This is the default behaviour
if no -bios option is
Signed-off-by: Michael Tokarev
Reviewed-by: Fabiano Rosas
---
migration/migration-stats.c | 2 +-
migration/migration.h | 4 ++--
migration/multifd-zlib.c| 2 +-
migration/multifd-zstd.c| 2 +-
migration/multifd.c | 2 +-
migration/savevm.c | 2 +-
Signed-off-by: Michael Tokarev
Reviewed-by: Peter Maydell
---
host/include/aarch64/host/cpuinfo.h | 2 +-
hw/arm/aspeed.c | 2 +-
hw/arm/mps2-tz.c | 2 +-
hw/intc/arm_gic.c | 4 ++--
hw/intc/arm_gicv3_redist.c| 2 +-
Signed-off-by: Michael Tokarev
Reviewed-by: Thomas Huth
---
hw/intc/s390_flic_kvm.c | 2 +-
include/hw/s390x/s390-pci-bus.h | 2 +-
include/hw/s390x/sclp.h | 2 +-
target/s390x/cpu_features.c | 2 +-
target/s390x/cpu_models.c| 2 +-
target/s390x/tcg/fpu_helper.c
Signed-off-by: Michael Tokarev
Reviewed-by: Peter Maydell
---
host/include/generic/host/cpuinfo.h | 2 +-
hw/m68k/next-cube.c | 2 +-
hw/m68k/next-kbd.c | 2 +-
hw/m68k/virt.c | 2 +-
Signed-off-by: Michael Tokarev
Reviewed-by: Christian Schoenebeck
---
hw/9pfs/9p-local.c | 8
hw/9pfs/9p-proxy.c | 2 +-
hw/9pfs/9p-synth.c | 2 +-
hw/9pfs/9p-util.h | 2 +-
hw/9pfs/9p.c | 4 ++--
hw/9pfs/9p.h | 2 +-
6 files changed, 10 insertions(+), 10 deletions(-)
Hi all,
The first patch in this series adds a small optimization to VFIO
migration by moving the STOP_COPY->STOP transition to
vfio_save_cleanup(). Testing with a ConnectX-7 VFIO device showed that
this can reduce downtime by up to 6%.
The rest of the series adds P2P support for VFIO migration.
Changing the device state from STOP_COPY to STOP can take time as the
device may need to free resources and do other operations as part of the
transition. Currently, this is done in vfio_save_complete_precopy() and
therefore it is counted in the migration downtime.
To avoid this, change the
From: Joao Martins
Move the PRE_COPY and RUNNING state checks to helper functions.
This is in preparation for adding P2P VFIO migration support, where
these helpers will also test for PRE_COPY_P2P and RUNNING_P2P states.
Signed-off-by: Joao Martins
Signed-off-by: Avihai Horon
---
Add pre VM state change callback to struct VMChangeStateEntry.
The pre VM state change callback is optional and can be set by the new
function qemu_add_vm_change_state_handler_prio_full() that allows
setting this callback in addition to the main callback.
The pre VM state change callbacks and
Add qdev_add_vm_change_state_handler_full() variant that allows setting
a pre VM state change callback in addition to the main callback.
This will facilitate adding P2P support for VFIO migration in the
following patches.
Signed-off-by: Avihai Horon
Signed-off-by: Joao Martins
---
VFIO migration uAPI defines an optional intermediate P2P quiescent
state. While in the P2P quiescent state, P2P DMA transactions cannot be
initiated by the device, but the device can respond to incoming ones.
Additionally, all outstanding P2P transactions are guaranteed to have
been completed by
Now that P2P support has been added to VFIO migration, allow migration
of multiple devices if all of them support P2P migration.
Single device migration is allowed regardless of P2P migration support.
Signed-off-by: Avihai Horon
Signed-off-by: Joao Martins
---
hw/vfio/common.c | 26
29 matches
Mail list logo
