From: Richard Henderson <richard.henderson@linaro.org>
To: "Emilio G. Cota" <cota@braap.org>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH tcg-next] cputlb: read CPUTLBEntry.addr_write atomically
Date: Tue, 16 Oct 2018 10:13:01 -0700 [thread overview]
Message-ID: <e8dea159-f72c-a3b9-503e-ed9349ed8dc6@linaro.org> (raw)
In-Reply-To: <20181016153840.25877-1-cota@braap.org>
On 10/16/18 8:38 AM, Emilio G. Cota wrote:
> Updates can come from other threads, so readers that do not
> take tlb_lock must use atomic_read to avoid undefined
> behaviour (UB).
>
> This completes the conversion to tlb_lock. This conversion results
> on average in no performance loss, as the following experiments
> (run on an Intel i7-6700K CPU @ 4.00GHz) show.
Thanks for the quick turn-around. Queued.
r~
prev parent reply other threads:[~2018-10-16 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 15:38 [Qemu-devel] [PATCH tcg-next] cputlb: read CPUTLBEntry.addr_write atomically Emilio G. Cota
2018-10-16 17:13 ` Richard Henderson [this message]
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=e8dea159-f72c-a3b9-503e-ed9349ed8dc6@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=cota@braap.org \
--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).