This patch should be applicable to the stable releases as well, as the issue
has existed since a while back.
Best regards
Mikael Szreder
On February 15, 2025 8:58:09 PM GMT+01:00, Richard Henderson
wrote:
>On 2/13/25 23:03, Mikael Szreder wrote:
>> The gdbstub implementation for
. For example, the register index of f32 is 64
and f34 is 65.
Fixes: 30038fd81808 ("target-sparc: Change fpr representation to doubles.")
Signed-off-by: Mikael Szreder
---
target/sparc/gdbstub.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/ta
gdb/features/sparc/sparc64-fpu.xml;h=8710585774d821c660af5e76f92707637633daf7;hb=HEAD>
Thanks in advance
Mikael Szreder
On February 13, 2025 5:57:59 PM GMT+01:00, Richard Henderson
wrote:
>On 2/3/25 06:50, Mikael Szreder wrote:
>> The gdbstub implementation for the Sparc architecture w
Ping
On February 3, 2025 3:50:56 PM GMT+01:00, Mikael Szreder wrote:
>The gdbstub implementation for the Sparc architecture would incorectly
> calculate the the floating point register offset.
>This would cause register pairs(eg f32,f33) to point to the same value.
>
>Fixe
:
v2:
- Corrected a mistake I made in the FqTOx instruction
- Fixed issues in the FsTOx, FxTOs, FxTOd, FxTOq instructions as well
Mikael Szreder (2):
target/sparc: Fix register selection for the fdtox and fqtox
instructions
target/sparc: Fix register selection for all F*TOx and FxTO
ves: https://gitlab.com/qemu-project/qemu/-/issues/2802
Signed-off-by: Mikael Szreder
---
target/sparc/insns.decode | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/sparc/insns.decode b/target/sparc/insns.decode
index 989c20b44a..694a28d88c 100644
--- a/target/sparc/in
Fixed a mistake I made in the FqTOx instruction.
Fixed issues in the FsTOx, FxTOs, FxTOd, FxTOq instructions.
Fixes: 0bba7572d40d ("target/sparc: Perform DFPREG/QFPREG in decodetree")
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2802
Signed-off-by: Mikael Szreder
---
ta
The gdbstub implementation for the Sparc architecture would incorectly
calculate the the floating point register offset.
This would cause register pairs(eg f32,f33) to point to the same value.
Fixes: 30038fd81808 ("target-sparc: Change fpr representation to doubles.")
Signed-off-
ves: https://gitlab.com/qemu-project/qemu/-/issues/2802
Signed-off-by: Mikael Szreder
---
target/sparc/insns.decode | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/sparc/insns.decode b/target/sparc/insns.decode
index 989c20b44a..694a28d88c 100644
--- a/target/sparc/in
Public bug reported:
Hi,
A big issue when using QEMU's VNC server (VNC KVM) is that, when there's
a network lag, unintended keypresses go through to the QEMU guest VM.
This is frequently "enter" keypresses, causing all kinds of unintended
consequences in the VM. So basically it's extremely dange
What I request seems to be the same option as x11vnc's "-norepeat",
http://linux.die.net/man/1/x11vnc
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1502884
Title:
Super important feature req: QEMU
x27;s spec sheets.
Which one is it?
Kind regards
--
Mikael Åsberg
PhD student (Doktorand), Computer Engineering
School of Innovation, Design and Engineering
Mälardalen University, Västerås Sweden
Phone: +46(0)21 101502
Room nr: U1-145
Mail: mikael.asb...@mdh.se
--
2012/4/10 Mikael
> Hi Jun -
>
> That's the problem - none of this can be done whatsoever with libvirt.
>
> The issue about libvirt is that it is a manager of virtualization programs
> running in separate OS processes. Doing the kind of tight interaction with
> sev
2012/4/10 Mikael
> Hi Jun -
>
> That's the problem - none of this can be done whatsoever with libvirt.
>
> The issue about libvirt is that it is a manager of virtualization programs
> running in separate OS processes. Doing the kind of tight interaction with
> sev
p to
contain/run several qemu instances at the same time.
The rest of the things (IO encapsulation features) already exist in
some form, they just need to be wrapped to into the form of an API rather
than being in the form of internal device drivers only.)
Thanks,
Mikael
Den 10 april 2012 04
lar to Unix' select() and read() for
picking up new data on sockets), that would be incredibly good. (If having
several machines, there could be infinite recursion problems if events are
passed to a callback instead of as a return.)
Looking forward to your response!
Thanks and kind regards,
Mikael
ward to your response!
Thanks and kind regards,
Mikael
17 matches
Mail list logo
