From: Hamza Mahfooz <someguy@effective-light.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Laurent Vivier <laurent@vivier.eu>,
QEMU Trivial <qemu-trivial@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] linux-user: make process_pending_signals thread-safe
Date: Thu, 27 May 2021 08:16:11 -0400 [thread overview]
Message-ID: <Z2MRTQ.QBPUAAPP6M0X1@effective-light.com> (raw)
In-Reply-To: <CAFEAcA8koCJTd5JY4NWX26EPpHq_QMwi11-FYf4OJhZyhecT-w@mail.gmail.com>
On Thu, May 27 2021 at 11:45:26 AM +0100, Peter Maydell
<peter.maydell@linaro.org> wrote:
> What issue are we trying to fix by making this change ?
I suppose that it wouldn't fix any issues in the current state of
affairs,
maybe it is something to reconsider if glibc ever changes such that,
sigprocmask is no longer MT-safe (which is within reason since the MT
behavior of sigprocmask is undefined by POSIX).
WARNING: multiple messages have this Message-ID (diff)
From: Hamza Mahfooz <someguy@effective-light.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Laurent Vivier <laurent@vivier.eu>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] linux-user: make process_pending_signals thread-safe
Date: Thu, 27 May 2021 08:16:11 -0400 [thread overview]
Message-ID: <Z2MRTQ.QBPUAAPP6M0X1@effective-light.com> (raw)
In-Reply-To: <CAFEAcA8koCJTd5JY4NWX26EPpHq_QMwi11-FYf4OJhZyhecT-w@mail.gmail.com>
On Thu, May 27 2021 at 11:45:26 AM +0100, Peter Maydell
<peter.maydell@linaro.org> wrote:
> What issue are we trying to fix by making this change ?
I suppose that it wouldn't fix any issues in the current state of
affairs,
maybe it is something to reconsider if glibc ever changes such that,
sigprocmask is no longer MT-safe (which is within reason since the MT
behavior of sigprocmask is undefined by POSIX).
next prev parent reply other threads:[~2021-05-27 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 2:46 [PATCH] linux-user: make process_pending_signals thread-safe Hamza Mahfooz
2021-05-24 2:46 ` Hamza Mahfooz
2021-05-27 10:16 ` Peter Maydell
2021-05-27 10:16 ` Peter Maydell
2021-05-27 10:37 ` Hamza Mahfooz
2021-05-27 10:37 ` Hamza Mahfooz
2021-05-27 10:45 ` Peter Maydell
2021-05-27 10:45 ` Peter Maydell
2021-05-27 12:16 ` Hamza Mahfooz [this message]
2021-05-27 12:16 ` Hamza Mahfooz
-- strict thread matches above, loose matches on Subject: below --
2021-04-27 6:32 effective-light
2021-04-27 6:32 ` effective-light
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z2MRTQ.QBPUAAPP6M0X1@effective-light.com \
--to=someguy@effective-light.com \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.