From: Tom Lane <tgl@sss.pgh.pa.us>
To: Paul Guyot <pguyot@kallisys.net>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16990: Random PANIC in qemu user context
Date: Sun, 02 May 2021 18:19:58 -0400
Message-ID: <3723542.1619993998@sss.pgh.pa.us> (raw)
In-Reply-To: <86C24765-95F7-464F-9677-B09A396A5F69@kallisys.net>
References: <16990-10b586bc699fd234@postgresql.org>
<3714052.1619980429@sss.pgh.pa.us>
<86C24765-95F7-464F-9677-B09A396A5F69@kallisys.net>
Paul Guyot <pguyot@kallisys.net> writes:
> QEMU user emulation documentation mentions something specific to threading on ARM.
> https://qemu.readthedocs.io/en/latest/user/main.html
>> Threading:
>> On Linux, QEMU can emulate the clone syscall and create a real host thread (with a separate virtual CPU) for each emulated thread. Note that not all targets currently emulate atomic operations correctly. x86 and Arm use a global lock in order to preserve their semantics.
Oooh, that's pretty suggestive. I wonder just when that "global lock" is
taken or released. Maybe the timing of it is such that it interferes
with ever seeing our lock as free?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, pguyot@kallisys.net, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16990: Random PANIC in qemu user context
In-Reply-To: <3723542.1619993998@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox