From: Richard Henderson <richard.henderson@linaro.org>
To: Wei Li <lw945lw945@yahoo.com>, pbonzini@redhat.com, eduardo@habkost.net
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] fix cmpxchg instruction
Date: Sun, 20 Mar 2022 12:07:47 -0700 [thread overview]
Message-ID: <5389600e-2bce-3db4-3826-1d46221dddb0@linaro.org> (raw)
In-Reply-To: <20220319160658.336882-2-lw945lw945@yahoo.com>
On 3/19/22 09:06, Wei Li wrote:
> We need a branch to determine when the instruction can touch the
> accumulator. But there is a branch provided by movcond.
There is no branch in movcond -- this expands to cmov.
> - /* store value = (old == cmp ? new : old); */
> - tcg_gen_movcond_tl(TCG_COND_EQ, newv, oldv, cmpv, newv, oldv);
> + tcg_gen_brcond_tl(TCG_COND_EQ, oldv, cmpv, label1);
...
> /* Perform an unconditional store cycle like physical cpu;
> must be before changing accumulator to ensure
> idempotency if the store faults and the instruction
> is restarted */
Your branch invalidates the comment -- the store becomes conditional, and we no longer get
a write fault on read-only pages when the comparison fails. OTOH, we're already getting
the incorrect SIGSEGV behaviour, since we get a read fault on an unmapped page instead of
a write fault.
The faulting behaviour could be addressed with a write_probe prior to the original load.
Alternately, we can use the tcg_gen_atomic_cmpxchg_tl path whenever mod != 3. While an
unlocked cmpxchg need not be atomic, it is not required to be non-atomic either, and it
would reduce code duplication.
r~
next prev parent reply other threads:[~2022-03-20 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220319160658.336882-1-lw945lw945.ref@yahoo.com>
2022-03-19 16:06 ` [PATCH 0/2] cmpxchg and lock cmpxchg should not touch accumulator Wei Li
2022-03-19 16:06 ` [PATCH 1/2] fix cmpxchg instruction Wei Li
2022-03-20 19:07 ` Richard Henderson [this message]
2022-03-19 16:06 ` [PATCH 2/2] fix lock " Wei Li
2022-03-20 19:21 ` Richard Henderson
2022-03-21 8:50 ` Wei Li
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=5389600e-2bce-3db4-3826-1d46221dddb0@linaro.org \
--to=richard.henderson@linaro.org \
--cc=eduardo@habkost.net \
--cc=lw945lw945@yahoo.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).