Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

..@iki.fi; > > qemu-triv...@nongnu.org; Peter Maydell; Shu-Chun Weng; Aleksandar > Markovic > > Subject: [EXTERNAL]Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and > SIGRTMAX - 1 > > > > Le 26/08/2019 à 23:10, Josh Kunz a écrit : > > > On Wed, Aug 21, 2019 a

Re: [EXTERNAL]Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

Sent: Wednesday, August 28, 2019 10:51 AM >> > To: Josh Kunz; Aleksandar Markovic; milos.stojano...@rt-rk.com >> > Cc: marlies.r...@gmail.com; qemu-devel@nongnu.org; riku.voi...@iki.fi; >> > qemu-triv...@nongnu.org; Peter Maydell; Shu-Chun Weng; Aleksandar >> M

Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

Le 26/08/2019 à 23:10, Josh Kunz a écrit : > On Wed, Aug 21, 2019 at 2:28 AM Laurent Vivier > wrote: > > Le 19/08/2019 à 23:46, Josh Kunz via Qemu-devel a écrit : > > Hi all, > > > > I have also experienced issues with SIGRTMIN + 1, and am interested in

Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

On Mon, 26 Aug 2019 at 22:10, Josh Kunz wrote: > That said, overall, fixing the SIGRTMIN+1 issue using a more-generic > signal-multiplexing mechanism doesn't seem *that* much better to me. It adds > a lot of complexity, and only saves a single signal (assuming glibc doesn't > add more reserved

Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

On Wed, Aug 21, 2019 at 2:28 AM Laurent Vivier wrote: > Le 19/08/2019 à 23:46, Josh Kunz via Qemu-devel a écrit : > > Hi all, > > > > I have also experienced issues with SIGRTMIN + 1, and am interested in > > moving this patch forwards. Anything I can do here to help? Would the > > maintainers

Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

Le 19/08/2019 à 23:46, Josh Kunz via Qemu-devel a écrit : > Hi all, > > I have also experienced issues with SIGRTMIN + 1, and am interested in > moving this patch forwards. Anything I can do here to help? Would the > maintainers prefer myself or Marli re-submit the patch? > > The Go issue here

Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

Hi all, I have also experienced issues with SIGRTMIN + 1, and am interested in moving this patch forwards. Anything I can do here to help? Would the maintainers prefer myself or Marli re-submit the patch? The Go issue here seems particularly sticky. Even if we update the Go runtime, users may

Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

Hi, Just wanted to follow up to see what your thoughts are. Is it preferable if I submit a PR to the Go runtime first? That would mitigate concerns about Go breaking on QEMU with this patch. Thanks, Marli On Mon, Jul 1, 2019 at 3:04 PM Marlies Ruck wrote: > Hi All, > > You are correct, this

Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

Hi All, You are correct, this would break Go binaries. I was planning on submitting a PR to the Go runtime if my patch was accepted to QEMU. The Go PR would ignore the failure to register a handler for SIGRTMAX - 1, just as it currently ignores the failure on SIGRTMAX (

Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

On Sat, 29 Jun 2019 at 11:53, Philippe Mathieu-Daudé wrote: > > Hi Marlies, > > On 6/29/19 1:26 AM, Marlies Ruck wrote: > > Hi, > > > > I just wanted to follow up since I sent this patch a week ago to make sure > > it was a received. An ack would be appreciated. > > You did not Cc'ed the

Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

Hi Marlies, On 6/29/19 1:26 AM, Marlies Ruck wrote: > Hi, > > I just wanted to follow up since I sent this patch a week ago to make sure > it was a received. An ack would be appreciated. You did not Cc'ed the maintainer, so he likely missed it. See:

Re: [Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

Hi, I just wanted to follow up since I sent this patch a week ago to make sure it was a received. An ack would be appreciated. Thanks, Marli On Fri, Jun 21, 2019 at 3:58 PM Marlies Ruck wrote: > Hi, > > Attached is a patch to let guest programs use SIGRTMIN + 1 by swapping > with SIGRTMAX -

[Qemu-devel] patch to swap SIGRTMIN + 1 and SIGRTMAX - 1

Hi, Attached is a patch to let guest programs use SIGRTMIN + 1 by swapping with SIGRTMAX - 1. Since QEMU links against glibc, it reserves the signal for itself and returns EINVAL (as noted in the commit message). This means various applications that use SIGRTMIN + 1 cannot run on QEMU, including