[Qemu-devel] [Bug 1258626] Re: Curses Keyboard Broken On OS X

EDIT: I should have mentioned that this is using QEMU 1.6.1, but the problem also occurs with 1.3.1. Also, in case it makes a difference, I installed QEMU using Homebrew. ** Description changed: Whenever I run ``qemu-system-i386 -curses ...'' (with or without a ``-k en-gb'') on OS X 10.9,

[Qemu-devel] [Bug 1258626] [NEW] Curses Keyboard Broken On OS X

Public bug reported: Whenever I run ``qemu-system-i386 -curses ...'' (with or without a ``-k en-gb'') on OS X 10.9, the keyboard does not work properly. For example, when attempting to switch to the QEMU console with Alt+2, I get: ``Warning: no scancode found for keysym 226 Warning: no scancode

[Qemu-devel] [PATCH v3] Fix linking relocatable objects on Sparc

On Sparc, gcc implicitly passes --relax to the linker, but -r is incompatible with this. Therefore, if --no-relax is supported, it should be passed to the linker. Signed-off-by: James Clarke <jrt...@jrtc27.com> --- Hi Peter, Sorry about that, I wasn't building in a git repository, so

[Qemu-devel] [PATCH v2] Fix linking relocatable objects on Sparc

On Sparc, gcc implicitly passes --relax to the linker, but -r is incompatible with this. Therefore, if --no-relax is supported, it should be passed to the linker. Signed-off-by: James Clarke <jrt...@jrtc27.com> --- Hi Peter, Sorry about that, I wasn't building in a git repository, so

Re: [Qemu-devel] [PATCH v2 2/2] target-ppc: mcrfs should always update FEX/VX and only clear exception bits

> On 31 Jan 2016, at 23:50, David Gibson <da...@gibson.dropbear.id.au> wrote: > On Fri, Jan 29, 2016 at 06:40:21PM +, James Clarke wrote: >> Here is the description of the mcrfs instruction from the PowerPC >> Architecture >> Book, Version 2.02, Book I

[Qemu-devel] [PATCH v2 1/2] target-ppc: Make every FPSCR_ macro have a corresponding FP_ macro

Signed-off-by: James Clarke <jrt...@jrtc27.com> --- target-ppc/cpu.h | 31 ++- 1 file changed, 22 insertions(+), 9 deletions(-) diff --git a/target-ppc/cpu.h b/target-ppc/cpu.h index 9706000..3a967b7 100644 --- a/target-ppc/cpu.h +++ b/target-ppc/cpu.h @@ -

[Qemu-devel] [PATCH v2 0/2] PPC handles mcrfs incorrectly

for submitting such a broken patch. James Clarke (2): target-ppc: Make every FPSCR_ macro have a corresponding FP_ macro target-ppc: mcrfs should always update FEX/VX and only clear exception bits target-ppc/cpu.h | 37 - target-ppc/translate.c | 21

[Qemu-devel] [PATCH v2 2/2] target-ppc: mcrfs should always update FEX/VX and only clear exception bits

such as condition flags not persisting when they should if read, and if you were to read a specific field with some exception bits set, but no others were set in the entire register, then the bits would be cleared correctly, but FEX/VX would not be updated to 0 as they should be. Signed-off-by: J

[Qemu-devel] [PATCH 1/2] target-ppc: Make every FPSCR_ macro have a corresponding FP_ macro

Signed-off-by: James Clarke <jrt...@jrtc27.com> --- target-ppc/cpu.h | 31 ++- 1 file changed, 22 insertions(+), 9 deletions(-) diff --git a/target-ppc/cpu.h b/target-ppc/cpu.h index 9706000..3a967b7 100644 --- a/target-ppc/cpu.h +++ b/target-ppc/cpu.h @@ -

[Qemu-devel] [PATCH 0/2] PPC handles mcrfs incorrectly

me FP_ macros needed to calculate FP_EX_CLEAR_BITS did not exist, and I reordered all the FP_ macros so that they are defined in the same order as the FPSCR_ macros. James Clarke (2): target-ppc: Make every FPSCR_ macro have a corresponding FP_ macro target-ppc: mcrfs should always update FEX/VX

[Qemu-devel] [PATCH 2/2] target-ppc: mcrfs should always update FEX/VX and only clear exception bits

Signed-off-by: James Clarke <jrt...@jrtc27.com> --- target-ppc/cpu.h | 6 ++ target-ppc/translate.c | 15 +++ 2 files changed, 17 insertions(+), 4 deletions(-) diff --git a/target-ppc/cpu.h b/target-ppc/cpu.h index 3a967b7..d811bc9 100644 --- a/target-ppc/cpu.h

[Qemu-devel] [PATCH] Fix linking relocatable objects on Sparc

On Sparc, gcc implicitly passes --relax to the linker, but -r is incompatible with this. Therefore, if --no-relax is supported, it should be passed to the linker. Signed-off-by: James Clarke <jrt...@jrtc27.com> --- configure | 13 + rules.mak | 2 +- 2 files changed, 14 inse

[Qemu-devel] [Bug 1258626] Re: Curses Keyboard Broken On OS X

Yes, I can still reproduce this with 2.8.0, and it gives exactly the same output. ** Changed in: qemu Status: Expired => New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1258626 Title:

