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 ar
contributing to QEMU. If you decide to use this patch, I'm happy to resend
the patch via `git send email`.
Thanks!
Marli
On Mon, Jul 1, 2019 at 2:08 AM Peter Maydell
wrote:
> On Sat, 29 Jun 2019 at 11:53, Philippe Mathieu-Daudé
> wrote:
> >
> > Hi Marlies,
> >
> &g
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
> w
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
