- Original Message -
> From: "Cédric Le Goater"
> To: "Alexey Kardashevskiy" , "Alex Williamson"
> , "Timothy Pearson"
>
> Cc: "l...@suse.de:PowerPC" , "qemu-devel"
> , "Frederic Barrat"
>
Correction -- the desynchronization appears to be on the DisINTx line.
Host:
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- TAbort- SERR- From: "
All,
I've been struggling for some time with what is looking like a potential bug in
QEMU/KVM on the POWER9 platform. It appears that in XIVE mode, when the
in-kernel IRQ chip is enabled, an external device that rapidly asserts IRQs via
the legacy INTx level mechanism will only receive one int
Map signal numbers in fcntl F_SETSIG and F_GETSIG.
Signed-off-by: Timothy E Baldwin
---
linux-user/syscall.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 945fc25279..8456bad109 100644
--- a/linux-user/syscall.c
info->brk was erroneously set to the end of highest addressed
writable segment which could result it in overlapping the executable.
As per load_elf_binary in fs/binfmt_elf.c in Linux, it should be
set to end of highest addressed segment.
Signed-off-by: Timothy E Baldwin
---
linux-u
Public bug reported:
When attempting to pass a Vega 56 GPU to a virtualized guest using QEMU
3.1 on ppc64el (POWER9), the guest is unable to initialize the GPU.
Further digging reveals the driver attempting to allocate a large BAR,
which then fails:
[6.058544] [drm] PCI I/O BAR is not found.
On Mon, 20 Aug 2018, at 10:45 AM, Aleksandar Markovic wrote:
> > As such an implementation of lstat that uses statx will be broken.
> >
> > Since fstatat exists since 2.6.16 this can be reduced to a call to fstatat.
>
> I am not sure what you meant here. I think QEMU lstat() implementation
> do
On 13/08/18 18:53, Aleksandar Markovic wrote:
From: Aleksandar Rikalo
Implement support for translation of system call statx(). The
implementation includes invoking other (more mature) syscalls
(from the same 'stat' family) on the host side. This way,
problems of availability of statx() on the
Is this the correct place to file kvm-pr bug reports?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1738691
Title:
Guest kernel crashes with kvm_pr on POWER8
Status in QEMU:
New
Bug description
Public bug reported:
When attempting to use the kvm_pr module with QEMU 2.10 on a POWER8
host, Debian and Ubuntu guests hang and show crashes.
Host kernel is 4.14. Issue is observed with host kernels 4.9 and 4.13
as well; no other host kernels were tested.
Is this the correct place to report a
Public bug reported:
MTTCG support is notably absent for x86_64 guests. The last Wiki update
on MTTCG was back in 2015, and I am having some difficulty determining
the current status of the underlying requirements to enable this feature
on x86 hosts.
For instance, has support for strong-on-weak
Nope, looks good here. As a note to other commenters, this won't work
unless you are using a kernel compiled with the 4k page size -- default
for PPC64 is 64k.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.ne
Public bug reported:
qemu-x86_66 GIT HEAD fails on a userspace application that requires
memfd_create with:
"qemu: Unsupported syscall: 319".
memfd_create support needs to be implemented in QEMU.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notific
cg/README| 148 +++
> 43 files changed, 7107 insertions(+), 776 deletions(-)
> create mode 100644 tcg/aarch64/tcg-target.opc.h
> create mode 100644 tcg/i386/tcg-target.opc.h
> create mode 100644 tcg/tcg-gvec-desc.h
> create mode 100644 tcg/tcg-op-gvec.h
> create mode 100644 accel/tcg/tcg-runtime-gvec.c
> create mode 100644 tcg/tcg-op-gvec.c
> create mode 100644 tcg/tcg-op-vec.c
>
--
Timothy Pearson
Raptor Engineering
+1 (415) 727-8645 (direct line)
+1 (512) 690-0200 (switchboard)
https://www.raptorengineering.com
Public bug reported:
When attempting to run wineserver on a 64-bit ppc64el host via QEMU's
user-mode i386 emulation, a file locking operation fails.
Command line:
qemu-i386-static /usr/lib/wine-development/wineserver32
Output:
wineserver: fcntl /tmp/.wine-0/server-17-14d21bf/lock: Invalid argume
Still seeing this issue. Only seems to happen with 4K pages on the
host. Any further debugging I could try?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1629618
Title:
QEMU causes host hang / re
Unfortunately, the machine just crashed again. It seems related to the
use of 4K pages instead of the more typical 64K pages; the machine is
rock solid with 64K pages.
** Changed in: qemu
Status: Fix Released => New
--
You received this bug notification because you are a member of qemu-
After running 4.8 for the past week or so I think I can state the
problem is resolved at this point. The machine has not hard reset once
since the update, even after numerous host and VM reboots.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification becaus
Host QEMU version: 1:2.6+dfsg-3.1
Host kernel version: 4.6.0
** Description changed:
QEMU causes a host hang / reset on PPC64EL when used in KVM + HV mode
(kvm_hv module).
After a random amount of uptime, starting new QEMU virtual machines will
cause the host to experience a soft CPU l
Public bug reported:
QEMU causes a host hang / reset on PPC64EL when used in KVM + HV mode
(kvm_hv module).
After a random amount of uptime, starting new QEMU virtual machines will
cause the host to experience a soft CPU lockup. Depending on
configuration and other random factors the host will e
Maydell
Signed-off-by: Timothy Edward Baldwin
---
Changes since v2:
Change do_sigreturn_v2 and do_rt_sigreturn_v2 to pass in context.
Rename frame_addr to context_addr
linux-user/signal.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/linux-user/signal.c
struct target_ucontext_v2 is not at the begining of the signal frame,
therefore do_sigaltstack was being passed bogus arguments.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/signal.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
Changes since v1: Fix style.
diff --git a
struct target_ucontext_v2 is not at the begining of the signal frame,
therefore do_sigaltstack was being passed bogus arguments.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/signal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/signal.c b/linux-user
** Attachment added: "Screenshot showing problem is also present in kernel
framebuffer mode"
https://bugs.launchpad.net/qemu/+bug/1546680/+attachment/4707706/+files/centos-big-endian-display-color-problem-kernel-framebuffer-fedora-24.png
--
You received this bug notification because you are
QEMU emulator version 2.6.0 (Debian 1:2.6+dfsg-3), Copyright (c)
2003-2008 Fabrice Bellard
qemu-system-ppc64 --enable-kvm -M pseries -cpu host -m 3G -cdrom Fedora-
Server-dvd-ppc64-24-1.2.iso
Fedora 24 Server
--
You received this bug notification because you are a member of qemu-
devel-ml, whic
Sounds very relevant, yes. Thanks for the link!
--
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 / setegid crashes x86_64 user-mode target
Status in QEMU:
New
Bug de
I mostly filed the bug report since I was seeing multiple different
attempts to implement this, and even a proper patch series on the
mailing list, but no movement at all toward integrating this feature
into mainline qemu.
What would be needed to e.g. make the patch series on the mailing list
acce
Public bug reported:
When setreuid() or setegid() are called from x86_64 target code in user
mode, qemu crashes inside the NPTL signal handlers. x86 targets do not
directly use a syscall to handle setreuid() / setegid(); instead the x86
NPTL implementation sets up a temporary data region in memor
Public bug reported:
SIMD instructions inside the guest (NEON, MMX, SSE, SSE2, AVX) are
translated to scalar instructions on the host instead of SIMD
instructions. It appears that there have been a few efforts to rectify
this [1], and even a submitted patch series, but all discussion has
effectiv
1. It will only work with open drivers as their IOCTLs are documented.
2. i965+ is only supported. That is any haswell, ivybridge, etc. GPU will work.
3. X doesn't start yet, though this patch eliminates all the visible
unsupported DRM IOCTL calls as observed by setting QEMU_STRACE=1.
4. Intel open
Note that x86_64 systems only offer the _rt signal handler variants,
so the legacy signal handlers remain unimplemented on this platform.
Signed-off-by: Timothy Pearson
---
linux-user/signal.c | 302 +++-
1 file changed, 299 insertions(+), 3
Patch series sent to mailing list here:
http://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg05334.html
In particular, this patch handles the original signal handler problem:
http://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg05335.html
** Changed in: qemu
Status: New => In P
This matches the calling conventions in the Linux kernel and
resolves select() hangs on i386/x86_64 guests.
Signed-off-by: Timothy Pearson
---
linux-user/syscall.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 2968b57
Tested with ExtremeTuxRacer in guest with HDMI audio sink on host
Signed-off-by: Timothy Pearson
---
linux-user/ioctls.h| 72
linux-user/syscall.c | 1 +
linux-user/syscall_defs.h | 73
linux-user/syscall_types.h | 273
Tested with ExtremeTuxRacer in guest with HDMI audio sink on host
Signed-off-by: Timothy Pearson
---
linux-user/ioctls.h| 72
linux-user/syscall.c | 1 +
linux-user/syscall_defs.h | 73
linux-user/syscall_types.h | 273
Tested on a Radeon R290X with multiple 3D applications.
Signed-off-by: Timothy Pearson
---
linux-user/ioctls.h| 45 +-
linux-user/syscall.c | 15
linux-user/syscall_defs.h | 45 +-
linux-user/syscall_types.h | 209
size if applicable.
Signed-off-by: Timothy Pearson
---
linux-user/syscall.c | 27 +--
1 file changed, 21 insertions(+), 6 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 1c17b74..2968b57 100644
--- a/linux-user/syscall.c
+++ b/linux-user
Tested on a Radeon R290X with multiple 3D applications.
Signed-off-by: Timothy Pearson
---
linux-user/ioctls.h| 45 +-
linux-user/syscall.c | 15
linux-user/syscall_defs.h | 45 +-
linux-user/syscall_types.h | 209
'd') IOCTLs in linux. With it and a corresponding architecture
chroot (say aarch64), I am able to successfully run a few 2D and
3D applications with native graphics acceleration. Some
notes/caveats are:
Timothy Pearson (6):
Add initial x86_64 signal handl
1. It will only work with open drivers as their IOCTLs are documented.
2. i965+ is only supported. That is any haswell, ivybridge, etc. GPU
will work.
3. X doesn't start yet, though this patch eliminates all the visible
unsupported DRM IOCTL calls as observed by setting QEMU_STRACE=1.
4. Intel open
Signed-off-by: Timothy Pearson
---
linux-user/x86_64/termbits.h | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/linux-user/x86_64/termbits.h b/linux-user/x86_64/termbits.h
index 1c3445c..5fc4639 100644
--- a/linux-user/x86_64/termbits.h
+++ b/linux-user/x86_64
Signed-off-by: Timothy Pearson
---
linux-user/x86_64/termbits.h | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/linux-user/x86_64/termbits.h b/linux-user/x86_64/termbits.h
index 1c3445c..5fc4639 100644
--- a/linux-user/x86_64/termbits.h
+++ b/linux-user/x86_64
This matches the calling conventions in the Linux kernel and
resolves select() hangs on i386/x86_64 guests.
Signed-off-by: Timothy Pearson
---
linux-user/syscall.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 2968b57
size if applicable.
Signed-off-by: Timothy Pearson
---
linux-user/syscall.c | 27 +--
1 file changed, 21 insertions(+), 6 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 1c17b74..2968b57 100644
--- a/linux-user/syscall.c
+++ b/linux-user
Note that x86_64 systems only offer the _rt signal handler variants,
so the legacy signal handlers remain unimplemented on this platform.
Signed-off-by: Timothy Pearson
---
linux-user/signal.c | 302
+++-
1 file changed, 299 insertions(+), 3
e graphics acceleration. Some
notes/caveats are:
Timothy Pearson (6):
Add initial x86_64 signal handlers
QEMU does not currently support host pages that are larger than
guest pages, likely due to glibc using fixed mmap requests.
Pass select() arguments directly to do_select() on x86
Finally figured it out!
It's the page size. qemu user mode does NOT support a host page that is
greater than 4k on x86/x86_64 systems, despite some claims to the
contrary on older documentation pages.
I'll be updating the patch to print a clear warning on failure instead
of allowing corrupt data
So after some further debugging effort it turns out while the page
allocator is unaware of the mapping (looks like the x86_64 NPTL
implementation never maps the thread ID memory?), g2h() does work on the
address, and in this case they map to the same value. I'll probably
submit a patch using g2h i
qemu can locate the guest page with that address but it has a flags
field of all zero (no access, invalid). Any ideas?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1591611
Title:
chroot using qem
On closer inspection maybe it's not that odd...the parent and child tid
pointers are in abi, not target, space. I'm going to assume direct
assignment is correct (using __put_user()) and proceed from there.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
OK, the fundamental problem is that do_fork() uses put_user_u32() on
child_tidptr, but child_tidptr appears to be a host pointer. Treating
it as a host pointer (direct assignment) allows fork to proceed, but
this seems a bit odd to say the least.
Still investigating.
--
You received this bug no
Yes, I saw that -- implementing the signal handlers fixed the hang and a
few other problems, but the assertion and subsequent SIGABORT/SIGSEGV
are still present. Currently attempting to track down the fork()
issues.
--
You received this bug notification because you are a member of qemu-
devel-ml
** Changed in: qemu
Assignee: (unassigned) => Timothy Pearson (kb9vqf)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1591611
Title:
chroot using qemu-x86_64-static fails on ppc64el
Status
Can you point me to the correct location in the codebase / any available
resources on these handlers? I might be able to tackle this at a later
date, but am not currently familiar with qemu's codebase.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is sub
Are there any plans to implement these signal handlers?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1591611
Title:
chroot using qemu-x86_64-static fails on ppc64el
Status in QEMU:
New
Bug des
Public bug reported:
When attempting to use qemu-x86_64-static from qemu 2.5.0 on a ppc64el
host to chroot into an amd64 environment, all commands fail with an
assertion error. /usr/bin/qemu-x86_64-static from the host was copied
into the chroot /usr/bin, and the host has multiformat support in t
** Tags added: power8
** Tags removed: power8
** Tags added: ppc qemu vga
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1546680
Title:
Incorrect display colors when running big endian guest on POW
Public bug reported:
When running a big endian CentOS guest on a little endian host system
the display shows severe color issues, probably due to endianness not
being properly detected / switched in the emulated display hardware.
Little endian guests show no display issues on the same host hardwar
Some of the signal handling was a mess with a mixture of tabs and 8 space
indents.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/signal.c | 1691 ++-
1 file changed, 867 insertions(+), 824 deletions(-)
diff --git a/linux-user/signal.c b
Now with system call restarting support by all targets remove
uneeded conditionals.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/aarch64/syscall.h| 2 --
linux-user/alpha/syscall.h | 2 --
linux-user/arm/syscall.h| 2 --
linux-user/cris/syscall.h | 2 --
linux
Signed-off-by: Timothy Edward Baldwin
---
linux-user/m68k/syscall.h | 2 ++
linux-user/main.c | 24 +++-
linux-user/signal.c | 20
3 files changed, 25 insertions(+), 21 deletions(-)
diff --git a/linux-user/m68k/syscall.h b/linux-user/m68k
within or
after the first handler with an incorrect context.
This is fixed by queuing synchronous signals separately, however this still
risks delaying a asynchronous signal until the synchronous signal handler
returns rather than handling the signal on another thread.
Signed-off-by: Timothy Edward
Without this SIGTERM could fail to terminate the process, as the
signal lost in QEMU's queue.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 1ce381e..48
Signed-off-by: Timothy Edward Baldwin
---
Signal handling NOT TESTED
linux-user/alpha/syscall.h | 2 ++
linux-user/main.c | 7 +--
linux-user/signal.c| 4 ++--
3 files changed, 9 insertions(+), 4 deletions(-)
diff --git a/linux-user/alpha/syscall.h b/linux-user/alpha
As host signals are now blocked whenever guest signals are blocked, the
queue of realtime signals in now in Linux. The Qemu queue is now
redundant and removed.
Signed-off-by: Timothy Edward Baldwin
Conflicts:
linux-user/qemu.h
---
linux-user/main.c | 7 --
linux-user/qemu.h
contains general infrastructure and safe_syscall_base for x86-64.
Signed-off-by: Timothy Edward Baldwin
---
configure| 13 +
linux-user/Makefile.objs | 3 +-
linux-user/qemu.h| 17 +++
linux-user/safe_syscall/x86_64.S | 34
Signed-off-by: Timothy Edward Baldwin
---
WARNING - NOT TESTED
linux-user/main.c | 7 ++-
linux-user/unicore32/syscall.h | 2 ++
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/linux-user/main.c b/linux-user/main.c
index d86751a..9ca1c99 100644
--- a/linux-user
Signed-off-by: Timothy Edward Baldwin
---
Works without signals, but my signal test case
crashes with or without my changes.
linux-user/main.c| 6 +-
linux-user/sh4/syscall.h | 2 ++
linux-user/signal.c | 16 ++--
3 files changed, 13 insertions(+), 11 deletions
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index da6d140..f89b730 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -6106,7 +6106,10 @@ abi_long
Without this a signal could vanish on thread exit.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 4839154..efe61e3 100644
--- a/linux-user/syscall.c
Signed-off-by: Timothy Edward Baldwin
---
linux-user/aarch64/syscall.h | 2 ++
linux-user/arm/syscall.h | 2 ++
linux-user/main.c| 47 +++-
linux-user/signal.c | 10 +-
4 files changed, 38 insertions(+), 23 deletions
() protects against
concurrency problems with respect to signal handlers.
Signed-off-by: Timothy Edward Baldwin
Conflicts:
linux-user/qemu.h
---
linux-user/qemu.h| 8 +++-
linux-user/signal.c | 111 ++-
linux-user/syscall.c | 49
Signed-off-by: Timothy Edward Baldwin
---
Works without signals, but my signal test case
crashes with or without my changes.
linux-user/main.c | 14 +-
linux-user/microblaze/syscall.h | 2 ++
linux-user/signal.c | 2 +-
3 files changed, 12 insertions
Without this a signal could vanish if thread sends SIGKILL to itself.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index efe61e3..da6d140 100644
--- a/linux
Signed-off-by: Timothy Edward Baldwin
---
gdbstub.c | 13 -
include/exec/gdbstub.h | 1 -
2 files changed, 14 deletions(-)
diff --git a/gdbstub.c b/gdbstub.c
index ffe7e6e..fd319af 100644
--- a/gdbstub.c
+++ b/gdbstub.c
@@ -1472,19 +1472,6 @@ void gdb_exit(CPUArchState
Signed-off-by: Timothy Edward Baldwin
---
WARNING - NOT TESTED
linux-user/cris/syscall.h | 2 ++
linux-user/main.c | 6 +-
linux-user/signal.c | 2 +-
3 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/linux-user/cris/syscall.h b/linux-user/cris/syscall.h
index
Restart read() and write() if signals occur before, or during with SA_RESTART
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index b9ad7b6..c213588 100644
Both queue_signal() and process_pending_signals() did check for default
actions of signals, this is redundant and also causes fatal and stopping
signals to incorrectly cause guest system calls to be interrupted.
The code in queue_signal() is removed.
Signed-off-by: Timothy Edward Baldwin
Signed-off-by: Timothy Edward Baldwin
---
WARNING - NOT TESTED
linux-user/main.c | 12 +---
linux-user/s390x/syscall.h | 2 ++
linux-user/signal.c| 4 ++--
3 files changed, 13 insertions(+), 5 deletions(-)
diff --git a/linux-user/main.c b/linux-user/main.c
index
The return value of openat was being translated by get_errno() twice.
Fixed by removing calls of get_errno() in do_syscall() and keeping those
in do_openat().
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff
Signed-off-by: Timothy Edward Baldwin
---
linux-user/main.c| 4
linux-user/ppc/syscall.h | 2 ++
2 files changed, 6 insertions(+)
diff --git a/linux-user/main.c b/linux-user/main.c
index 124e9cc..5e9e3a8 100644
--- a/linux-user/main.c
+++ b/linux-user/main.c
@@ -1948,6 +1948,10
If there is a signal pending during fork() the signal handler will
erroneously be called in both the parent and child, so handle any
pending signals first.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/linux-user
Signed-off-by: Timothy Edward Baldwin
---
linux-user/signal.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/linux-user/signal.c b/linux-user/signal.c
index 15bd082..fc37f3b 100644
--- a/linux-user/signal.c
+++ b/linux-user/signal.c
@@ -629,7 +629,7 @@ out
Signed-off-by: Timothy Edward Baldwin
---
linux-user/main.c| 3 +++
linux-user/signal.c | 2 +-
linux-user/sparc/syscall.h | 2 ++
linux-user/sparc64/syscall.h | 2 ++
4 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/linux-user/main.c b/linux-user/main.c
index
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index e68eddb..281fa2d 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -698,6 +698,10
confusion with -TARGET_ERESTARTSYS and cpu_loop() will be
altered to act upon the return value accordingly.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/errno_defs.h | 3 +++
linux-user/mips/syscall.h | 4
linux-user/mips64/syscall.h | 4
linux-user/ppc/syscall.h| 2 --
4
Signed-off-by: Timothy Edward Baldwin
---
WARNING - NOT TESTED
linux-user/main.c | 22 ++
linux-user/openrisc/syscall.h | 2 ++
2 files changed, 16 insertions(+), 8 deletions(-)
diff --git a/linux-user/main.c b/linux-user/main.c
index 9ca1c99..b052e17 100644
Signed-off-by: Timothy Edward Baldwin
---
linux-user/i386/syscall.h | 2 ++
linux-user/main.c | 47 -
linux-user/signal.c | 15 +++
linux-user/syscall.c| 2 --
linux-user/x86_64/syscall.h | 2 ++
5 files
If DEBUG_ERESTARTSYS is set restart all system calls once.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 04c91fb..80b8fa8 100644
--- a/linux-user/syscall.c
+++ b
Restart open() and openat() if signals occur before,
or during with SA_RESTART.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 18 --
1 file changed, 4 insertions(+), 14 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index df9b2ca
Signed-off-by: Timothy Edward Baldwin
---
linux-user/main.c | 4
linux-user/mips/syscall.h | 2 ++
linux-user/mips64/syscall.h | 2 ++
3 files changed, 8 insertions(+)
diff --git a/linux-user/main.c b/linux-user/main.c
index 9653155..124e9cc 100644
--- a/linux-user/main.c
+++ b
Check array bounds in host_to_target_errno() and target_to_host_errno().
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 264debc..4e40dc6 100644
--- a/linux
ld be appreciated - this is the only change I intend to make
to unshared code to all targets.
Outstanding issues:
- The remaining blocking target system calls.
- Fatal default actions may be delayed in a broken blocking target
system call.
Timothy E Baldwin (34):
linux-user: Fix array bounds in
Whilst calls to do_fork() are wrapped in get_errno() this does not
translate return values.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index f62c698..264debc
Implemented atomic_barrier system call using GCC/clang
builtin __sync_synchronize().
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index bca3424..72d107a 100644
--- a
Implemented ARM __kernel_memory_barrier using GCC/clang
builtin __sync_synchronize().
Signed-off-by: Timothy Edward Baldwin
---
linux-user/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/main.c b/linux-user/main.c
index 2c9658e..f4b81b1 100644
--- a/linux
Whilst calls to do_fork() are wrapped in get_errno() this does not
translate return values.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/syscall.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index f62c698..bca3424
Misspelled system call name in macro was causing timerfd_create not
to be supported for the ARM target.
Signed-off-by: Timothy Edward Baldwin
---
linux-user/arm/syscall_nr.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/arm/syscall_nr.h b/linux-user/arm
Misspelled system call name in macro was causing timerfd_create not to be
supported for the ARM target.
---
linux-user/arm/syscall_nr.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/arm/syscall_nr.h b/linux-user/arm/syscall_nr.h
index 7d7be7c..53552be 100644
--- a
On 08/03/15 10:23, Peter Maydell wrote:
On 8 March 2015 at 04:18, Timothy Baldwin
wrote:
From ebcb08f4f4ed90c8557cafc02593360c59e10a49 Mon Sep 17 00:00:00 2001
From: Timothy E Baldwin
Date: Sat, 7 Mar 2015 18:42:41 +
Subject: [PATCH] Actually block signals that have been queued in
1 - 100 of 118 matches
Mail list logo
