[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Thread safety of coroutine-sigaltstack
From: |
Peter Maydell |
Subject: |
Re: Thread safety of coroutine-sigaltstack |
Date: |
Thu, 21 Jan 2021 16:44:40 +0000 |
On Thu, 21 Jan 2021 at 16:10, Daniel P. Berrangé <berrange@redhat.com> wrote:
> FWIW The libucontext impl is all ASM based and has coverage for all the
> arches we care about:
>
> https://github.com/kaniini/libucontext
>
> so doesn't seem like there's a need for coroutine-asm if we can rely
> on libucontext for portability where neede.
The README for that notes a couple of pretty major omissions:
* it doesn't handle floating point registers
* it doesn't do anything about the signal mask
I'm pretty sure that not handling the fp regs could cause breakage
for Arm at least (depending on what the compiler chooses to do
in the functions that work with the ucontext functions). The
signal mask stuff might be OK for us because of the carefully
limited use we make of the ucontext functions, but it would be
a bit of a pain to have to analyse that code for both sets of semantics.
thanks
-- PMM
- Re: Thread safety of coroutine-sigaltstack, (continued)
- Re: Thread safety of coroutine-sigaltstack, Paolo Bonzini, 2021/01/20
- Re: Thread safety of coroutine-sigaltstack, Eric Blake, 2021/01/20
- Re: Thread safety of coroutine-sigaltstack, Laszlo Ersek, 2021/01/20
- Re: Thread safety of coroutine-sigaltstack, Paolo Bonzini, 2021/01/21
- Re: Thread safety of coroutine-sigaltstack, Daniel P . Berrangé, 2021/01/21
- Re: Thread safety of coroutine-sigaltstack,
Peter Maydell <=
- Re: Thread safety of coroutine-sigaltstack, Paolo Bonzini, 2021/01/21
- Re: Thread safety of coroutine-sigaltstack, Laszlo Ersek, 2021/01/22
- Re: Thread safety of coroutine-sigaltstack, Laszlo Ersek, 2021/01/22
- Re: Thread safety of coroutine-sigaltstack, Laszlo Ersek, 2021/01/22
- Re: Thread safety of coroutine-sigaltstack, Markus Armbruster, 2021/01/22
Re: Thread safety of coroutine-sigaltstack, Max Reitz, 2021/01/22