[Qemu-devel] [Bug 1643619] Re: netlink broken on big-endian mips

This has been fixed by 40493c5f2b0f124c9b2581e539bba14522e51269, which is exactly the same diff as given here. ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1716767] Re: file(1) fails with "Invalid argument" on qemu-sh4-user

With the attached patch, qemu-sh4-static now works for file: root@debian:/# /usr/bin/qemu-sh4-static.new2 /usr/bin/file /bin/bash /bin/bash: ELF 32-bit LSB executable, Renesas SH, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2,

[Qemu-devel] [PATCH v2] linux-user/syscall.c: Handle SH4's exceptional alignment for p{read, write}64

Fixes: https://bugs.launchpad.net/qemu/+bug/1716767 Signed-off-by: James Clarke <jrt...@jrtc27.com> --- Changes since v1: * Removed all changes in v1 :) * Added syscall num argument to regpairs_aligned * Added SH4-specific implementation of regpairs_aligned to return 1 for p{read,wr

[Qemu-devel] [PATCH v3] linux-user/syscall.c: Handle SH4's exceptional alignment for p{read, write}64

Fixes: https://bugs.launchpad.net/qemu/+bug/1716767 Signed-off-by: James Clarke <jrt...@jrtc27.com> --- Changes since v2: * Fixed opening curly brace formatting, both for my new SH4-specific regpairs_aligned function, as well as the Arm one I touched, to appease checkpatch.pl C

[Qemu-devel] [PATCH] linux-user/syscall.c: Handle SH4's exceptional alignment for p{read, write}64

Fixes: https://bugs.launchpad.net/qemu/+bug/1716767 Signed-off-by: James Clarke <jrt...@jrtc27.com> --- linux-user/syscall.c | 12 1 file changed, 12 insertions(+) diff --git a/linux-user/syscall.c b/linux-user/syscall.c index 9b6364a266..24d6a81c21 100644 --- a/linux-user/sys

[Qemu-devel] [Bug 1594394] Re: Using setreuid / setegid crashes x86_64 user-mode target

What's the status of this? This is causing aptitude in Debian chroots to reliably segfault under qemu-arm-user. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1594394 Title: Using setreuid /

[Qemu-devel] [Bug 1594394] Re: Using setreuid / setegid crashes x86_64 user-mode target

And to confirm, while somewhat of a hack, that patch does indeed fix aptitude as expected (as well as my minimal test case I wrote when debugging this before stumbling upon this bug report). -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to

[Qemu-devel] [Bug 1716767] Re: file(1) fails with "Invalid argument" on qemu-sh4-user

Ok, I was wrong, there's a whole load of code being included inside the function from a header. The issue seems to be the pread: 20771@1505254578.94:guest_user_syscall cpu=0x62850620 num=0x00b4 arg1=0x0003 arg2=0xf6fe6798 arg3=0x0020

[Qemu-devel] [Bug 1716767] Re: file(1) fails with "Invalid argument" on qemu-sh4-user

(Currently regpairs_aligned gets checked, but this, rightly, returns false for SH; alignment is not a requirement of the SH ABI, but p{read,write}64 are an exception for it.) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1716767] Re: file(1) fails with "Invalid argument" on qemu-sh4-user

Bah, and that's "read *from an offset of* 0x34 bytes"; I got confused between count and pos midway through that paragraph. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1716767

[Qemu-devel] [Bug 1716767] Re: file(1) fails with "Invalid argument" on qemu-sh4-user

The "0 == 18446744073709551615 = 0" is actually fine, it's just printing "-1" as a 64-bit unsigned integer. Could you please upload the fill output of `file -d /bin/bash 2>&1`? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1716767] Re: file(1) fails with "Invalid argument" on qemu-sh4-user

I just ran it myself inside and outside the sh4 chroot. The logging output is the same, with the exception of the final line. Something is happening once it's decided it's elf; looking at file_tryelf, my guess is the fstat call is failing[0]. [0]

Re: [Qemu-devel] [PATCH v3] linux-user/syscall.c: Handle SH4's exceptional alignment for p{read, write}64

On 6 Nov 2017, at 19:57, Riku Voipio wrote: > > On Wed, Oct 04, 2017 at 10:38:50AM +0200, John Paul Adrian Glaubitz wrote: >> Hi! >> >> Any chance that this patch gets merged soon? >> >> Looks like it has been reviewed by at least Richard and Philippe. > > Sorry, slipped

[Qemu-devel] [PATCH] slirp: Send window updates to guest after window was closed

If the receive window presented to the guest closes, slirp should send a window update once the window reopens sufficiently, rather than forcing the guest to send a window probe, which can take several seconds. Signed-off-by: James Clarke <jrt...@jrtc27.com> --- Hi, I encountered this

[PATCH] target/mips: Fix ll/sc after 7dd547e5ab6b31e7a0cfc182d3ad131dd55a948f

uglink: https://bugs.launchpad.net/qemu/+bug/1861605 Cc: Aurelien Jarno Cc: Aleksandar Markovic Cc: Aleksandar Rikalo Cc: Richard Henderson Signed-off-by: James Clarke --- target/mips/op_helper.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/target/mips/op_helper.c